• State Verified Answer
  • Replies 1 reply
  • Subscribers 71 subscribers
  • Views 3123 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 114793
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF51822 mKit- Connecting to J-Link via USB failed. Way to resolve?

Utkarsha Agwan

I've connected my nRF51822 mKit to my Linux system via a USB cable. While trying to upload code on the board, I got the following error:

SEGGER J-Link Commander V5.12g (Compiled May 27 2016 17:03:43) DLL version V5.12g, compiled May 27 2016 17:03:38

Connecting to J-Link via USB...FAILED: Can not connect to J-Link via USB. Unknown command. '?' for help.

How do I resolve this?

Parents
  • 0

    Hi.

    The mKit board has the mBed Standard CMSIS-DAP firmware programmed on the on-board debugger chip. You must therefore use programming software on your pc that support CMSIS-DAP. One example is the OpenOCD software. If you have a windows machine available, ARM's Keil software also supports CMSIS-DAP.

    Does the board mount itself as a mass storage device in your system? Then you can drag'n'drop hex files to it directly. This is the normal method with mBed compiled hex files.

    How are you compiling the hex files you wish to flash to the board?

Reply
  • 0

    Hi.

    The mKit board has the mBed Standard CMSIS-DAP firmware programmed on the on-board debugger chip. You must therefore use programming software on your pc that support CMSIS-DAP. One example is the OpenOCD software. If you have a windows machine available, ARM's Keil software also supports CMSIS-DAP.

    Does the board mount itself as a mass storage device in your system? Then you can drag'n'drop hex files to it directly. This is the normal method with mBed compiled hex files.

    How are you compiling the hex files you wish to flash to the board?

Children
No Data
Related
Terms of service