Nordic Semiconductor · Low-level team
Senior R&D Engineer, since Feb 2023 · Kraków
- nrfx integration with the Zephyr shim layer - the drivers that carry every Nordic SoC into the RTOS.
- Bring-up of new SoCs: startup code, assembly, clock and power domains, hands-on hardware debug.
- Device tree at scale - bindings, overlays, multi-domain SoC descriptions in Zephyr and nRF Connect SDK.
- Subsystems: app-domain RT framework and HPF (high-performance framework).
Selected contributions - upstream/NCS
zephyrproject-rtos/zephyr #108432
zephyrproject-rtos/zephyr #109317
nrfconnect/sdk-nrf #29253
nrfconnect/sdk-nrf #27905
nrfconnect/sdk-nrf #27792
Reviewable code, not bullet points - every line went through public review.
Frequently asked questions
What does Collaborator status on Zephyr RTOS mean?
It is a role in the upstream Zephyr RTOS project granted to people who contribute code regularly and take part in public review. In practice it means the work is open and verifiable - every pull request goes through open community review.
What is the Zephyr shim layer and what role does nrfx play?
nrfx is Nordic Semiconductor's HAL for nRF devices. The shim connects it to Zephyr's driver API, so every Nordic SoC runs under the RTOS without writing drivers from scratch for each part.
What does bringing up a new SoC involve?
Startup code and assembly, clock and power domain configuration, describing the part in device tree (bindings and overlays), and hands-on hardware debug - until the silicon boots reliably under Zephyr and the nRF Connect SDK.
Where can the code be seen?
In public repositories: zephyrproject-rtos/zephyr and nrfconnect/sdk-nrf. Five selected pull requests are linked on this page.