Supply your dependency source
The integration build expects the library trees under lib/<name> by default, with CMake cache variables for alternate locations. The toolkit does not automatically vendor or pin a compatible dependency set.
EMBEDDED COMPONENTS · 20 CATALOGUE ENTRIES
Small components.
Separate contracts.
Micro Toolkit is an integration and documentation repository for a core set of independent C99 libraries. The libraries keep their own repositories and APIs; the toolkit is not a framework that bundles them into one runtime.
01 / INTEGRATION REPOSITORY
Nine documented core libraries
The toolkit README lists nine core projects and a multi-library sensor-node example. It serves as integration documentation, migration notes and examples, not the source of truth for each library.
COMMUNICATIONmicrobus
TIMEmicrotimer
Integration is not hardware validation
The toolkit repository says its example does not prove platform support. Its verification notes distinguish inspected headers from an integration build and mark that build as not verified in the audit record.
Support status. The integration matrix lists upstream refs as UNPINNED. CI is configured to clone current upstream source and build the example under GCC/Clang variants, but the repository’s own status table does not claim a locally verified compatible dependency set. Do not infer a release-ready or hardware-supported bundle from the existence of the example.
02 / COMPONENT MAP
Find a library by what it owns
These placements describe the module’s primary role. A module remains independently integrated and versioned.
03 / CORE MODULES
Browse the documented toolkit set
Micro ToolkitDevelopment
micoring
A fixed-capacity copy-based ring uses caller-owned storage, with optional constrained SPSC atomic mode.
Product detailsMicro ToolkitDevelopment
microbus
A small event bus copies payload bytes and supports synchronous publish or bounded deferred dispatch.
Product detailsMicro ToolkitDevelopment
microcbor
A zero-allocation encoder/decoder implements a definite-length RFC 8949 subset.
Product detailsMicro ToolkitVerification
microconf
Validated schemas and a canonical two-slot format keep data caller-owned and bounded.
Product detailsMicro ToolkitDevelopment
microfsm
A table-driven finite-state-machine engine keeps states, events and actions explicit.
Product detailsMicro ToolkitDevelopment
microlog
A small logging component routes structured records through caller-controlled storage and sinks.
Product detailsMicro ToolkitDevelopment
microres
Caller-owned retry, circuit-breaker and token-bucket primitives provide explicit resilience policy.
Product detailsMicro ToolkitDevelopment
microsh
A fixed-capacity shell parses ASCII commands and calls registered argc/argv handlers.
Product detailsMicro ToolkitDevelopment
microtimer
A fixed-capacity manager fires caller callbacks from explicit tick calls.
Product details04 / RELATED LIBRARIES
Other independently presented micro components
These products share an embedded scale or naming lineage. They are not listed among the toolkit repository’s nine core modules.
05 / INTEGRATION NOTES
Choose a module; keep its limits local
- Use the individual repository page and header as the API reference for that component.
- Review the toolkit’s integration and migration docs when combining modules.
- Keep dependency revisions explicit in your own build until the toolkit records a pinned compatible set.
- Check platform and ISR claims against the individual library’s own evidence; the integration repository does not establish them for the whole set.
- Build the example with your selected library revisions before treating the combination as verified.