• State Verified Answer
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 89 subscribers
  • Views 698 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 354563
Options

nRF54L05 without Zephyr/VSCode

pungent1188

How do I download the bare metal SDK without Zephyr/VSCode addon?

Looks like we are moving backwards when manufacturers forced our hands to use specific tools.

Parents
  • 0

    Agree with the conclusions in this thread. Nordic’s own reply basically says: nrf-bm is a stepping stone toward NCS and it still depends on West/Kconfig/Zephyr build plumbing. So if the goal is “self-contained CMSIS/MDK-style project” or “use any compiler/toolchain with a flat folder + macros,” nrf-bm isn’t that today.

    The MDK + nrfx approach Emil mentioned is the closest to “pure bare metal,” but as noted it’s just startup + registers + drivers — you don’t get BLE or higher layers for free.

    Disclosure: I’m the author of IOcomposer/IOsonata.

    I’m working on a different workflow: keep the Nordic vendor layer underneath for nRF54, but make the *application* workflow MCU-centric and C/C++ configured (no Devicetree/Kconfig as the primary config model). IOcomposer generates the project, sets up build + debug, and the optional AI can scaffold a full project (including BLE) with patch-style edits grounded in the actual installed headers.

    Demo (unedited): prompt → complete nRF54L15 BLE project → builds → launches debugger:
    https://youtu.be/LR2vYtMeC8A
    Try/install: https://iocomposer.io

    If you test it, even a short reply helps:
    - Host OS
    - Board / chip
    - What you tried
    - First error line + snippet (if it fails)

Reply
  • 0

    Agree with the conclusions in this thread. Nordic’s own reply basically says: nrf-bm is a stepping stone toward NCS and it still depends on West/Kconfig/Zephyr build plumbing. So if the goal is “self-contained CMSIS/MDK-style project” or “use any compiler/toolchain with a flat folder + macros,” nrf-bm isn’t that today.

    The MDK + nrfx approach Emil mentioned is the closest to “pure bare metal,” but as noted it’s just startup + registers + drivers — you don’t get BLE or higher layers for free.

    Disclosure: I’m the author of IOcomposer/IOsonata.

    I’m working on a different workflow: keep the Nordic vendor layer underneath for nRF54, but make the *application* workflow MCU-centric and C/C++ configured (no Devicetree/Kconfig as the primary config model). IOcomposer generates the project, sets up build + debug, and the optional AI can scaffold a full project (including BLE) with patch-style edits grounded in the actual installed headers.

    Demo (unedited): prompt → complete nRF54L15 BLE project → builds → launches debugger:
    https://youtu.be/LR2vYtMeC8A
    Try/install: https://iocomposer.io

    If you test it, even a short reply helps:
    - Host OS
    - Board / chip
    - What you tried
    - First error line + snippet (if it fails)

Children
No Data
Related
Terms of service