Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

RE: Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

efurunes — Mon, 11 May 2020 16:16:00 GMT

Hi,

the programmer now works. I dont know why it works and I dont know why it did not work previously. Both the DK and the custom board are the same.

Anyways, thanks for your help.

RE: Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

Kenneth — Mon, 11 May 2020 10:01:51 GMT

I think trying another programmer (for instance DK) is something you should consider to test if you have several boards that no longer can be programmed. I am not aware of anything in specific that should cause the programmer to fail.

Best regards,
Kenneth

RE: Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

efurunes — Wed, 06 May 2020 12:15:38 GMT

Ok, sounds reasonable to make nrfjprog work first...

I have several custom boards, none of them can be reached by the programmer.

I have only one DK here, but I have one or a few more in the office (I think)

RE: Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

Kenneth — Wed, 06 May 2020 11:56:00 GMT

I assume you will need to do a full uninstall of nRF Connect for Desktop and re-install an older one?
https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Connect-for-desktop/Download#infotabs

But if nrfjprog doesn't work, then trying to use nRF Connect for Desktop won't do any difference. You will likely have better luck if trying to downgrade nrfjprog if you want to test older versions, and run the suggested nrfjprog commands from there:
https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download

Do you have more than one DK and one custom board for testing?

RE: Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

efurunes — Wed, 06 May 2020 11:53:30 GMT

Is there a way to change to an earlier version of the programmer?

RE: Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

efurunes — Wed, 06 May 2020 11:14:31 GMT

From the programmer:

Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: CANNOT_CONNECT (fffffff5)

Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: WRONG_FAMILY_FOR_DEVICE (fffffffb)

RE: Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

efurunes — Wed, 06 May 2020 11:13:19 GMT

Hi,

it did not work:

C:\TEMP\RCC1601\EMC>nrfjprog --recover
Recovering device. This operation might take 30s.
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.

C:\TEMP\RCC1601\EMC>nrfjprog --version
nrfjprog version: 10.8.0
JLinkARM.dll version: 6.70d

RE: Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

Kenneth — Wed, 06 May 2020 10:53:31 GMT

I have updated the screenshot, hopefully more visible now. Here are the commands you can run in any case:

nrfjprog --version
nrfjprog --recover

Best regards,
Kenneth

RE: Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

efurunes — Wed, 06 May 2020 10:51:51 GMT

Hi,

It is a bit hard to read the image since it is so small, but I tried using the nrfjprog:

C:\TEMP\RCC1601\EMC>nrfjprog -f UNKNOWN --log --program BLE.hex
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.

C:\TEMP\RCC1601\EMC>

It might be that something has happened to the board (even though it seems to work fine). I will investigate...

RE: Can not connect to nRF5240 through DK (PCA10040) after updating nRF Connect

Kenneth — Wed, 06 May 2020 10:39:50 GMT

Is it possible that something have happened to your board to make the hardware fail somehow? Check electrical connection, power supply etc.

Can you try to run the nRF Command line tool directly, e.g.: