This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PCA10028 firmware update problems

Hi, I am trying to use the nRF51DK (PCA10028 v.1.2.2).

I cannot get Windows 7 to recognize it via USB reliably. I have JLink v6.16a installed and when I plug in the board, if it recognized it, it is listed as drive F instead of removable drive JLINK. When I start nRFgo Studio there is a message from JLink saying that a new firmware version is available. When I try to update the board it ends in either a timeout error or a read error.

Windows 7 does recognize PCA10031 and allowed me to do the firmware update with no problem.

At this point all I am trying to do is get blinky loaded and working on PCA10028. Does anyone have suggestions for making it work?

Thank you.

  • Here is the firmware read error as stated in the log file:

    2017-08-02T23:17:11.816Z ERROR Unable to read connectivity firmware version: Unable to get version info for 681605782: Error occured when get device info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

    Not sure why JLink erroring out....

  • Try J-Link Configurator util from SEGGER SW pack you installed, it serves for stand-alone J-Link FW upgrade. Also surprisingly changing USB cable helps sometimes when you have problems and even more surprisingly (or not) it can exhibit more during FW upgrade...

  • Thanks for the response! I found that the J-Link Configurator cannot see the PCA10028 board even though it is correctly listed in the Device Manager. I have tried to use the command line JLink.exe. Interestingly, JLink.exe version. 6.16j does not work with the board, i.e. it cannot read the board's current firmware version. When I use JLink.exe verion 6.16a, it can see the board (the current firmware can be read), however, the firmware update still fails with a read timeout. Frustrating. I feel like I'm missing something simple.

  • I just tried a new USB cable and everything worked! Whew. Thanks for the suggestion.

  • in the end it was something simple;)

Related