Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

RE: Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

CapAble — Tue, 23 Jan 2024 02:04:37 GMT

The latest version of Virtualbox (7.0.14 r161095) with the corresponding Extension pack seems to not have the issue that I reported earlier. Thought it might help anyone who might experience similar issue.

RE: Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

CapAble — Tue, 05 Dec 2023 18:50:18 GMT

In the Ubuntu Virtualbox guest, the command line you shared is one I had used before, fails with the same error I posted earlier. This time I also removed the Virtualbox guest extension pack, and it still fails. Like before, the same command when run on Windows 11 works ok.

I suppose, given the issue is not clearly in any one of Segger/JLink, nRF board, or Virtualbox, it might be harder to analyze. I am ok with the work around to copy the hex file to Windows 11 host, and program it there.

As for debugging it, a quick test showed that I can run JLilnkGDBServer on Windows 11 (making sure it listens on all incoming connections on port 2331,2332, and 2333), and can connect from the Linux guest OS running in Virtualbox. Not optimal, but is do able.

Thanks for your timely and helpful response Jared. You may close this ticket or mark this as resolved.

Regards.

RE: Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

Jared — Tue, 05 Dec 2023 11:53:44 GMT

I understand. You mentioned that you are able to list the debugger with nrfjprog but not flash the hex. Are you able to do a recover?

'nrfjprog --log zephyr.hex --sectoranduicrerase --verify -f NRF52 --snr 1050263398

Can you try this instead, and share the log:

 nrfjprog --program zephyr.hex --chiperase --verify --log

I haven't been able to test this on virtual box yet but it worked on VMware at least,

regards

Jared

RE: Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

CapAble — Mon, 04 Dec 2023 16:17:34 GMT

Hi Jared.

The response to my post on Segger support (https://support.segger.com/#ticket/zoom/35021) is as below. Essentially, it says I need to seek help from Nordic.

You are using a J-Link OB which is an on-board debug probe for evaluation boards.

The J-Link OB is provided solely as part of an evaluation board.

It is not sold separately and may only be used to debug the device on the evaluation board it comes with.

Support is provided via the evaluation board manufacturer.

This article might help you to get up & running:

https://wiki.segger.com/J-Link_cannot_connect_to_the_CPU

If you need any additional help, we would suggest to get in touch with Nordic

I suppose this this could mean the issue is tied to the USB interface exposed by the nRF52840-DK, not the JLink interface itself that is exposed.

How could I debug this further? If it help recreate the scenario, the configuration I have is: Windows 11 host OS, Virtualbox 7.0.12 with extension pack + USB 2.0 emulation, Ubuntu 22.04 guest OS, JLink 7.94.

Regards.

RE: Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

Jared — Mon, 04 Dec 2023 13:31:34 GMT

Hi,

Yes, I think you should post this on the Segger Forum, they would be able to support you better on this issue,

regards

Jared

RE: Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

CapAble — Fri, 01 Dec 2023 19:18:06 GMT

Hello.

The problem seems to be with the Virtualbox setup that I have for running Linux. I have tried using the USB 1.0, 2,0, and 3.0 emulation, and with the Virtualbox extenstion pack installed. The Segger JLink is identified by "lsusb", and "nrfjprog --ids" reports the correct serial number, the serial ports are also ok when once the app is installed, so are the couple of Bluetooth examples.

However, to flash the FW/app it seems only the host OS (Windows 11) is able to do so with the nrfjprog. This does give me a work around to flash the image, but not for the ability to use GDB over JLink

Anyone might have any clue why Virtiualbox might have a problem? The setup seems to have worked well for quite some time now with other USB devices importted into the Linux guest machine. Also, per https://wiki.segger.com/J-Link_on_VirtualBox the config is supported. Will check if there is support forum for Segger.

Regards,

-Arun.

RE: Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

CapAble — Fri, 01 Dec 2023 16:06:28 GMT

Hi,

I checked the list you pointed to. Following is my response to each point:

Does the device show up in Device Manager on your computer? Please try to connect and disconnect the kit a few times. It might show up with unexpected names.

Yes, the SEGGER USB device is listed in the output of "lsusb" command. And yes, I have power cycled the board many times now.

Also, a MSD gets mounted on the Linux host, and I see "README.TXT" and "SEGGER.HTML" files with expected contents.

Like I mentioned before, I see the LED1 blink, which I suppose means some default sample program on the board is running on it, is this correct?
Have you tried a different USB cable? Faulty cables are surprisingly often the problem. Have you tried using a different computer? If it works on a different computer we know that the kit is not broken and that it is probably a driver issue.

Yes, I have changed three USB cables, each of which I know works with other devices that I have. Note also that like I mentioned earlier, "nrfjprog --ids" does list the board, so the board is accessible.

The board is connected to a powered USB hub which seems to work well with many other devices. I have changed to another powered USB hub, but the same result.

I do not have another computer to try to find one where I can try this. But shouldn't all the other inputs here be sufficient to say the host side as well as the USB hub/cables are ok?
Have you tried to press the IF BOOT/RESET button while power cycling the kit? It should then show up as a Removable Storage Device named "BOOTLOADER". Then you can drag-and-drop the J-LINK interface MCU firmware found here (v170724) onto the storage device to reprogram the JLINK firmware.

When I press the reset button while the board is connected and powered on, I see the LED1 switch off until I release the reset button.

When I keep the reset button pressed and power on the board, then release the reset button 10 seconds after powering on, the board does not enter the bootloader. The MSD Instead the LED1 starts to blink, which I presume to mean the board did not enter the bootloader, is this correct? Shouldn't this work at least?

i downloaded the "j-link-ob-sam3u128-v2-nordicsemi-170724.bin" file, and copied it to the MSD that gets mounted as "/media/user/JLINK". But a file "FAIL.TXT" gets created with contents "The currently active SWD interface does not support MSD drag and drop". Am I doing something wrong?
Have you measured the supply voltage on the kit? It should be somewhere between 2.8V-3.3V. If it isn't, then the hardware is probably broken.

The board is powered from USB, all other observations would seem to mean the power is ok, isn't this reasonable assumption?
Have you made sure that you are using the latest J-Link driver version?

I downloaded the current version of Segger SW, which per output of "nrfjprog --ids" is at "7.9.4".
Have you tried this guide? https://devzone.nordicsemi.com/blogs/...

The "JLinkExe" comnand outputs "Connecting to J-Link via USB...FAILED: Cannot connect to J-Link.". So cannot try anything else.

The board is new, it was delivered yesterday.

RE: Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

Jared — Fri, 01 Dec 2023 13:26:10 GMT

Hi,

Can you go through this checklist and see if any of them resolves your issue?

regards

Jared

RE: Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

CapAble — Fri, 01 Dec 2023 13:15:15 GMT

Hi Jared.

The board is as it was delivered, no modifications to it.
Settings of the switches
- SW6: I have left it at default, and LED5 lights up. If it is at nRF only then the LED does not light and the board does not show up on the Linux host. Also, LED1 blinks (fades in and out).
- SW8: is on, else the LED5 does not light.
- SW9: is on VDD position, else LED5 does not light.

Without the above settings, the board does not show up the Linux host (output of 'lsusb' command), and the "nrfprog --ids' does not list the board ID. The command 'nrfjprog --program ./build/zephyr/zephyr.hex --sectoranduicrerase --verify -f NRF52 --snr 1050263398 --log mylog' fails as before, and there is nothing in the log file.

If it is relevant, I see /dev/ttyACM0 and /dev.ttyACM1 show up, but I do not see any output on them at 11500 bps & no parity.

Regards,

-Arun,

RE: Unable to program nRF52840_DK, fails with error ''Cannot connect to J-Link.''

Jared — Fri, 01 Dec 2023 10:02:41 GMT

Hi,

Have you done any modifications to the development kit such as soldering or cutting any solder bridge?

How is the different switches such as SW9, SW8, SW6 configured?

regards

Jared