Porting Zephyr OS for a SoC (Cortex-R5)
summary
Shows whether a Cortex-R5 port actually boots: exact SOC/board file layout, linker script, DTSI snippets and kconfig entries used; driver work: UART implementation with printk-backed shell, timer hooks and interrupt binding; build and toolchain specifics via West/CMake build flow and where generated headers and .config land; debugging that worked: Trace32 and RAM dump steps, which prints appeared, what failed, how many iterations to a working flashable image and which tests prove success.
AI-written summary · about
chapters (13)
- 0:00Porting Zephyr for Cortex-R5
- 1:11Zephyr OS overview
- 1:56SOC compatibility components
- 2:58Hardware support for Cortex-R5
- 6:31Adding new SOC in Zephyr
- 8:40Device tree files
- 11:06Board configurations
- 12:55New drivers integration
- 15:24Porting debugging tips
- 16:29Zephyr tools and commands
- 17:32Timer driver implementation
- 19:40UART driver demo
- 21:03Future enhancements
related talks
27mZephyr Porting Efforts in High Performance SoCs
42mEnabling Zephyr on Your Hardware Platform
42mEnabling Zephyr on Your Hardware Platform
34mZephyr Project: RTOS Start-up and Initialization Flow
30mSoC Development: From ROM to Application
01h 03mZephyr RTOS: Software power tools for constrained devices
40mHow to extract a bare metal flavor of code out of Zephyr to use in RTOS?
42mTaking Your Hardware to Production with Zephyr RTOS