Nordic nrf52840DK board is failing to connect w/ newest NRF Connect Desktop v4.4.0 and w/ Segger Embedded Studio

[ant]

Hi,

I need help with my Nordic nrf52840DK board. Its is now failing to connect with the latest NRF Connect Desktop v4.4.0

I plug the board into the USB port of my macbook pro (MacOS BigSur v11.7.0) and the RSSI desktop app sees the jlink serial number but there's always an error that says failed to open device. and I tried to match what the NRF Connect version wants (it's looking for 7.88j) but there's only version 7.88n that is downloadable and upgrading to that version doesn't work either and fails the same.

The additional problem now is I cannot use my nrf52840DK board which Segger Embedded Studio (using several versions: 7.12a, 5.68, 5.34) stopped finding.

Any ideas or fixes to this recent observed failures w/ 52840DK boards working w/ NRF Connect Desktop and Segger Embedded Studio ?

[dejans]

Hi,

I need help with my Nordic nrf52840DK board. Its is now failing to connect with the latest NRF Connect Desktop v4.4.0

I plug the board into the USB port of my macbook pro (MacOS BigSur v11.7.0) and the RSSI desktop app sees the jlink serial number but there's always an error that says failed to open device. and I tried to match what the NRF Connect version wants (it's looking for 7.88j) but there's only version 7.88n that is downloadable and upgrading to that version doesn't work either and fails the same.

Did you use RSSI Viewer application from nRF Connect for Desktop? Have you tried programming the device when prompted to do so?

Best regards,
Dejan

[ant]

I tried to use RSSI Viewer but failed to do so and yes I tried to program the device when prompted but that also failed even though the serial number is "seen" but NRF connect fails to open the connectivity to my 52840DK...... I also tried drag and dropping the OB bin file from Segger for the Nordic 52840DK board but after that the same failures still occur

[ant]

that would not be recommended because if I erase the control chip, i would be bricking the nrf52840

[ant]

oh you meant the nrfjprog recovery ... i tried that but it did not work

[dejans]

Hi,

Are you able to use "west build" and "west flash" successfully to build and flash your nrf52840-dk board?

Best regards,
Dejan

[ant]

no west did not work

[ant]

I dug up my old windows PC notebook w/ Win10, and an older installation of NRF Connect desktop the BLE app was v4.0.1,... it recognized my nrf52840dk board ... and I was able to program it .... the good news is that when I plugged the dk board back onto my newer macOS NRF Connect desktop (v4.4.0)... the BLE app also successfully found the dk board and programmed it and can now scan BLE 

[dejans]

Hi,

This is really good news. Thank you for the update.

Best regards,
Dejan

[ant]

hi Dejan,

You're welcome.

on another board that has a similar issue, ... I followed "pressing the BOOT button" to get it into the mode to ingest the jlink OB bin file and dragged and dropped it ... it flashed .. but the problem is even thought the segger jlink id is seen by the nrf desktop app for example RSSI or BLE, ... somehow the type of DK board is showing as "0x00000 .... 0xFFFFFFF" and because of this , this second board is not able to be programmed by the NRF Connect desktop apps ...

do you have any suggestions for this second board's possible recovery ?  is there a way to write  somewhere in flash  "NRF52840DK" so that it is found ?

[dejans]

Hi,

ant said:

... somehow the type of DK board is showing as "0x00000 .... 0xFFFFFFF" and because of this , this second board is not able to be programmed by the NRF Connect desktop apps ...

Can you show this with screenshots/pictures?
What happens when the second board cannot be programmed? Do you get any error message? Can you provide some logs which we could look into?

Best regards,
Dejan