How to Integrate My (Proprietary) Code in Zephyr
summary
Concrete steps to link a proprietary static library (Cadence natureDSP for HiFi4) into Zephyr using either CMake variables or Zephyr’s module mechanism, with exact files and commands: add CMakeLists entries to set lib location/name and include dirs, or package the library as an external module with a module.yml that declares a binary blob and license, fetch it with West blob, then build with West (or CMake + ninja) pointing Zephyr SDK toolchain; includes a working proof‑of‑concept IRQ driver and ongoing Sound Open Firmware port to Zephyr device-driver APIs.
AI-written summary · about
chapters (5)
- 0:00Introduction and agenda
- 0:22Zephyr project overview
- 0:55Integrating proprietary code
- 25:58Sound Open Firmware case study
- 28:48Conclusion and Q&A
related talks
27mBuilding a Zephyr-Native Audio Framework With Sound Open Firmware
42mEnabling Zephyr on Your Hardware Platform
36mZephyr on a Hearing Aid
40mHow to extract a bare metal flavor of code out of Zephyr to use in RTOS?- 27mBuilding a Zephyr-Native Audio Framework With Sound Open Firmware
42mEnabling Zephyr on Your Hardware Platform
08mKeynote: Zephyr as the Foundation for a Microcontroller SDK
20mAbusing zephyr and meta-zephyr