uVision reflashed J-Link on nRF51822-EK, failed, and PCA10001 no longer works.

[Hamilton]

I'm getting started with this evaluation kit by working through the user guide and almost made it through the Blinky example before I ran into trouble.

After compiling the example and during loading, uVision 5 offered to update the J-Link flash (I believe) and subsequently failed.

That was the end of the PCA10001, it had a green led lit up to this point and was enumerated as COM3 in windows device manager, but after it appears as a USB device in device manager, but doesn't enumerate as a comm port.

I performed a similar process with donle (with the uart example) and refused it's offer to upgrade the firmware and it appears that worked. As part of that process I learned that the dialog box asking about upgrading the firmware had the a title of: "J-Line V4.78j Firmware update" and contained the following text: "A new firmware version is available for the connected emulator. Do you want to update to the latest firmware version? This is strongly recommend, etc...".

After all of this J-Link Configurator is able to see the dongle (which has a nice green led lit) but does not see the PCA100001.

Has anyone else had a similar experience, or know how to bring this back to life.

Thanks in advance for any help. -- Andy

[Hamilton]

Thank you Petter, I really appreciate your help. I had checked "Install USB driver for J-Link-OB with CDC" when I installed the J-Link Software pack. Actually, I installed in once without checking that box and then re-installed and did check it. Please let me know if you think this is related and I'll uninstall and reinstall it with the correct boxes checked.

Anyway, I've made some progress, I was able to see the device in nRfgo Studio, and it also asked about updating the flash. I agreed to that and although it said it failed, it actually did seem to work, the green light came on and I was subsequently about to download the code from uVision (as long as I didn't let uVision reflash things...).

I then repeated the whole process and again uVision caused it to fail and nRfgo Studio made it work again, so now I can brick and un-brick at will.

Here is the contents of the dialog boxes that are present during the flash updates, similar but slightly different in the versions, both say they fail, but the nRfgo studio seems to work (after disconnecting and reconnecting the USB cable anyway).

From uVision 5: (this results in a non-working eval board) Dialog Box Title = "SEGGER J-Link V4.78j Firmware Update" Dialog Box Contents = New firmware: J-Link OB-SAM3U128 V1 compiled Aug 1 2012 10:57:06 Current firmware: J-Link OB-SAM3U128 V1 compiled Dec 19 2011 BTL
Starting bootloader... already started. Sending firmware data... OK (114688 bytes).
Waiting for new firmware to boot... Waiting for emulator to detach... OK after 260ms. Waiting for emulator to attach... Timeout. ERROR: Communication timeout. Emulator did not re-enumerate.
ERROR: Firmware update failed.

From nRfgo Studio: (this results in a working eval board) Dialog Box Title = "SEGGER J-Link V4.52c Firware Update" Dialog Box Contents = New firmware: J-Link OB-SAM3U128 V1 compiled Aug 1 2012 10:57:06 Current firmware: J-Link OB-SAM3U128 V1 compiled Dec 19 2011 BTL
Starting bootloader... already started. Sending firmware data... OK (114688 bytes). Waiting for new firmware to boot... Waiting for emulator to detach... OK after 260ms. Waiting for emulator to attach... Timeout. ERROR: Communication timeout. Emulator did not re-enumerate. ERROR: Firmware update failed.

So I'm able to move forward now as long as I don't let uVision reflash things, but it would be nice to know what's going on here and how to fix it.

Thanks again for your help! -- Andy

[Petter Myhre]

Could you try another USB port and another cable?