Can't debug the system with jlink

RE: Can't debug the system with jlink

Elfving — Tue, 25 Feb 2025 14:45:29 GMT

I believe there are a few different ways of disabling it, and easy to miss something you need to enable it, but essentially you need to configure it to be off in both the netcore and appcore.

What you essentially need to do is to make sure that ENABLE_APPROTECT_USER_HANDLING (and ENABLE_SECURE_APPROTECT_USER_HANDLING for the appcore) are set in the project. And then call nrf53_handle_approtect() early on it the initialization of the code. Do all of this for both the appcore and netcore code if you have custom applications running on both; if just the BLE stack is running on the netcore then just doing the appcore should be okay.

If that doesn't work, check if CONFIG_NRF_APPROTECT_USE_UICR is set.

Regards,

Elfving

RE: Can't debug the system with jlink

levijo — Mon, 24 Feb 2025 13:24:57 GMT

It also seems to me as an autoprotect issue, but in the other hand it is working well with the DK, using the same auto protection configurations

RE: Can't debug the system with jlink

levijo — Mon, 24 Feb 2025 11:05:38 GMT

I'm using version 2.7.0

RE: Can't debug the system with jlink

Elfving — Mon, 10 Feb 2025 08:39:53 GMT

Looks like approtect being enabled is the issue.

You can disable that to debug it, though how you do it depends a bit on the NCS version. And you'll have to do it for both the netcore and appcore for the nRF5340. What NCS version are you using?

Regards,

Elfving

RE: Can't debug the system with jlink

levijo — Sun, 09 Feb 2025 07:46:13 GMT

sometimes the debug console shows the following logs, which implies that the jlink debug server was able to connect but vs code doesn't show anything on the IDE:

JLinkGDBServerCL: SEGGER J-Link GDB Server V8.12d Command Line Version
JLinkGDBServerCL: 
JLinkGDBServerCL: JLinkARM.dll V8.12d (DLL compiled Jan 29 2025 13:06:04)
JLinkGDBServerCL: 
JLinkGDBServerCL: -----GDB Server start settings-----
JLinkGDBServerCL: GDBInit file:                  none
JLinkGDBServerCL: GDB Server Listening port:     57568
JLinkGDBServerCL: SWO raw output listening port: 2332
JLinkGDBServerCL: Terminal I/O port:             2333
JLinkGDBServerCL: Accept remote connection:      localhost only
JLinkGDBServerCL: Generate logfile:              off
JLinkGDBServerCL: Verify download:               off
JLinkGDBServerCL: Init regs on start:            off
JLinkGDBServerCL: Silent mode:                   on
JLinkGDBServerCL: Single run mode:               on
JLinkGDBServerCL: Target connection timeout:     0 ms
JLinkGDBServerCL: ------J-Link related settings------
JLinkGDBServerCL: J-Link Host interface:         USB
JLinkGDBServerCL: J-Link script:                 none
JLinkGDBServerCL: J-Link settings file:          none
JLinkGDBServerCL: ------Target related settings------
JLinkGDBServerCL: Target device:                 nrf5340_xxaa_app
JLinkGDBServerCL: Target device parameters:      none
JLinkGDBServerCL: Target interface:              SWD
JLinkGDBServerCL: Target interface speed:        12000kHz
JLinkGDBServerCL: Target endian:                 little
JLinkGDBServerCL: 
=thread-group-added,id="i1"
=cmd-param-changed,param="pagination",value="off"
arch_cpu_atomic_idle (key=32) at C:/Repos/Genio2.2/genio-worskpace/zephyr/arch/arm/core/cortex_m/cpu_idle.c:131
131		SLEEP_IF_ALLOWED(__WFE);

RE: Can't debug the system with jlink

levijo — Thu, 06 Feb 2025 10:52:50 GMT

also recovering helps when the device program fails, but the connection to the j-link for debugging always fails

RE: Can't debug the system with jlink

levijo — Thu, 06 Feb 2025 10:47:08 GMT

Hi Elfving,

This debug is working in the evaluation board; its our board, which is based on nRF5340 MCU that I can't connect with a debugger. Flashing with the VS code is working well but it seems like some security locks not allowing to connect with the J-link.

RE: Can't debug the system with jlink

Elfving — Thu, 06 Feb 2025 10:06:09 GMT

Hi again Joshua,

Does recovering or "erasing all" help? Do you have all the switches on the board on the board in the default position?

Regards,

Elfving