Build with open resources.
Official, open and partner-provided resources for embedded HMI development — organized by what you need, not by one vendor.
What are you looking for?
Use Guides when you are deciding what to build. Use Technical Resources when you already know the platform or tool you need.
Architecture & design decisions
Serial HMI vs chip-level HMI, MCU / MPU / SoC, GUI workflow and the path from chip to production.
Read the Guides →SDKs, docs, tools & hardware
Search official and Open HMI resources by vendor, category, access model and source.
Browse Resources →Demos, integrations & contributors
Discover reusable engineering work and the people who can help turn it into a project.
Explore Community →Three layers. Clear ownership.
Vendor Resources
SDKs, documentation, tools and hardware references linked to their official source and access rules.
Browse Technical Resources →Practical Guides
Architecture guides, demo cases, integration notes and reusable development knowledge created for HMI projects.
Open Guide Library →Contributor Knowledge
Demos, porting notes, guides and integration experience shared by engineers and solution partners.
Browse Contributors →Practical decisions, not another link list.
Vendor-neutral architecture and workflow guides connect the resource library to real product decisions.
When Should You Move Beyond a Serial HMI?
Cost, convenience, flexibility, product differentiation and the ecosystem needed for chip-level HMI.
Read Guide → ArchitectureMCU, MPU or SoC for Embedded HMI?
A requirement-first method for choosing compact RTOS, performance RTOS or Linux / multimedia HMI.
Read Guide → GUI & SoftwareChoosing the Right GUI Tool
Compare embedded GUI workflows by team, platform, hand-off, integration and maintainability.
Read Guide → ProductionFrom Chip to Production HMI
How compute, display, BSP, application, engineering and production supply fit into one platform.
Read Guide →Published contributions
The registry indexes useful work without taking ownership of linked repositories, then connects published capability to relevant project paths.
One structure. Different access models.
A vendor workspace can be as open or as controlled as the vendor requires. The first structured workspace is live; more can be added without redesigning the site.
Know how a resource is available.
License permits open collaboration. Check the source license before reuse or mirroring.
Publicly accessible from the official or project source.
Available after account registration with the resource owner.
Access is provided after project or technical qualification.
Resource existence can be shown, but files remain controlled by the owner.
Developer Resources
Official vendor resources remain owned and governed by their respective source owners. Open HMI Network organizes discovery and adds independent guides, demos and community content.
Help build the ecosystem.
Share a demo, guide, porting note or integration — or add a vendor workspace with the right access model.