Cannot flash using VSCode in nRF54L15 dev kit

RE: Cannot flash using VSCode in nRF54L15 dev kit

iek2443 — Fri, 28 Feb 2025 04:58:16 GMT

Hi,

You can download nrfutil from https://www.nordicsemi.com/Products/Development-tools/nRF-Util and move it to the "Scripts" folder inside Python. Then, open nRF Connect terminal in VS Code and run the following command to check if nrfutil is installed:

nrfutil --version

If this command returns a version number, it means nrfutil is successfully installed. Next, you can run the following command to install the device:

nrfutil install device

After completing these steps, the issue should be resolved.

Thanks,

iek

RE: Cannot flash using VSCode in nRF54L15 dev kit

mojangeex — Mon, 09 Dec 2024 11:02:33 GMT

This worked for me, thank you.
Nrfutil has multiple versions, on github, pip, nordic website... which is confusing specially if you have previous ones installed.

RE: Cannot flash using VSCode in nRF54L15 dev kit

FMistrorigo — Thu, 28 Nov 2024 07:55:40 GMT

Ok, found the problem...

In the DevAcademy they skip some important steps, I removed everything that was possibly messing around and at this point finally I encountered this error:
"Error: nrfutil command `device` not found. See `nrfutil list` for full list of installed commands, `nrfutil search` for installable commands, and `nrfutil install` for installation of new commands."

Running "nrfutil --version" in cmd confirmed that I was finally using nrfutil 7.13.0

At this point i was able to run "nrfutil search" to see the downloadable commands.

After: "nrfutil install completion", "nrfutil install device" and "nrfutil install nrf5sdk-tools", the flashing process worked...

Follow this guide nRF Util - nordicsemi.com, it was so simple....

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Wed, 27 Nov 2024 16:14:37 GMT

Hi,

You should be using nrfutil version 7 or above (https://www.nordicsemi.com/Products/Development-tools/nRF-Util). Previous versions don't support programming. It also does not have any dependencies on Python.

West and Python are bundled with the Toolchain. It doesn't seem like they are related to the issue you're facing.

[quote userid="138252" url="~/f/nordic-q-a/116601/cannot-flash-using-vscode-in-nrf54l15-dev-kit/512420"]I really can't figure out why in the Desktop app everything works but in the VSCode extension I have problems.[/quote]

I would be nice if you could debug the application without TF-M similar to what you did with TF-M earlier to see where the program hangs.

I still haven't been able to reproduce these issues here.

RE: Cannot flash using VSCode in nRF54L15 dev kit

FMistrorigo — Wed, 27 Nov 2024 15:56:26 GMT

Hi,

I was wondering if you can provide the version of everything I need, I noticed that for someone else Python 3.10.x caused problems, maybe the version of nrfutil, west, JLink or someting else is wrong...

(I already changed nrfutil version from 5.2.0 to 5.0.0 after finding problems with python)

I really can't figure out why in the Desktop app everything works but in the VSCode extension I have problems.

This problem is slowing the development process.

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Wed, 27 Nov 2024 12:02:30 GMT

Hi,

The current nrfutil device and nrfjprog versions are tested and validated with JLink_V7.94i, but this does not mean it has to be incompatible with never versions of Jlink. I have JLink_V8.10f installed on my system, and have not experienced any issues.

Testing blinky sample with SDK v2.8.0 with nRF54LDK (rev. 0.8.1)

Flashing (LED1 starts blinking after this point)

Debugging

But I see that there is a mismatch between Jlink GDB server version and the jlink library in your case. May be worth trying to have only one version of Jlink installed.

Edit:

Hex file from my build:

devzone.nordicsemi.com/.../8508.merged.hex

It can be programmed from the command line with nrfutil:

nrfutil device program --firmware merged.hex --options chip_erase_mode=ERASE_ALL,verify=VERIFY_READ,reset=RESET_SYSTEM

RE: Cannot flash using VSCode in nRF54L15 dev kit

FMistrorigo — Wed, 27 Nov 2024 11:29:52 GMT

Hi, I noticed that I was using V8.10 of JLinkARM.dll, I updated it to be the version that it needs to be V7.94i but nothing changed.

In the tutorial it says: "nRF Command Line Tools are needed to install the SEGGER J-Link package, which is a requirement to flash firmware to your board." so I think that maybe the usage of the version 7.94i is a new thing and maybe for new users it breaks the flashing process in the extension.

RE: Cannot flash using VSCode in nRF54L15 dev kit

FMistrorigo — Tue, 26 Nov 2024 08:08:46 GMT

Hi,

Board revision is 0.8.1, I tryied to build and flash also the Blink PWM example and the matter weather station example, none of them worked.

I will try to use the pheipheral_lbs example as soon as possible, but currently I have also other things to do.

The debug without TF-M doesn't work.

With the build configuration ns:

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Mon, 25 Nov 2024 13:46:40 GMT

FMistrorigo , what board revision of the nRF54L development board are you using, what happens when you debug the application without TF-M, and have you tried to see if you are able to run any of the other SDK samples that have been tested for the 54L15DK (e.g., peripheral_lbs example in nrf/samples/bluetooth).

[quote userid="81950" url="~/f/nordic-q-a/116601/cannot-flash-using-vscode-in-nrf54l15-dev-kit/511736"]Also nRF Connect for desktop, reading device memory fails here is the log:[/quote]

You can view the core registers in the top right corner. The xPSR register will tell which ISR number this interrupt vector has.

RE: Cannot flash using VSCode in nRF54L15 dev kit

mojangeex — Fri, 22 Nov 2024 17:16:48 GMT

I dont think it even starts. If I pause it its always on same address.

Also nRF Connect for desktop, reading device memory fails here is the log:

2024-11-22T12:43:10.278Z INFO Initialising the bundled nrfutil device
2024-11-22T12:43:10.322Z DEBUG Application data folder: C:\Users\bor.buh\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2024-11-22T12:43:10.354Z DEBUG App pc-nrfconnect-programmer v4.4.2 (official)
2024-11-22T12:43:10.354Z DEBUG App path: C:\Users\bor.buh\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2024-11-22T12:43:10.355Z DEBUG nRFConnect 5.1.0, required by the app is (>=5.0.2)
2024-11-22T12:43:10.355Z DEBUG nRFConnect path: C:\Users\bor.buh\AppData\Local\Programs\nrfconnect\resources\app.asar
2024-11-22T12:43:10.355Z DEBUG HomeDir: C:\Users\bor.buh
2024-11-22T12:43:10.355Z DEBUG TmpDir: C:\Users\bor.buh\AppData\Local\Temp
2024-11-22T12:43:11.326Z INFO Using the bundled core version for nrfutil device: 7.13.0
2024-11-22T12:43:11.616Z INFO Using nrfutil-device version: 2.6.4
2024-11-22T12:43:11.617Z INFO Using nrf-device-lib version: 0.17.35
2024-11-22T12:43:11.617Z INFO Using nrfjprog DLL version: 10.24.2
2024-11-22T12:43:11.617Z INFO Using JLink version: JLink_V7.94i
2024-11-22T12:43:11.837Z INFO Getting serial port options from the persistent store for FTWXT38G.pc-nrfconnect-programmer
2024-11-22T12:43:11.837Z INFO Getting serial port options from the persistent store for 001050337463.pc-nrfconnect-programmer
2024-11-22T12:43:21.554Z INFO Selecting device with the serial number 001050337463
2024-11-22T12:43:22.811Z INFO Selected device with the serial number 001050337463
2024-11-22T12:43:22.812Z INFO Using nrfutil device to communicate with target via JLink
2024-11-22T12:43:22.812Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Oct  9 2024 11:01:34
2024-11-22T12:43:22.813Z INFO Device family NRF52_FAMILY
2024-11-22T12:43:22.813Z INFO Device version 
2024-11-22T12:43:22.813Z INFO Board version PCA10040
2024-11-22T12:43:23.817Z INFO Reading readback protection status for Application core
2024-11-22T12:43:23.818Z INFO Reading readback protection status for Application core 0%
2024-11-22T12:43:23.824Z INFO Reading readback protection status for Application core 100%
2024-11-22T12:43:23.824Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_ALL'
2024-11-22T12:43:23.825Z INFO Reading readback protection status for Application core completed
2024-11-22T12:43:24.076Z INFO Skipping reading core Application information as it is protected.
2024-11-22T12:43:26.296Z INFO Reading readback protection status for Application core
2024-11-22T12:43:26.297Z INFO Reading readback protection status for Application core 0%
2024-11-22T12:43:26.302Z INFO Reading readback protection status for Application core 100%
2024-11-22T12:43:26.302Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_ALL'
2024-11-22T12:43:26.303Z INFO Reading readback protection status for Application core completed
2024-11-22T12:43:26.555Z INFO Device is loaded and ready for further operation
2024-11-22T12:44:14.965Z INFO Reading readback protection status for Application core
2024-11-22T12:44:14.965Z INFO Reading readback protection status for Application core 0%
2024-11-22T12:44:14.972Z INFO Reading readback protection status for Application core 100%
2024-11-22T12:44:14.972Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_ALL'
2024-11-22T12:44:14.972Z INFO Reading readback protection status for Application core completed
2024-11-22T12:54:15.346Z INFO Parsing HEX file:  C:\Users\bor.buh\Documents\BT45\BT45\_build\fullpackage_app.hex
2024-11-22T12:54:15.366Z INFO File was last modified at  02/04/2024, 19:11:56
2024-11-22T12:54:15.533Z INFO Update files regions according to Application core
2024-11-22T12:54:15.533Z INFO Parse memory regions for file
2024-11-22T12:54:15.535Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T12:54:22.202Z INFO Recovering Application core
2024-11-22T12:54:22.202Z INFO Recovering Application core 0%
2024-11-22T12:54:23.361Z INFO Recovering Application core 100%
2024-11-22T12:54:23.362Z INFO Recovering Application core completed
2024-11-22T12:54:23.362Z INFO Writing HEX to Application core
2024-11-22T12:54:23.520Z INFO Writing HEX to Application core 33%
2024-11-22T12:54:23.520Z INFO Writing HEX to Application core 33%
2024-11-22T12:54:23.521Z INFO Writing HEX to Application core 67%
2024-11-22T12:54:23.598Z INFO Writing HEX to Application core 44%
2024-11-22T12:54:23.598Z INFO Writing HEX to Application core 37%
2024-11-22T12:54:23.599Z INFO Writing HEX to Application core 40%
2024-11-22T12:54:23.599Z INFO Writing HEX to Application core 43%
2024-11-22T12:54:23.609Z INFO Writing HEX to Application core 47%
2024-11-22T12:54:23.609Z INFO Writing HEX to Application core 50%
2024-11-22T12:54:23.620Z INFO Writing HEX to Application core 53%
2024-11-22T12:54:23.620Z INFO Writing HEX to Application core 57%
2024-11-22T12:54:23.631Z INFO Writing HEX to Application core 60%
2024-11-22T12:54:23.632Z INFO Writing HEX to Application core 63%
2024-11-22T12:54:23.632Z INFO Writing HEX to Application core 67%
2024-11-22T12:54:23.632Z INFO Writing HEX to Application core 55%
2024-11-22T12:54:23.632Z INFO Writing HEX to Application core 37%
2024-11-22T12:54:23.696Z INFO Writing HEX to Application core 42%
2024-11-22T12:54:26.404Z INFO Writing HEX to Application core 46%
2024-11-22T12:54:28.206Z INFO Writing HEX to Application core 50%
2024-11-22T12:54:28.640Z INFO Writing HEX to Application core 54%
2024-11-22T12:54:28.651Z INFO Writing HEX to Application core 58%
2024-11-22T12:54:28.671Z INFO Writing HEX to Application core 67%
2024-11-22T12:54:28.671Z INFO Writing HEX to Application core 100%
2024-11-22T12:54:28.683Z INFO Writing HEX to Application core completed
2024-11-22T12:54:28.683Z INFO Loading core information for Application core
2024-11-22T12:54:28.684Z INFO Loading core information for Application core 0%
2024-11-22T12:54:28.686Z INFO Update files regions according to Application core
2024-11-22T12:54:28.686Z INFO Parse memory regions for file
2024-11-22T12:54:28.686Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T12:54:28.690Z INFO Loading core information for Application core 100%
2024-11-22T12:54:28.691Z INFO Loading core information for Application core completed
2024-11-22T12:54:28.694Z INFO Update files regions according to Application core
2024-11-22T12:54:28.694Z INFO Parse memory regions for file
2024-11-22T12:54:28.694Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T12:54:30.829Z INFO Reading readback protection status for Application core
2024-11-22T12:54:30.830Z INFO Reading readback protection status for Application core 0%
2024-11-22T12:54:30.836Z INFO Reading readback protection status for Application core 100%
2024-11-22T12:54:30.836Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T12:54:30.837Z INFO Reading readback protection status for Application core completed
2024-11-22T12:54:37.498Z INFO Reading memory for Application core
2024-11-22T12:54:37.501Z INFO Reading memory for Application core 0%
2024-11-22T12:54:41.112Z INFO Reading memory for Application core 100%
2024-11-22T12:54:41.323Z INFO Reading memory for Application core completed
2024-11-22T12:54:41.326Z INFO Parse memory regions for Application core
2024-11-22T12:54:44.116Z INFO Deselected device
2024-11-22T12:54:44.122Z INFO Update files regions according to Application core
2024-11-22T12:54:44.122Z INFO Parse memory regions for file
2024-11-22T12:54:44.122Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T12:55:00.519Z INFO Selecting device with the serial number 001050337463
2024-11-22T12:55:01.627Z INFO Selected device with the serial number 001050337463
2024-11-22T12:55:01.628Z INFO Using nrfutil device to communicate with target via JLink
2024-11-22T12:55:01.628Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Oct  9 2024 11:01:34
2024-11-22T12:55:01.628Z INFO Device family NRF52_FAMILY
2024-11-22T12:55:01.628Z INFO Device version NRF52832_xxAA_REV3
2024-11-22T12:55:01.628Z INFO Board version PCA10040
2024-11-22T12:55:01.634Z INFO Update files regions according to Application core
2024-11-22T12:55:01.634Z INFO Parse memory regions for file
2024-11-22T12:55:01.634Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T12:55:02.525Z INFO Reading readback protection status for Application core
2024-11-22T12:55:02.526Z INFO Reading readback protection status for Application core 0%
2024-11-22T12:55:02.533Z INFO Reading readback protection status for Application core 100%
2024-11-22T12:55:02.533Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T12:55:02.533Z INFO Reading readback protection status for Application core completed
2024-11-22T12:55:03.652Z INFO Loading core information for Application core
2024-11-22T12:55:03.652Z INFO Loading core information for Application core 0%
2024-11-22T12:55:03.654Z INFO Update files regions according to Application core
2024-11-22T12:55:03.654Z INFO Parse memory regions for file
2024-11-22T12:55:03.654Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T12:55:03.686Z INFO Loading core information for Application core 100%
2024-11-22T12:55:03.687Z INFO Loading core information for Application core completed
2024-11-22T12:55:03.689Z INFO Update files regions according to Application core
2024-11-22T12:55:03.689Z INFO Parse memory regions for file
2024-11-22T12:55:03.689Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T12:55:04.785Z INFO Reading readback protection status for Application core
2024-11-22T12:55:04.785Z INFO Reading readback protection status for Application core 0%
2024-11-22T12:55:04.790Z INFO Reading readback protection status for Application core 100%
2024-11-22T12:55:04.790Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T12:55:04.791Z INFO Reading readback protection status for Application core completed
2024-11-22T12:55:05.003Z INFO Device is loaded and ready for further operation
2024-11-22T12:55:10.053Z INFO Reading memory for Application core
2024-11-22T12:55:10.057Z INFO Reading memory for Application core 0%
2024-11-22T12:55:13.659Z INFO Reading memory for Application core 100%
2024-11-22T12:55:13.846Z INFO Reading memory for Application core completed
2024-11-22T12:55:13.847Z INFO Parse memory regions for Application core
2024-11-22T12:55:25.132Z INFO Recovering Application core
2024-11-22T12:55:25.133Z INFO Recovering Application core 0%
2024-11-22T12:55:26.290Z INFO Recovering Application core 100%
2024-11-22T12:55:26.290Z INFO Recovering Application core completed
2024-11-22T12:55:26.293Z INFO Loading core information for Application core
2024-11-22T12:55:26.294Z INFO Loading core information for Application core 0%
2024-11-22T12:55:26.296Z INFO Update files regions according to Application core
2024-11-22T12:55:26.296Z INFO Parse memory regions for file
2024-11-22T12:55:26.296Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T12:55:26.308Z INFO Loading core information for Application core 100%
2024-11-22T12:55:26.308Z INFO Loading core information for Application core completed
2024-11-22T12:55:26.310Z INFO Update files regions according to Application core
2024-11-22T12:55:26.310Z INFO Parse memory regions for file
2024-11-22T12:55:26.311Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T12:55:28.520Z INFO Reading readback protection status for Application core
2024-11-22T12:55:28.520Z INFO Reading readback protection status for Application core 0%
2024-11-22T12:55:28.524Z INFO Reading readback protection status for Application core 100%
2024-11-22T12:55:28.524Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T12:55:28.524Z INFO Reading readback protection status for Application core completed
2024-11-22T13:02:49.003Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T13:02:49.460Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T13:02:49.892Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T13:16:12.770Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T13:16:13.248Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T13:16:13.655Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T13:16:45.713Z INFO Deselected device
2024-11-22T13:16:45.720Z INFO Update files regions according to Application core
2024-11-22T13:16:45.720Z INFO Parse memory regions for file
2024-11-22T13:16:45.720Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T13:20:07.131Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T13:20:07.137Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T13:20:07.633Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T13:25:08.027Z INFO Selecting device with the serial number 001057739708
2024-11-22T13:25:08.952Z INFO Selected device with the serial number 001057739708
2024-11-22T13:25:08.953Z INFO Using nrfutil device to communicate with target via JLink
2024-11-22T13:25:08.953Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Oct  9 2024 11:01:34
2024-11-22T13:25:08.953Z INFO Device family NRF54L_FAMILY
2024-11-22T13:25:08.953Z INFO Device version NRF54L15_xxAA_ENGB
2024-11-22T13:25:08.953Z INFO Board version PCA10156
2024-11-22T13:25:09.674Z INFO Reading readback protection status for Application core
2024-11-22T13:25:09.675Z INFO Reading readback protection status for Application core 0%
2024-11-22T13:25:09.690Z INFO Reading readback protection status for Application core 100%
2024-11-22T13:25:09.690Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T13:25:09.691Z INFO Reading readback protection status for Application core completed
2024-11-22T13:25:10.687Z INFO Loading core information for Application core
2024-11-22T13:25:10.688Z INFO Loading core information for Application core 0%
2024-11-22T13:25:10.690Z INFO Update files regions according to Application core
2024-11-22T13:25:10.690Z INFO Parse memory regions for file
2024-11-22T13:25:10.690Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T13:25:10.697Z INFO Loading core information for Application core 100%
2024-11-22T13:25:10.697Z INFO Loading core information for Application core completed
2024-11-22T13:25:10.699Z INFO Update files regions according to Application core
2024-11-22T13:25:10.699Z INFO Parse memory regions for file
2024-11-22T13:25:10.701Z INFO SoftDevice detected, id 0x101 (S132 v7.2.0)
2024-11-22T13:25:11.847Z INFO Reading readback protection status for Application core
2024-11-22T13:25:11.847Z INFO Reading readback protection status for Application core 0%
2024-11-22T13:25:11.862Z INFO Reading readback protection status for Application core 100%
2024-11-22T13:25:11.862Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T13:25:11.863Z INFO Reading readback protection status for Application core completed
2024-11-22T13:25:12.074Z INFO Device is loaded and ready for further operation
2024-11-22T13:25:18.161Z INFO Reading memory for Application core
2024-11-22T13:25:26.819Z INFO Reading memory for Application core
2024-11-22T13:26:23.258Z INFO Getting serial port options from the persistent store for 001050337463.pc-nrfconnect-programmer
2024-11-22T13:26:23.624Z INFO Getting serial port options from the persistent store for 001050337463.pc-nrfconnect-programmer
2024-11-22T13:26:24.089Z INFO Getting serial port options from the persistent store for 001050337463.pc-nrfconnect-programmer
2024-11-22T13:26:43.269Z INFO Deselected device
2024-11-22T13:26:46.464Z INFO Selecting device with the serial number 001050337463
2024-11-22T13:26:47.587Z INFO Selected device with the serial number 001050337463
2024-11-22T13:26:47.587Z INFO Using nrfutil device to communicate with target via JLink
2024-11-22T13:26:47.587Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Oct  9 2024 11:01:34
2024-11-22T13:26:47.587Z INFO Device family NRF52_FAMILY
2024-11-22T13:26:47.587Z INFO Device version NRF52832_xxAA_REV3
2024-11-22T13:26:47.587Z INFO Board version PCA10040
2024-11-22T13:26:48.529Z INFO Reading readback protection status for Application core
2024-11-22T13:26:48.529Z INFO Reading readback protection status for Application core 0%
2024-11-22T13:26:48.535Z INFO Reading readback protection status for Application core 100%
2024-11-22T13:26:48.535Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T13:26:48.535Z INFO Reading readback protection status for Application core completed
2024-11-22T13:26:49.650Z INFO Loading core information for Application core
2024-11-22T13:26:49.651Z INFO Loading core information for Application core 0%
2024-11-22T13:26:49.687Z INFO Loading core information for Application core 100%
2024-11-22T13:26:49.687Z INFO Loading core information for Application core completed
2024-11-22T13:26:50.783Z INFO Reading readback protection status for Application core
2024-11-22T13:26:50.783Z INFO Reading readback protection status for Application core 0%
2024-11-22T13:26:50.789Z INFO Reading readback protection status for Application core 100%
2024-11-22T13:26:50.790Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T13:26:50.790Z INFO Reading readback protection status for Application core completed
2024-11-22T13:26:51.076Z INFO Device is loaded and ready for further operation
2024-11-22T13:26:55.879Z INFO Reading memory for Application core
2024-11-22T13:26:55.880Z INFO Reading memory for Application core 0%
2024-11-22T13:26:59.503Z INFO Reading memory for Application core 100%
2024-11-22T13:26:59.720Z INFO Reading memory for Application core completed
2024-11-22T13:26:59.721Z INFO Parse memory regions for Application core
2024-11-22T13:27:02.597Z INFO Deselected device
2024-11-22T13:27:04.937Z INFO Selecting device with the serial number 001057739708
2024-11-22T13:27:05.832Z INFO Selected device with the serial number 001057739708
2024-11-22T13:27:05.833Z INFO Using nrfutil device to communicate with target via JLink
2024-11-22T13:27:05.833Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Oct  9 2024 11:01:34
2024-11-22T13:27:05.833Z INFO Device family NRF54L_FAMILY
2024-11-22T13:27:05.833Z INFO Device version NRF54L15_xxAA_ENGB
2024-11-22T13:27:05.833Z INFO Board version PCA10156
2024-11-22T13:27:06.569Z INFO Reading readback protection status for Application core
2024-11-22T13:27:06.570Z INFO Reading readback protection status for Application core 0%
2024-11-22T13:27:06.587Z INFO Reading readback protection status for Application core 100%
2024-11-22T13:27:06.588Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T13:27:06.588Z INFO Reading readback protection status for Application core completed
2024-11-22T13:27:07.550Z INFO Loading core information for Application core
2024-11-22T13:27:07.551Z INFO Loading core information for Application core 0%
2024-11-22T13:27:07.560Z INFO Loading core information for Application core 100%
2024-11-22T13:27:07.560Z INFO Loading core information for Application core completed
2024-11-22T13:27:08.545Z INFO Reading readback protection status for Application core
2024-11-22T13:27:08.545Z INFO Reading readback protection status for Application core 0%
2024-11-22T13:27:08.560Z INFO Reading readback protection status for Application core 100%
2024-11-22T13:27:08.561Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T13:27:08.561Z INFO Reading readback protection status for Application core completed
2024-11-22T13:27:08.717Z INFO Device is loaded and ready for further operation
2024-11-22T13:27:12.539Z INFO Reading memory for Application core
2024-11-22T13:27:22.662Z INFO Reading memory for Application core
2024-11-22T13:27:25.951Z INFO Deselected device
2024-11-22T13:27:27.683Z INFO Selecting device with the serial number 001050337463
2024-11-22T13:27:28.780Z INFO Selected device with the serial number 001050337463
2024-11-22T13:27:28.780Z INFO Using nrfutil device to communicate with target via JLink
2024-11-22T13:27:28.780Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Oct  9 2024 11:01:34
2024-11-22T13:27:28.781Z INFO Device family NRF52_FAMILY
2024-11-22T13:27:28.781Z INFO Device version NRF52832_xxAA_REV3
2024-11-22T13:27:28.781Z INFO Board version PCA10040
2024-11-22T13:27:29.679Z INFO Reading readback protection status for Application core
2024-11-22T13:27:29.680Z INFO Reading readback protection status for Application core 0%
2024-11-22T13:27:29.683Z INFO Reading readback protection status for Application core 100%
2024-11-22T13:27:29.684Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T13:27:29.684Z INFO Reading readback protection status for Application core completed
2024-11-22T13:27:30.896Z INFO Loading core information for Application core
2024-11-22T13:27:30.897Z INFO Loading core information for Application core 0%
2024-11-22T13:27:30.935Z INFO Loading core information for Application core 100%
2024-11-22T13:27:30.935Z INFO Loading core information for Application core completed
2024-11-22T13:27:32.094Z INFO Reading readback protection status for Application core
2024-11-22T13:27:32.096Z INFO Reading readback protection status for Application core 0%
2024-11-22T13:27:32.103Z INFO Reading readback protection status for Application core 100%
2024-11-22T13:27:32.103Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T13:27:32.103Z INFO Reading readback protection status for Application core completed
2024-11-22T13:27:32.369Z INFO Device is loaded and ready for further operation
2024-11-22T13:27:35.291Z INFO Reading memory for Application core
2024-11-22T13:27:35.294Z INFO Reading memory for Application core 0%
2024-11-22T13:27:38.907Z INFO Reading memory for Application core 100%
2024-11-22T13:27:39.122Z INFO Reading memory for Application core completed
2024-11-22T13:27:39.123Z INFO Parse memory regions for Application core
2024-11-22T13:27:42.256Z INFO Deselected device
2024-11-22T14:26:15.514Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T14:26:16.414Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T14:26:17.002Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T17:10:14.016Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T17:10:14.433Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T17:10:14.915Z INFO Getting serial port options from the persistent store for 001057739708.pc-nrfconnect-programmer
2024-11-22T17:12:48.979Z INFO Selecting device with the serial number 001057739708
2024-11-22T17:12:50.071Z INFO Selected device with the serial number 001057739708
2024-11-22T17:12:50.072Z INFO Using nrfutil device to communicate with target via JLink
2024-11-22T17:12:50.072Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Oct  9 2024 11:01:34
2024-11-22T17:12:50.072Z INFO Device family NRF54L_FAMILY
2024-11-22T17:12:50.072Z INFO Device version NRF54L15_xxAA_ENGB
2024-11-22T17:12:50.072Z INFO Board version PCA10156
2024-11-22T17:12:50.888Z INFO Reading readback protection status for Application core
2024-11-22T17:12:50.889Z INFO Reading readback protection status for Application core 0%
2024-11-22T17:12:50.904Z INFO Reading readback protection status for Application core 100%
2024-11-22T17:12:50.904Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T17:12:50.905Z INFO Reading readback protection status for Application core completed
2024-11-22T17:12:51.867Z INFO Loading core information for Application core
2024-11-22T17:12:51.868Z INFO Loading core information for Application core 0%
2024-11-22T17:12:51.877Z INFO Loading core information for Application core 100%
2024-11-22T17:12:51.877Z INFO Loading core information for Application core completed
2024-11-22T17:12:52.927Z INFO Reading readback protection status for Application core
2024-11-22T17:12:52.928Z INFO Reading readback protection status for Application core 0%
2024-11-22T17:12:52.943Z INFO Reading readback protection status for Application core 100%
2024-11-22T17:12:52.943Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T17:12:52.943Z INFO Reading readback protection status for Application core completed
2024-11-22T17:12:53.127Z INFO Device is loaded and ready for further operation
2024-11-22T17:13:10.041Z INFO Deselected device
2024-11-22T17:13:12.074Z INFO Selecting device with the serial number 001057739708
2024-11-22T17:13:12.966Z INFO Selected device with the serial number 001057739708
2024-11-22T17:13:12.966Z INFO Using nrfutil device to communicate with target via JLink
2024-11-22T17:13:12.966Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Oct  9 2024 11:01:34
2024-11-22T17:13:12.966Z INFO Device family NRF54L_FAMILY
2024-11-22T17:13:12.966Z INFO Device version NRF54L15_xxAA_ENGB
2024-11-22T17:13:12.966Z INFO Board version PCA10156
2024-11-22T17:13:13.678Z INFO Reading readback protection status for Application core
2024-11-22T17:13:13.679Z INFO Reading readback protection status for Application core 0%
2024-11-22T17:13:13.703Z INFO Reading readback protection status for Application core 100%
2024-11-22T17:13:13.703Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T17:13:13.703Z INFO Reading readback protection status for Application core completed
2024-11-22T17:13:14.675Z INFO Loading core information for Application core
2024-11-22T17:13:14.676Z INFO Loading core information for Application core 0%
2024-11-22T17:13:14.685Z INFO Loading core information for Application core 100%
2024-11-22T17:13:14.686Z INFO Loading core information for Application core completed
2024-11-22T17:13:15.717Z INFO Reading readback protection status for Application core
2024-11-22T17:13:15.718Z INFO Reading readback protection status for Application core 0%
2024-11-22T17:13:15.734Z INFO Reading readback protection status for Application core 100%
2024-11-22T17:13:15.734Z INFO Application core protection status 'NRFDL_PROTECTION_STATUS_NONE'
2024-11-22T17:13:15.734Z INFO Reading readback protection status for Application core completed
2024-11-22T17:13:15.912Z INFO Device is loaded and ready for further operation
2024-11-22T17:13:50.683Z INFO Reading memory for Application core

And read buttond doesnt change anything:

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Fri, 22 Nov 2024 17:06:15 GMT

In that case, please try to debug the application in VS code (use nrf54l15dk/nrf54l15/cpuapp) as FMistrorigo did above to see where the program hangs.

EDIT: have you tried any of the other SDK examples to see if they work? For example, the peripheral_lbs example in nrf/samples/bluetooth?

RE: Cannot flash using VSCode in nRF54L15 dev kit

mojangeex — Fri, 22 Nov 2024 17:03:30 GMT

I am using v2.8.0

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Fri, 22 Nov 2024 16:53:14 GMT

[quote userid="81950" url="~/f/nordic-q-a/116601/cannot-flash-using-vscode-in-nrf54l15-dev-kit/511703"]Nohing shows up on any of them, not while programming not after manual reset with button.[/quote]

Are you using SDK v2.7.0 by chance? In this version, the UART instances had hardware flow control enabled by default, which could block the UART console. This issue was addressed in SDK v2.8.0, and is the recommended version for developing with the nRF54L15DK.

Workaround if on v2.7.0 is to create a devicetree overlay to disable flow control. The overlay must contain the following:

&uart20 {
    /delete-property/ hw-flow-control;
};

And the must be named either nrf54l15pdk_nrf54l15_cpuapp_ns.overlay or nrf54l15pdk_nrf54l15_cpuapp.overlay and placed in your project root or <project root>/boards directory. You also need to perform a pristine build after it as been added to be detected by the build system.

RE: Cannot flash using VSCode in nRF54L15 dev kit

mojangeex — Fri, 22 Nov 2024 14:59:23 GMT

Nohing shows up on any of them, not while programming not after manual reset with button.

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Fri, 22 Nov 2024 14:54:13 GMT

You can view the logs in VS code by opening the nRF Serial terminal as shown below. The Jlink on the DK will expose 2 COM ports, one for each UART instance.

RE: Cannot flash using VSCode in nRF54L15 dev kit

mojangeex — Fri, 22 Nov 2024 14:51:01 GMT

How do i check the UART logs?
Only thing i get is this:

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Fri, 22 Nov 2024 14:45:28 GMT

[quote userid="81950" url="~/f/nordic-q-a/116601/cannot-flash-using-vscode-in-nrf54l15-dev-kit/511692"]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.[/quote]

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.

[quote userid="81950" url="~/f/nordic-q-a/116601/cannot-flash-using-vscode-in-nrf54l15-dev-kit/511692"]While picking cpuapp only (so I presume secure) the warning is wrong. Should be for the /ns option[/quote]

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)

RE: Cannot flash using VSCode in nRF54L15 dev kit

mojangeex — Fri, 22 Nov 2024 14:37:04 GMT

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

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Fri, 22 Nov 2024 14:32:43 GMT

[quote userid="138252" url="~/f/nordic-q-a/116601/cannot-flash-using-vscode-in-nrf54l15-dev-kit/511689"]I already tryied to do that but without success, everything is the same,[/quote]

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?

RE: Cannot flash using VSCode in nRF54L15 dev kit

FMistrorigo — Fri, 22 Nov 2024 14:30:36 GMT

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.

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Fri, 22 Nov 2024 13:50:25 GMT

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

RE: Cannot flash using VSCode in nRF54L15 dev kit

mojangeex — Fri, 22 Nov 2024 13:44:37 GMT

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.

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Thu, 21 Nov 2024 14:54:21 GMT

Both TF-M and the main app will be included in the merged.hex file. It looks like the Programmer app has not been updated to support the nRF54L yet, but running the "Memory report" action will give a more accurate representation of the memory layout. Either way, it seems like there is an issue with the configuration of the TF-M image. A workaround for now if you wish to build with TF-M is to add CONFIG_TFM_PROFILE_TYPE_MINIMAL=y to your project configuration file.

RE: Cannot flash using VSCode in nRF54L15 dev kit

FMistrorigo — Thu, 21 Nov 2024 14:32:08 GMT

It probably throws the error because ther's no program in the board, the "Erase and flash board" only removed the firmware but did't flash it back.
I will try the other build as suggested.

PS. Does the nRF54L15 support the "Read" functionality in the Desktop app, It can be helpfull to understand what happens in the flash.
Now I'm getting this error: "Error: Failed with exit code 1. One or more batch tasks failed: - [Probe] The fw-read operation is not supported, code: Generic. Message: Batch task fw-read failed, [Probe] The fw-read operation is not supported."

RE: Cannot flash using VSCode in nRF54L15 dev kit

Vidar Berg — Thu, 21 Nov 2024 14:27:10 GMT

The screenshot shows that an error was raised in TF-M before the program reached the main app. I suggest you try with the nrf54l15dk/nrf54l15/cpuapp build target (does not include TF-M) and see if that works to help narrow down the problem.