Slide 42
Slide 42 text
Q&A Example:1
Question Answer
What was the most difficult
part?
Contest: The tight deadlines were hard because I have limited time as a hobbyist.
Zephyr: Understanding the configuration system (CMakeLists, prj.conf, Device Tree) was tricky at first.
But once I learned the basic West commands, I could write C/C++ code normally.
What are the benefits of
using Zephyr?
1. Small Size: Zephyr fits on small SoC easily (low RAM/ROM usage).
2. Hardware support: It supports many boards, giving lots of choices.
3. Rich libraries: Libraries for interfaces and wireless make creating hardware demos very easy.
Advice for beginners
implementing Zephyr?
1. Copy and modify: Copy the reference board's schematic, config, and Device Tree
from the IC maker, then modify them.
2. Use recommended tools: Use the manufacturer's recommended IDE
(e.g., "nRF Connect for VS Code" for Nordic).
What Zephyr feature do you
want to try next?
I want to test inter-core communication (IPC, OpenAMP).
Many recent SoCs, like the nRF54L15 and Pico 2, have multiple cores.
Is building for RISC-V
difficult?
It is not difficult. You just need to specify the target core in the west build command
(e.g., select "cpuapp" for Arm or "cpuflpr" for RISC-V).
“west build -p always -b xiao_nrf54l15/nrf54l15/cpuapp(cpuflpr) samples/hello_world”