FATAL ERROR: command exited with status 1: /opt/SEGGER/JLink_V770e/JLinkExe -nogui 1 -if swd -speed 4000 -device nrf52 -CommanderScript /tmp/tmp9lqsoklajlink/runner.jlink -nogui 1

[ruben.m]

Hello, 

I am getting an error when I try to flash my device with j-link (see capture I attach) and this is some information I have:

-I can flash correctly with zephyr 3.2.0 vanila but now that I am working with NCS 2.2.0 I get this error.

-I can flash other devices with the same microcontroller (nrf52840) and NCS 2.2.0, so I just get this error in one of the devices I have.

I hope you can help me and I can provide you all information you need.

Best regards

[Naeem Maroof]

Hi Ruben,

Thank you for contacting DevZone at NordicSemi.

As you are using a nordic soc (nrf52840) and the ncs 2.2.0, may I ask you to build and flash using VS Code and see if error persists, or if you get any other information.

As you mentioned that you can build and flash other nrf52840 devices and experiencing error with one of the device:

1) May I ask to check that you are building / flashing it correctly (using same command as for other devices and correct parameters)?

2) Were you able to program this device previously?

3) Were there any changes to the jlink (updation etc. recently)?

4) When you connect this device, does it get recognized? Can you please test with the VS Code. 

Also, make sure the device is in correct mode (switches etc in the correct position if it is the DK, or any other related configurations).

I am not sure about jlink commander (though under the hood our solutions are using jlink), we recommend uisng VS Code with NRF Extensions and/or using the nrfjprog and other nrf-standalone tools (nrfconnect for desktop and nrfutils).

BR,

Naeem

[ruben.m]

Hello, thanks for answering, maybe I don't express myself well, I have two projects with ncs 2.2.0, I can flash one of them, but the other returns the error that I showed you, so it seems that the error is in the code.

I've been trying to figure it out all morning and seems that the problem is lack of memory since I can flash without debug but I can not with debug options, this is my memory partitions:

 

and I would like to be able to debug in order to find bugs and test correctly, I tried to comment bootloader and mcumgr but seems is not enough

[Naeem Maroof]

I think this ticket describes the issue you are having.

[ruben.m]

Yes, seems the same but also seems that Nordic did not find a solution yet?

[Naeem Maroof]

Hi Ruben,

I think it is not the issue related to the Nordic hardware including SoC and the DK, or the Nordic software including drivers and the SDK, but rather the user application (code and the size using different required libraries etc) and the partitions.