Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

sakumasss — Fri, 21 Nov 2025 03:25:42 GMT

Thanks for your useful sharing!

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

herrtylee — Tue, 14 Oct 2025 09:30:22 GMT

Stickman Boost Unblocked refers to a version of the game that bypasses these restrictions, allowing players to enjoy the game on school or office networks.

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

Luna Harris — Sat, 11 Oct 2025 14:24:34 GMT

The error usually happens because JLinkExe is connecting to the non-secure domain on Cortex-M33 chips, while your hex file targets the secure ulyagames region. Try connecting with the correct Nordic device name (e.g., nRF5340_xxAA_APP) or switching to the secure domain in JLinkExe. If that doesn’t work, downgrade your J-Link software to a stable version like V7.92i, as newer releases sometimes cause flash write issues on macOS.

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

sh4k3jkeee — Tue, 23 Sep 2025 11:35:27 GMT

After erasing the device, you may need to reset the target energywisesystems or reinitialize the connection before loading the file.

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

playground — Fri, 29 Aug 2025 04:52:07 GMT

When playing Melon Playground, imagination rules the world, whether you’re creating epic explosions or silly interactions between characters and strange machines. Melon Playground

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

colormania — Wed, 06 Aug 2025 03:18:05 GMT

Seeing consistent 100% load on a single core during find & replace confirms that even basic operations aren’t taking advantage of multithreading yet. color rush game

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

junbon — Thu, 24 Jul 2025 06:40:25 GMT

Hi Dennis,

It sounds like you’re encountering a common issue when using JLinkExe. After erasing the device, you may need to reset the target or reinitialize the connection before loading the file. Try adding a command to reset the device after the erase step but before the loadfile command. You can do this by using the r command to reset the device. Here’s a quick example:

Copy
JLinkExe -device NRF5340_XXAA_APP -if swd -speed 4000
erase
r
loadfile yourfile.hex

This should help you perform both operations within the same session without securing the device. Let me know if this resolves your issue!

Best,
[Snow Rider]

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

tag game — Sat, 26 Apr 2025 04:38:20 GMT

Hi Asbjørn, thank you for your insights. I’ll check the pin reset issue and ensure proper target selection. Best, Dennis.

tag game

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

fnfweek — Wed, 22 Jan 2025 09:09:12 GMT

thank you

Stickman Hook

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

Asbjørn — Mon, 20 Jan 2025 12:51:38 GMT

Hi Dennis,

the target selection might have worked for a while, but if I recall correctly, once the specific target is available in j-link it might not support the generic option selection that Coretx-M33 even though it is a Coretx-M33.

I'm not entirely sure what and how Segger does their steps, it should work. The description you mention of needing to exit jlink.exe between erase and loadfile indicates that there's a need for a pinreset of the device that isn't supplied when the device stays connected after the erase.

Best regards

Asbjørn

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

munsie — Fri, 17 Jan 2025 19:27:29 GMT

Hi Asbjørn --

The reason I hadn't specified the APP CPU was because we previously didn't need to do so. I just tried with the following command line instead:

JLinkExe -device NRF5340_XXAA_APP -if swd -speed 4000

And was able to successfully erase the device, but when I went to do a loadfile, it failed with this:

SEGGER J-Link Commander V8.12b (Compiled Jan 15 2025 13:47:46)
DLL version V8.12b, compiled Jan 15 2025 13:47:14

Connecting to J-Link via USB...O.K.
Firmware: J-Link V11 compiled Dec  4 2024 17:53:35
Hardware version: V11.00
J-Link uptime (since boot): 0d 00h 00m 05s
S/N: 51025827
License(s): GDB
USB speed mode: High speed (480 MBit/s)
VTref=1.794V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Device "NRF5340_XXAA_APP" selected.


Connecting to target via SWD
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 7us
InitTarget() start
Device will be unsecured now.
InitTarget() end - Took 2.36s
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[1]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[3]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FE000
CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)
Feature set: Mainline
Cache: No cache
Found Cortex-M33 r0p4, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
Security extension: implemented
Secure debug: enabled
CoreSight components:
ROMTbl[0] @ E00FE000
[0][0]: E00FF000 CID B105100D PID 000BB4C9 ROM Table
ROMTbl[1] @ E00FF000
[1][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33
[1][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT
[1][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB
[1][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM
[1][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM
[1][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI
[0][1]: E0040000 CID B105900D PID 000BBD21 DEVARCH 00000000 DEVTYPE 11 TPIU
Memory zones:
  Zone: "Default" Description: Default access mode
Cortex-M33 identified.
J-Link>erase
No address range specified, 'Erase Chip' will be executed
'erase': Performing implicit reset & halt of MCU.
Reset type: NORMAL (https://wiki.segger.com/J-Link_Reset_Strategies)
Reset: ARMv8M core with Security Extension enabled detected. Switch to secure domain.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Erasing device...
J-Link: Flash download: Total time needed: 0.252s (Prepare: 0.023s, Compare: 0.000s, Erase: 0.216s, Program: 0.000s, Verify: 0.000s, Restore: 0.012s)
J-Link: Flash download: Total time needed: 0.248s (Prepare: 0.023s, Compare: 0.000s, Erase: 0.212s, Program: 0.000s, Verify: 0.000s, Restore: 0.012s)
J-Link: Flash download: Total time needed: 0.294s (Prepare: 0.048s, Compare: 0.000s, Erase: 0.208s, Program: 0.000s, Verify: 0.000s, Restore: 0.036s)
Erasing done.
J-Link>loadfile merged.hex
'loadfile': Performing implicit reset & halt of MCU.
Reset type: NORMAL (https://wiki.segger.com/J-Link_Reset_Strategies)
Reset: ARMv8M core with Security Extension enabled detected. Switch to secure domain.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Reset: SYSRESETREQ has confused core.
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[1]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[3]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[0]: Skipped. Could not read CPUID register
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
Reset: Using fallback: VECTRESET.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.VECTRESET.
Reset: VECTRESET has confused core.
Reset: Using fallback: Reset pin.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[1]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[3]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[0]: Skipped. Could not read CPUID register
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
CPU could not be halted
Reset: Core did not halt after reset, trying to disable WDT.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[1]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[3]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[0]: Skipped. Could not read CPUID register
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
CPU could not be halted
Reset: Failed. Toggling reset pin and trying reset strategy again.
Failed to attach to CPU. Trying connect under reset.
Found SW-DP with ID 0x6BA02477
SWD speed too high. Reduced from 4000 kHz to 2700 kHz for stability
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[1]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[3]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[0]: Skipped. Could not read CPUID register
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Reset: SYSRESETREQ has confused core.
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[1]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[3]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[0]: Skipped. Could not read CPUID register
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
Reset: Using fallback: VECTRESET.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.VECTRESET.
Reset: VECTRESET has confused core.
Reset: Using fallback: Reset pin.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[1]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[3]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[0]: Skipped. Could not read CPUID register
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
CPU could not be halted
Reset: Core did not halt after reset, trying to disable WDT.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[1]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[3]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
AP[0]: Skipped. Could not read CPUID register
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
CPU could not be halted
CPU could not be halted

****** Error: Failed to halt CPU.
CPU could not be halted
Downloading file [merged.hex]...
CPU could not be halted

****** Error: Failed to preserve target RAM @ 0x20000000-0x2007FFFF.
Failed to prepare for programming.
Cannot read register 16 (XPSR) while CPU is running
Cannot read register 20 (CFBP) while CPU is running
Cannot read register 0 (R0) while CPU is running
Cannot read register 1 (R1) while CPU is running
Cannot read register 2 (R2) while CPU is running
Cannot read register 3 (R3) while CPU is running
Cannot read register 4 (R4) while CPU is running
Cannot read register 5 (R5) while CPU is running
Cannot read register 6 (R6) while CPU is running
Cannot read register 7 (R7) while CPU is running
Cannot read register 8 (R8) while CPU is running
Cannot read register 9 (R9) while CPU is running
Cannot read register 10 (R10) while CPU is running
Cannot read register 11 (R11) while CPU is running
Cannot read register 12 (R12) while CPU is running
Cannot read register 14 (R14) while CPU is running
Cannot read register 15 (R15) while CPU is running
Cannot read register 17 (MSP) while CPU is running
Cannot read register 18 (PSP) whi
Unspecified error -1
J-Link>

The device will be in the secured state as well after failing, requiring me to unsecure the device before attempting to flash it again.

If I exit out of JLinkExe between the erase and loadfile step, I am able to successfully flash the device successfully.

Is there something else I need to do between the erase and loadfile to allow it to happen all in one JLinkExe session?

Thanks!

dennis

RE: Unable to use JLinkExe to flash firmware to device, nrfjprog does work with same file

Asbjørn — Fri, 17 Jan 2025 14:19:32 GMT

Hi Dennis,

There's presumably two difference merged files, one for appmcu and one for cpunet? In j-link you have to select the correct target to use the right memory map. So there's a target for nRF5340appmcu and one for nRF5340cpunet available where you chose Cortex-M33. With the right target selected you should be able to program using j-link as well.

Best regards

Asbjørn