J-Link Base not showing anything and debug not working VS Code

[Svetlio141]

Hi,

I am currently developing a software for a custom board with nRF9160 chip.

The code is tested and works on nrf9160DK. The debugging works and the device is showing all information from logs.

The problem comes when I move to my custom board and I try to upload code from my J-Link Base.

There the code uploads but you cannot see any log information on the port of the J-Link.

Also when I try to debug the code I get the following message:

and I cannot seem to fix it.

For trying to see the log I go to NRF Terminal, select the COM port that the device is on and choose 115200 8n1.

Also tried with putty with 9600 but still the connection is established but nothing comes on the screen,

Any suggestions on why the J-Link is not functioning as intended?

[Håkon Alseth]

Hi,

 

when debugging with the nordic vscode plugin, you should be able to link the specific build with a debugger/programmer using this:

Does your debugger serialnumber now pop up?

Are you able to use nrfjprog to program manually?

  

Kind regards,

Håkon

[Svetlio141]

The debugger serial number pops up. 

And I also tried this and get the same results.

Håkon Alseth said:

Are you able to use nrfjprog to program manually?

I am not completely sure what this is. But the programming of the device works fine. The debugging doesn't.

[Håkon Alseth]

Hi,

 

At your end, it is most likely the wrong debug configuration type is used in launch.json:

"name": "(gdb) Launch",
"type": "cppdbg"
...

Can you try to remove that or just select the correct "nrf-connect" type when launching?

 

Kind regards,

Håkon

[Svetlio141]

I tried removing this line but didn't fix the problem.

What do you mean by selecting the correct nrf-connect type?

[Håkon Alseth]

Hi,

 

Svetlio141 said:

What do you mean by selecting the correct nrf-connect type?

You have two debug targets defined in your launch.json at this time.

You can either remove the whole of:

{
    "name": "(gdb) Launch",
    "type": "cppdbg"
    ...
},

And only keep the "nrf-connect" part, or select "nrf-connect" as your debug target.

Svetlio141 said:

I tried removing this line but didn't fix the problem.

Is there still no output in the debug console?

 

Kind regards,

Håkon

[Svetlio141]

Håkon Alseth said:

Is there still no output in the debug console?

No.

[Håkon Alseth]

Q1: Could you try to use the nRF9160-DK as an external debugger (see here for hardware setup: https://infocenter.nordicsemi.com/topic/ug_nrf91_dk/UG/nrf91_DK/hw_debug_out.html?cp=2_0_4_3_11)?

Then enter debug mode, ie. not a UART terminal.

Q2: Have you tried the same procedure on a newer installation of NCS, lets say v2.2.0?

Q3: Could you share details about your JLink Base debugger? Which version of JLink is it? That should be on a sticker on the backside of the debugger.

 

Kind regards,

Håkon

[Svetlio141]

Håkon Alseth said:

Q1: Could you try to use the nRF9160-DK as an external debugger (see here for hardware setup: https://infocenter.nordicsemi.com/topic/ug_nrf91_dk/UG/nrf91_DK/hw_debug_out.html?cp=2_0_4_3_11)?

Then enter debug mode, ie. not a UART terminal.

I have tried this before also. With the DK debugger I can't even upload code to the device. 

These are the errors that I get in Terminal:

Flashing build to 960072282
west flash -d c:\Users\SvetoslavAnev\tests\aws\build --skip-rebuild -r nrfjprog --snr 960072282

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: C:\Users\SvetoslavAnev\tests\aws\build\zephyr\merged.hex
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
Failed to read device memories.[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [  nRF91] - Failed when checking readback protect status.
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 33: nrfjprog --program 'C:\Users\SvetoslavAnev\tests\aws\build\zephyr\merged.hex' --sectorerase -f NRF91 --snr 960072282

 *  The terminal process terminated with exit code: 33. 
 *  Terminal will be reused by tasks, press any key to close it. 

Håkon Alseth said:

Q2: Have you tried the same procedure on a newer installation of NCS, lets say v2.2.0?

I haven't tried with newer versions. 

Håkon Alseth said:

Q3: Could you share details about your JLink Base debugger? Which version of JLink is it? That should be on a sticker on the backside of the debugger.

Version 11.0.

[Håkon Alseth]

Hi,

 

Svetlio141 said:

I have tried this before also. With the DK debugger I can't even upload code to the device. 

What is the VDD_IO voltage of your custom board?

On the nRF9160-DK it is default set to 1.8V, via the DIP-switch in the lower left corner marked "VDD IO".

If your custom design uses 3V, please change the position on the nRF9160-DK to match this.

 

Kind regards,

Håkon

[Svetlio141]

The VDD_IO is 1.8V.

[Håkon Alseth]

And this is also corresponding to what your custom board is powered and setup with?

[Svetlio141]

I'm sorry, my last message was not really clear.

Both the VDD_IO and the custom board setup is 1.8 V.