No emulators connected via USB on nRF51 and nRF52

[wendytang2000]

I just recently got both nRF51422 and nRF52844 DK. However, when I tried to connect through J-LINK, the error message popped up: No emulators connected via USB. Do you want to connect through TCP/IP? 

I have checked in Device Manager that J-link has showed up under COM port and USB controllers:

So far, I have tried many things individually as following to no avail. I tried on two boards and they appear to be working with LE5 blinking. 

1. install the latest segger embedded studio for x64 and x86;

2. install the latest J-link software pack for windows;

3. manually update the driver for J-link: 

4. manually select the USB driver under SES: 

5. update to the latest MCU firmware (J-Link OB-SAM3U128-V2-NordicSemi 170724.bin)

6. switch to a different PC also using windows 10;

7. switch to a different USB cable;

8. switch to a different DK;

9. step 1- 8 individually with rebooting my PC and reopen SES;

10. tried to connect J-Link through TCP/IP. But I failed to find the correct s/n of J-link;

11. measure the voltage of pins to make sure the board is good; 

At this moment, I ran out of ideas to try and would appreciate any input. Thanks. 

[Einar Thorsrud]

Hi,

The first things I would ask was to try another DK, cable, computer etc, all of which you have allready done. One last thing that comes to mind then is if there could be an issue with switch positions on the DK or similar. Can you take a photo of your DK so that I can see how it is configured (all switch positions etc), and how it is connected to your computer?

[wendytang2000]

IMG_0507.zipHi, Thanks for your reply. Please see pictures attached with nRF51422 connected. I have same issue with the DK. 

[Einar Thorsrud]

Hi,

All looks good there. Can you try to download the latest nRF Command line tools and do a "nrfjprog --recover"? Does it work? If not, what error message do you get? If it fails it could also be useful to se the debug log which you get by appending "--log log.txt" to the command.

[wendytang2000]

Hi Einar,

The error message is:

C:\Users\Administrator>nrfjprog --recover
ERROR: There is no debugger connected to the PC.

The log file is attached. Thanks!

Wendy

Fullscreen 1348.log.txt Download

[2021-Mar-08 13:42:15] [ info] --------------------------------------------------------------------------------
[2021-Mar-08 13:42:15] [ info] nrfjprog --recover --log log.txt 
[2021-Mar-08 13:42:15] [ info] nrfjprog version 10.12.1 
[2021-Mar-08 13:42:15] [ info] --------------------------------------------------------------------------------
[2021-Mar-08 13:42:15] [debug] [ nRF0x0] - open_dll
[2021-Mar-08 13:42:15] [ info] [ nRF0x0] - Load library at C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin\JLINKARM_UNKNOWN_NRFJPROG.dll.
[2021-Mar-08 13:42:15] [ info] [ nRF0x0] - Library loaded, loading member functions.
[2021-Mar-08 13:42:15] [ info] [ nRF0x0] - Member functions succesfully loaded.
[2021-Mar-08 13:42:15] [ info] [Backend] - Logger callback at 0x7ff7b72756f0 registered in Segger backend logger.
[2021-Mar-08 13:42:15] [ info] [  JLink] - [Info    ] [JLink     ] Logger callback at 0x7ff7b72756f0 registered in JLink logger.
[2021-Mar-08 13:42:15] [debug] [nRFUnknown] - Just_open_dll_tagged_callback
[2021-Mar-08 13:42:15] [debug] [Backend] - open_dll
[2021-Mar-08 13:42:15] [ info] [Backend] - No J-Link DLL path was provided. Attempting to auto detect.
[2021-Mar-08 13:42:15] [ info] [Backend] - Load library at C:\Program Files\SEGGER\JLink\JLink_x64.dll.
[2021-Mar-08 13:42:15] [ info] [Backend] - Library loaded, loading member functions.
[2021-Mar-08 13:42:15] [ info] [Backend] - Member functions succesfully loaded.
[2021-Mar-08 13:42:15] [debug] [Backend] - dll_version
[2021-Mar-08 13:42:15] [ info] [Backend] - Segger dll version 6.88.a loaded.
[2021-Mar-08 13:42:15] [debug] [Backend] - set_core_data
[2021-Mar-08 13:42:15] [debug] [ nRF0x0] - enum_emu_snr
[2021-Mar-08 13:42:15] [debug] [nRFUnknown] - Just_enum_emu_snr
[2021-Mar-08 13:42:15] [debug] [Backend] - enum_emu_snr
[2021-Mar-08 13:42:15] [debug] [Backend] - ---just_enum_emu_snr
[2021-Mar-08 13:42:15] [debug] [Backend] - ---just_get_num_emus
[2021-Mar-08 13:42:15] [debug] [ nRF0x0] - close_dll
[2021-Mar-08 13:42:15] [debug] [nRFUnknown] - Just_close_dll
[2021-Mar-08 13:42:15] [debug] [Backend] - close
[2021-Mar-08 13:42:15] [debug] [Backend] - disconnect_from_emu
[2021-Mar-08 13:42:15] [debug] [Backend] - is_connected_to_emu
[2021-Mar-08 13:42:15] [debug] [Backend] - Segger Backend closed.

[Einar Thorsrud]

I am unable to explain this. It is clear that the debugger enumerates as a J-Link from your screenshot from the Device manager, so things should work. Also that you see the same issue even when replacing every component (DK, computer, USB cable) make me puzzled.

Can you try to remove all Segger related code, reboot, install the nRF Command line tools including segger tools, reboot and then test nrfjprog again? You do not need to do any manual tweaking of drivers etc, it should all work automatically.

[wendytang2000]

Today, I tried what you suggested. Unfortunately, the issue persists. I got the same log file. Is it possible to set up a zoom meeting with you to troubleshoot? I just want to connect to the board so I can start to write some sw. Thanks. 

[Einar Thorsrud]

Hi,

I have discussed this with a few collogues an none of us are able to explain this, as you should have covered everything with the list form the initial post, and everything seems good from the device manager. Can you ask a collogue of you to try and see if he/she can get it to work, just in case there is an issue that is repeated that we do not spot?

Other then that I think we have almost exhausted all ideas allready, so I do not see that this would be solved faster by a conference call.

[wendytang2000]

Hi Einar, today I switched to HP instead of another microsoft surface pro. The following message showed up when I segger J-linked to USB. After clicked on Yes, it updated the firmware then I was able to J-link the board. Although I updated the firmware using drag and drop before, I didn't think it was done successfully without proper initialization. 

After the firmware was updated, I was able to J-link to the board using my own PC. 

Thanks for your help!

Wendy