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 Mihail,

 

If you can flash, there should not be a hardware-wise restriction to enter debug mode. It can be a dependency (i.e. on some sort of python library or similar).

  

Could you try to navigate to the ncs project that you have built and flashed, go into the build-folder and write:

cd path/to/my_project/build
ninja debug

 

And see if it enters debug mode successfully? 

Mihail M said:

- Our custom board has a switch similar to the nrf9160dk that switches the debug port between an nrf52833 and a nrf91. Programming the nrf9160 and the nrf52833 works fine through nrfjprog and vscode, trying to "debug" the application throws the error.

Is there any details around the error message that you can share? Is it similar to the original message, where it is "file not found"?

Mihail M said:

My end goal would be to be to use CLion for development, but as far as I know it's not oficially supported by NCS, so fixing the problem with debugging within VScode is also an acceptable solution.

NCS (and zephyr for that matter) is quite versatile when it comes to which IDE/editor you use. The idea is that you can integrate it into your favorite editor or IDE, as long as you use the same toolchain (ie. zephyr-sdk toolchain.

 

Kind regards,

Håkon