Cannot flash using VSCode in nRF54L15 dev kit

[FMistrorigo]

Hi,

I just finished to setup everything to start using nRF Connect for VSCode Extension. I followed the "nRF Connect SDK Fundamentals" course in the DevAcademy.

I installed nRF Command Line Tools, VSCode and the nRF Connect for VSCode extension pack. I then installed the latest toolchain and SDK. (all versions at the end)

After copying the Blinky example and changing the code to turn on also a second led, I was able to build the configuration and build the project, but once I tryied to flash it to the board nothing changed. (the board shows in the Connected Devices)

I then tryied different things to make it work and found out that using the nRF Connect for Desktop app everything works... using the programmer tool and passing my merged.hex file, it programmed successfully.

I then moved to VSCode and used the "Erase Board" command to be sure that the board was reachable; It worked and removed the firmware from the dev kit.

I really don't know if the problem is related to something I'm missing or if it's a problem of the command in the extension.

Please help me find out what is causing the problem.

Thanks,

Fabio

MORE INFO:

Command Line Tools (10.24.2)

VSCode version (1.95.3)

nRF Connect for VSCode extension pack (v2024.9.5) - so I'm now working with nRF Connect v2024.11.75.

Toolchain (v2.8.0)

SDK (v2.8.0)

running the command "nrfjprog --version" in powershell returns:
"nrfjprog version: 10.24.2 external"
"JLinkARM.dll version: 8.10h"

[mojangeex]

Im having the same problem here. I am using nRF54L15-PDK v0.8.1 and with no success. says flashed successfully but nothing gets loaded to device. 

In dev acedemy: https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-1-nrf-connect-sdk-introduction/topic/exercise-2-1/ 
It says to just use it as dk board but sadly doesnt work either. 

[Vidar Berg]

Are you building for cpuapp or cpuapp_ns? If the latter, please try adding CONFIG_TFM_PROFILE_TYPE_MINIMAL=y to your project configuration.

[FMistrorigo]

I already tryied to do that but without success, everything is the same, my only guess for now is that maybe the project folder needs to be somewhere else... but it makes no sense.

[Vidar Berg]

FMistrorigo said:

I already tryied to do that but without success, everything is the same,

The program will not enter the TFM error handler if you are building for cpuapp instead of cpuapp_ns. So it can't be the same issue. Did you try to debug the applications after you changed the build target?

[mojangeex]

Tried 4 different options  secure and non secure with pdk and secure and non secure with dk.
It doesnt work on any of the options with my PDK 0.8.1.
Also while creating build configuration i think there is a mistake with this warning:

While picking cpuapp only (so I presume secure) the warning is wrong. Should be for the /ns option

[Vidar Berg]

mojangeex said:

Tried 4 different options  secure and non secure with pdk and secure and non secure with dk.
It doesnt work on any of the options with my PDK 0.8.1.

Can you check the UART logs from the device to see if any runtime errors are reported? I have not been able to replicate the issue on my end.

mojangeex said:

While picking cpuapp only (so I presume secure) the warning is wrong. Should be for the /ns option

This may seem contradictory at first, but "ns" indicates that the application will run in the non-secure processing environment, enabling better isolation between the application program and secure code in the bootloader and TF-M.  An Introduction to Trusted Firmware-M (TF-M)