Hi there!
May I know why sample codes cannot be run on nRF54L15DK when board target "nrf54l15dk/nrf54l15/cpuapp" is chosen?
Yet, everything is fine when nrf54l15dk/nrf54l15/cpuapp/ns" is selected.
Thanks!
Hi there!
May I know why sample codes cannot be run on nRF54L15DK when board target "nrf54l15dk/nrf54l15/cpuapp" is chosen?
Yet, everything is fine when nrf54l15dk/nrf54l15/cpuapp/ns" is selected.
Thanks!
Hi,
Which NCS version are you using?
Can you elaborate what is not working when you build for "nrf54l15dk/nrf54l15/cpuapp" target? I have built many samples for this target, and never seen any problems with running the samples.
Which samples have you tested?
Which version of the nRF54L15 DK are you using? (see sticker on the board)
Best regards,
Jørgen
Hi,
Can you try to install nRF Connect SDK (NCS) and toolchain v2.9.0 and see if you experience the same problem there?
nRF54L15 DK v0.9.2 has a revision 1 chip and this is only supported in NCS v2.9.0. The changes should not have any impact on this, but it would be good if you can try this out anyway.
Best regards,
Jørgen
Hi there! what do you mean by "delete the build directory" Is that removing the entire build and create a new one?
Yes, delete the folder where the build files are stored. In your case, this looks like "C:/Users/morri/nrf/direct_test_mode/build/" according to your build log.
Tried but still showing the same thing.
Hi there!
I reinstalled toolchain v2.9.0. Now I can have both target boards "nrf54l15dk/nrf54l15/cpuapp" and "nrf54l15dk/nrf54l15/cpuapp/ns" for my application.
If I use my own hardware design instead of the DK, may I ask if I can still use the two target boards above? Anything I need to pay attention to ?
Thanks!
Great to hear that a reinstall of the toolchain resolved the problem.
You can typically use the DK targets for initial testing, but since they describe the hardware on our boards, it may include things not present on your board and missing parts that you have on your board. I would recommend creating your own board targets as soon as you have you own hardware, see this DevAcademy lesson: https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-3-adding-custom-board-support/
Great to hear that a reinstall of the toolchain resolved the problem.
You can typically use the DK targets for initial testing, but since they describe the hardware on our boards, it may include things not present on your board and missing parts that you have on your board. I would recommend creating your own board targets as soon as you have you own hardware, see this DevAcademy lesson: https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-3-adding-custom-board-support/
Thanks!