Using nRF54L15-DK from the command line?

RE: Using nRF54L15-DK from the command line?

jakkra — Mon, 16 Dec 2024 09:35:39 GMT

Hi, I have the same issue. Downloaded latest nrfjporg and nrfutil. Also manually downloaded latest SEGGER JLINK 8.1

Brand new unused nRF54L15 DK

jkra@SE-MLM-DT-JKRA MINGW64 ~
$ JLink.exe --version
SEGGER J-Link Commander V7.94e (Compiled Jan 15 2024 15:20:36)
DLL version V7.94e, compiled Jan 15 2024 15:18:46

Unknown command line option --version.

jkra@SE-MLM-DT-JKRA MINGW64 ~
$ nrfjprog --version
nrfjprog version: 10.24.2 external
JLinkARM.dll version: 7.94e

jkra@SE-MLM-DT-JKRA MINGW64 ~
$ nrfutil --version
nrfutil 7.13.0 (8289424 2024-07-01)
commit-hash: 82894242d19ff24a1541712312b3ea3af0ca8f85
commit-date: 2024-07-01
host: x86_64-pc-windows-msvc
build-timestamp: 2024-07-01T07:37:50.864803700Z
classification: nrf-external


jkra@SE-MLM-DT-JKRA MINGW64 ~
$ nrfutil device --version
nrfutil-device 2.3.6 (20652ac 2024-05-30)
commit-hash: 20652ac7e517947958af060dcb956b9de5fe5456
commit-date: 2024-05-30
host: x86_64-pc-windows-msvc
build-timestamp: 2024-05-30T11:22:18.696383800Z
classification: nrf-external


jkra@SE-MLM-DT-JKRA MINGW64 ~
$ nrfutil device program --firmware /c/Users/jkra/Downloads/FW_nRF54L15DK.hex --options chip_erase_mode=ERASE_ALL
[00:00:00] ------ 0% [1057716191] Failed, [Probe] Device error: Unknown devic
Error: One or more program tasks failed:
* 1057716191: [Probe] Device error: Unknown device: Unknown part number 0x0000001c and revision 0x00000001 , code: Generic

Latest JLink:

jkra@SE-MLM-DT-JKRA MINGW64 ~
$ JLink.exe --version
SEGGER J-Link Commander V8.10l (Compiled Dec 11 2024 16:03:18)
DLL version V8.10l, compiled Dec 11 2024 16:02:28

Unknown command line option --version.

jkra@SE-MLM-DT-JKRA MINGW64 ~
$ nrfutil --version
nrfutil 7.13.0 (8289424 2024-07-01)
commit-hash: 82894242d19ff24a1541712312b3ea3af0ca8f85
commit-date: 2024-07-01
host: x86_64-pc-windows-msvc
build-timestamp: 2024-07-01T07:37:50.864803700Z
classification: nrf-external


jkra@SE-MLM-DT-JKRA MINGW64 ~
$ nrfutil device --version
nrfutil-device 2.3.6 (20652ac 2024-05-30)
commit-hash: 20652ac7e517947958af060dcb956b9de5fe5456
commit-date: 2024-05-30
host: x86_64-pc-windows-msvc
build-timestamp: 2024-05-30T11:22:18.696383800Z
classification: nrf-external


jkra@SE-MLM-DT-JKRA MINGW64 ~
$ nrfutil device program --firmware /c/Users/jkra/Downloads/FW_nRF54L15DK.hex --options chip_erase_mode=ERASE_ALL
[00:00:00] ------ 0% [1057716191] Failed, [Probe] Device error: Unknown devic
Error: One or more program tasks failed:
* 1057716191: [Probe] Device error: Unknown device: Unknown part number 0x0000001c and revision 0x00000001 , code: Generic

EDIT: Apparently downloading nrfutil directly from Nordic Website does not give you the latest version.

After running nrfutil upgrade it fixed my problem.

RE: Using nRF54L15-DK from the command line?

Amanda Hsieh — Tue, 10 Dec 2024 20:44:46 GMT

Hi,

[quote user=""]Currently I have installed:
- nrfutil v7.5.0
- nrfutil-device v2.3.6[/quote]

Your nrfutil device version is a bit old, update with this command: nrfutil upgrade device. See Updating nRF Util and its commands.

Regards,
Amanda H.

RE: Using nRF54L15-DK from the command line?

hmolesworth — Tue, 10 Dec 2024 19:16:41 GMT

I used nrfjprog version 10.24.2; I think that is required for the nRF54 which can be downloaded from Segger as the latest release.

nrfjprog version: 10.24.2 external
JLinkARM.dll version: 7.94e

Also don't miss the BOOTCOMP step after the recover

nrfjprog --memwr 0x00FFD080 --val 0x00000003

// Set BOOTCONF (UICR offset 0x80) = 0x00000003
// nrfjprog --memrd 0x00FFD000
// nrfjprog --memrd 0x00FFD080
// nrfjprog --memrd 0xE000E000
// nrfjprog --memrd 0xE000ED00                     /* 410FD214 __CM33_REV=r0p4 SCB Offset: 0x000 CPUID Base Register */
// nrfjprog --memwr 0x00FFD080 --val 0x00000003    /* Set BOOTCONF (UICR offset 0x80) = 0x00000003 */
// Memory mapping of Core Hardware
//  SCS_BASE            (0xE000E000UL)                System Control Space Base Address
//  ITM_BASE            (0xE0000000UL)                ITM Base Address
//  DWT_BASE            (0xE0001000UL)                DWT Base Address
//  TPI_BASE            (0xE0040000UL)                TPI Base Address
//  CoreDebug_BASE      (0xE000EDF0UL)                Core Debug Base Address
//  SysTick_BASE        (SCS_BASE +  0x0010UL)        SysTick Base Address
//  NVIC_BASE           (SCS_BASE +  0x0100UL)        NVIC Base Address
//  SCB_BASE            (SCS_BASE +  0x0D00UL)        System Control Block Base Address

RE: Using nRF54L15-DK from the command line?

Jeremy — Tue, 10 Dec 2024 18:52:52 GMT

With nrfjprog (running 'nrfjprog --recover' as the most basic test), I get a different error:
```
ERROR: nrfjprog could not identify the target device. This may be due to an
ERROR: invalid family argument, a problem with your device, or nrfjprog may
ERROR: not yet support your device.
ERROR: Please check the family argument passed, or upgrade nrfjprog to a more
ERROR: recent version.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
```

Adding --log ('nrfjprog --recover --log') I get a bit more info:
```
ERROR: [ nRFXX] - Family identification failed.
ERROR: nrfjprog could not identify the target device. This may be due to an
ERROR: invalid family argument, a problem with your device, or nrfjprog may
ERROR: not yet support your device.
ERROR: Please check the family argument passed, or upgrade nrfjprog to a more
ERROR: recent version.
```

I'm running nrfjprog version 10.15.3 external, though this may be out of date. When I looked to see about updating it there are messages about it retiring so I focused on trying to get nrfutil updated and working.

Should I be trying to get nrfjprog updated and working, or is nrfutil the future and what I should focus on?

RE: Using nRF54L15-DK from the command line?

hmolesworth — Tue, 10 Dec 2024 17:29:31 GMT

Maybe try this 3-step sequence from the command line:

// nrf54L15 UICR Arm Cortex-M33
// ============================
// To program a hex file:
// In \Projects\Nordic\nRF5_SDK_17.1.0\examples\peripheral\blinky\pca10156\blank\iar\_build
nrfjprog --recover
nrfjprog --memwr 0x00FFD080 --val 0x00000003
nrfjprog --program blinky_pca10156.hex --chiperase --verify -r --log
// Example:
//    D:\Projects\Nordic\nRF5_SDK_17.1.0\examples\peripheral\blinky\pca10156\blank\iar\_build>nrfjprog --recover
//    Recovering device. This operation might take 30s.
//    Erasing user code and UICR flash areas.
//    D:\Projects\Nordic\nRF5_SDK_17.1.0\examples\peripheral\blinky\pca10156\blank\iar\_build>nrfjprog --memwr 0x00FFD080 --val 0x00000003
//    Parsing parameters.
//    Writing.
//    D:\Projects\Nordic\nRF5_SDK_17.1.0\examples\peripheral\blinky\pca10156\blank\iar\_build>nrfjprog --program blinky_pca10156.hex --chiperase --verify -r --log
//    [ #################### ]   0.263s | Erase file - Done erasing
//    [ #################### ]   0.197s | Program file - Done programming
//    [ #################### ]   0.072s | Verify file - Done verifying
//    Applying system reset.
//    Run.