Applications › Secure IoT
Connected devices keep keys and critical logic in the Secure world and run the network stack outside it. STK can schedule both worlds from one kernel.
Network stacks, USB and parsers are exposed. A bug there must not reveal keys or firmware-update logic.
TrustZone separates Secure and Non-Secure code, but something still has to schedule threads on both sides.
Cortex-M23 and M33-class MCUs have little flash and RAM to spare for security infrastructure.
The open-source TrustZone driver schedules Secure tasks, with independent Secure and Non-Secure MPU hardening.
The kernel runs in the Secure binary and schedules both worlds, with CMSE-checked NSC gateways and wrappers for tasks and sync objects. Developed on Cortex-M23/M33/M55/M85-class cores.
Non-Secure code uses a Kernel facade with the familiar STK API, so application code does not need rewriting.
Third-party ports for lwIP and mbedTLS.
TinyUSB port for USB device and host stacks.
Raspberry Pi Pico 2 W examples, including TrustZone, are in the repository.
Keep key storage, firmware-update verification and cryptography in the Secure world.
Run the network stack (lwIP, TLS with mbedTLS) and the application as Non-Secure tasks that call into the Secure world through CMSE-checked gateways.
Use the commercial interface so both worlds share one scheduler and Non-Secure code keeps the STK API.
Restrict tasks inside each world with MPU regions and unprivileged mode.
Secure-only scheduling is part of the MIT-licensed kernel; the full Secure + Non-Secure interface is a commercial component. Contact us for details.
Porting, real-time tuning, certification support and commercial components are available. See services.