Since update 3.9.0, I am not seeing my Dev Kits or J-links showing up in the "Select Device" device list.
I have tried both Mac and Windows.
Anyone else experiencing the same issues?
Since update 3.9.0, I am not seeing my Dev Kits or J-links showing up in the "Select Device" device list.
I have tried both Mac and Windows.
Anyone else experiencing the same issues?
I am experiencing a similar problem. Have you tried actually physically connecting the device you are trying to connect the J-Link to and then re-checking the 'Select Device' list? I had to actually have my 6-pin J-Link probe connected to my chip I'm trying to work on in order for nRF to even see the J-Link on the 'Select Device' list. Maybe an added layer of security to make sure folks are using proprietary equipment? Let me know if this works for you. I'm just learning all this stuff.
I found this on another forum, looks like it's actually one of Nordic's people:
'The developers have also found that the JLink version that is bundled with the latest version of nRF Command Line Tools causes errors in nRF Connect for Desktop. They are working on a fix for this as well, but a temporary workaround is to downgrade JLink to a known working version, v6.88a, from https://www.segger.com/downloads/jlink.
Best regards,
Marte'
I am experiencing a similar problem. Have you tried actually physically connecting the device you are trying to connect the J-Link to and then re-checking the 'Select Device' list? I had to actually have my 6-pin J-Link probe connected to my chip I'm trying to work on in order for nRF to even see the J-Link on the 'Select Device' list. Maybe an added layer of security to make sure folks are using proprietary equipment? Let me know if this works for you. I'm just learning all this stuff.
I found this on another forum, looks like it's actually one of Nordic's people:
'The developers have also found that the JLink version that is bundled with the latest version of nRF Command Line Tools causes errors in nRF Connect for Desktop. They are working on a fix for this as well, but a temporary workaround is to downgrade JLink to a known working version, v6.88a, from https://www.segger.com/downloads/jlink.
Best regards,
Marte'