jlink cannot recognize nrf51-dk

RE: jlink cannot recognize nrf51-dk

Anders Strand — Fri, 08 Apr 2016 09:07:47 GMT

Thanks for posting an accurate description of the solution :) The main difference between the mBed and JLINK firmware, is that mBed uses CMSIS-DAP between the PC and debugger chip. The JLink uses Jlink. You can drag and drop .hex files on both types.

RE: jlink cannot recognize nrf51-dk

chadrick — Fri, 08 Apr 2016 08:36:52 GMT

solved it. The core of the problem was that the interface firmware(IF) is MBED version, and not JLINK OB version.

Even in the User Guide, it mentioned this but I didn't understand it then but now I do.

From my 'basic' understanding, MBED IF is for loading nRF51 chip with hex files generated from mbed online compiler.

On the other hand, JLINK IF is required for the nRF51-DK to be compatible with J-Link software.

To summarize, the problem had nothing to do with host OS but rather the target board didn't have the proper firmware to interact with JLink tool.

The method of changing the IF is introduced in the "nRF51-DK User's Guide", but the description was not accurate, leading me to do stupid stuff for a long time.

A more straightforward and clear description of do this can be found in one of the answer(answer by Tanasis!) in this post(https://devzone.nordicsemi.com/question/44531/i-cant-update-the-j-link-ob-firmware-nrf51-dk/).

also, I've made a video just in case people would like a more elaborate, straightforward explanation(https://www.youtube.com/watch?v=_z-l-QunYfA&feature=youtu.be)

RE: jlink cannot recognize nrf51-dk

Christopher — Fri, 08 Apr 2016 05:49:59 GMT

For your information, you can install the latest Segger tools by yourself. The latest version is 5.12. You can download it from here.

You can run JLinkConfig to see the connected Segger probes. You can update the firmware of the emulator if you do not want to use the CMSIS DAP interface.