new nRF52840 V217.40 - 0.9.3 not being seen by Segger/nRFgoStudio

[ToasTer86]

Dear Nordic Devzone,

Just recently I purchased 2 additional nRF52840. In total I have 6 of them now; The first four all have the following numbers on the chip:

pca10056
0.9.2
2017.33
serial number

The 2 new one's have 2 other numbers on the chip:

pca10056
0.9.3
2017.40
serial number

The unfortunate interesting thing is that the 2 new one's are both not being recognized by nRFgo studio/Segger embedded studio. But Windows is showing them in my device manager, I can also see the J-link storage device.

So trying to troubleshoot this I went to the "device event page" in the device manager. Windows does tell me the drivers have been installed, with the exact same message as the 4 other nRF52840 that are working fine.

Driver Management concluded the process to install driver jlinkcdc.inf_amd64_8134dd13435f192f\jlinkcdc.inf for Device Instance ID USB\VID_1366&PID_1015&MI_00\6&1E3257C6&0&0000 with the following status: 0x0.

I tried uninstalling the device and reinstalling it, but it still does not show up in any of the tooling.

Do I need separate drivers for these new boards?

[Bjørn Kvaale]

I just tested my pca0056 0.9.3 2017.39 serial number board with nrf go studio. Your device says 2017.40, but that only means that your nrf52840pdk was produced in week 40 and mine in week 39. The most important thing is that we are using the same version 0.9.3. The device is recognized in nrf go studio and ses. Was also able to upload the ble_app_hrs example to the board on segger embedded studio (am using v3.30 64 bits) and run the heart rate example on nrf toolbox for ios. Have you tried restarting your pc? Which version of segger embedded studio are you using? I would suggest upgrading to the latest version if you haven't already.

EDIT: I got a tip from a colleague. First, you can download the J-Link FW from this link here. If you turn your pdk off and then hold in the IF BOOT/RESET button while turning on the preview dk, you should see the board appear as a BOOTLOADER drive. Then, you can drag and drop the .bin file you downloaded to the BOOTLOADER drive. That should hopefully fix your problem.

[Bjørn Kvaale]

Really hope that fixes things. Not ideal if you need to use two computers to program your boards. I wonder if it's a Windows driver issue maybe...