nRF Connect Programmer does not recognize hardware

[Jim R]

Have used nRF Connect V3.30 for the past year to program nRF52DK with USB and nRF52832 BLE modules with Segger J-Link Base programmer without issue.  Updated programmer app yesterday and now the programmer does not recognize the nRF52DK or the Segger programmer.  The devices show up in the Select Menu but give an "Unrecognized device.." message when selected.  Have uninstalled nRF Connect and all Segger programs and drivers and re-installed the latest versions several times but get the same results.  Tried installing old V3.30 nRF Connect but get message that Programmer app is only compatible with nRF Connect V3.60.  It appears that installing the old nRF connect still installs the latest individual apps.  How do I either get V3.61 to work or get the old Programer app?

[Simonr]

Is the nRF52 DK working as intended with the other apps, and does it work as intended in SEGGER or not? If you have issues with the DK as a whole, please go through the list here to see if that changes the nRF52 DK behavior.

Best regards,

Simon

[Jim R]

I am able to program the nRF52 DK using the Segger J-Flash app and the DK works properly.

[Simonr]

There seems to be a bug in the latest nRFConnect version causing both the errors seen in this thread, and I'm currently awaiting a reply from the app developers with the correct way to fix this. Thank you for your patience.

Best regards,

Simon

[Henry_Chou]

Simon:

Sorry for late update my status. The ill condition is using NRF51DK & the NRF51822AA production board with segger Jlink EDU (Driver V6.8.6f). Both of them can't readback when I replace from V3.6.1 (because device connection problems) to V3.6.0.But actually, I think the root cause is programmer App. Because I had done the V3.6.0 with old progammer App, in that case it worked well. So I advise our PE to keep old V3.6.0. Thanks for your reply. And waiting for your good news.

[Simonr]

Hello Jim and Henry

Could you please provide some more information on the hardware you're using, as we would like to get a better scope of what devices this is affecting. Please provide the hardware information on the DKs you are seeing this issue in, I.E. PCA10100, 1.0.0, 2019.40.

Please also provide the information seen when connecting in the nRFConnect log as well., I.E. NRF52832_xxAA_REV2.

Best regards,

Simon