• State Not Answered
  • Replies 3 replies
  • Subscribers 95 subscribers
  • Views 191 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 362839
Options

IAR Compiler for nRF Connect SDK Bare Metal - nRF54L

Julio Cabrera

We develop Class C software for a medical device on the nRF54L15 with the S145 SoftDevice. We are also evaluating the nRF54LM20A. We use only the nRF Connect SDK Bare Metal option (sdk-nrf-bm v2.0.0). We do not use the nRF Connect SDK with the Zephyr RTOS. We have two questions about the compiler and SDK usage.

1. Can we build an sdk-nrf-bm application with the IAR Arm Toolchain (v9.70 or newer) instead of the GCC toolchain in the NCS toolchain bundle? Please tell us if this configuration is supported, tolerated, or not supported. If so, please tell us how to select IAR in the build.

2. Which compiler toolchains does Nordic support for sdk-nrf-bm? Please give the complete list, with versions.

2.16.1.2
2.16.1.2
2.16.1.2
2.16.1.2
Parents Reply
  • 0 in reply to Amanda Hsieh

    Hi Amanda,

    Thank you for your answer.

    I asked about IAR support because I found two indications that it may be possible to use the nRF54L15 with IAR:

    1. The IAR supported devices page lists the nRF54L15_M33 as a supported device.

    2. An earlier nrfx release, v4.3.1, includes an IAR startup file for the nRF54L15 application core. I understand that this is a previous version and that the latest nrfx release is currently v4.5.0.

    Could you please clarify what “IAR is not supported” means in this context? Does it mean that Nordic does not officially integrate, test, or maintain IAR support in nRF Connect SDK Bare Metal, even though IAR lists the device and an earlier nrfx release provides startup code? 

    I would like to understand whether an unofficial custom IAR integration is technically possible, even if it is not officially supported by Nordic.

    Regards,
    Julio

Children
Related
Terms of service