User guide

The current usable workflow is native kernel development and conformance testing. Embedded ports have QEMU configurations; a complete physical-board controller, driver platform and isolated profile remain later gates.

• Getting started
  • Prerequisites
  • Embedded tests on EmbSIM
  • Reference model
  • First sample
• Choosing current APIs
• Core concepts
• Threads, periodic work and shutdown
  • A complete finite program
  • Compile and run on native Linux
  • Choose priorities and deadlines deliberately
  • Storage and cancellation
• Synchronization and notifications
  • A complete producer/consumer program
  • Why the bound consumer drains first
  • Wait results and execution context
  • Mutex ownership and owner death
• Configuration and testing
  • Select a reference configuration
  • Add diagnostic options without changing the reference preset
  • Inspect generated results
  • Limits that configuration cannot remove
• Debugging and diagnosing failures
  • Narrow a failing run
  • Inspect a thread
  • Register bounded diagnostic hooks
  • Common symptoms

Use the generated API reference for current declarations, subsystem specifications for target semantics, and Project status for implementation/evidence limits. Future APIs are not substitutes for an implementation.