[SOLVED]Linux: Unable to connect to J-Link on board nRF51822 Evaluation Kit

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Many Mac OS X problems

    I've had a lot of problems along these lines, and also a lot of great solutions.

    I basically went through 3 phases with my nRF51822 Evaluation Kit board (PCA10001).

    In phase 1, everything worked will, both with and without softdevice. I could use JLinkExe to download programs and I could use JLinkGDBServer with gdb to debug. This was with version 4.62, previous versions didn't work so well.

    In phase 2, I could use JLinkExe to download programs using the si 1 and selemu commands first (without them it didn't work). However, the GDB server didn't work. The output was:

    Source Code

    1. Connecting to J-Link...
    2. Connecting to J-Link failed. GDBServer will be closed...
    3. Restoring target state and closing J-Link connection...
    4. Connecting to J-Link...
    5. Connecting to J-Link failed. GDBServer will be closed...
    6. Restoring target state and closing J-Link connection...
    7. Shutting down...


    In phase 3, JLinkExe doesn't work even with si 1 and selemu. This is the output:

    Source Code

    1. J-Link>selemu
    2. J-Link[0]: Connection: USB, Serial number: 0, USB address: -257
    3. Select emulator index: 0
    4. DLL version V4.62, compiled Jan 25 2013 15:29:24
    5. Firmware: J-Link OB-SAM3U128 V1 compiled Jan 7 2013 18:12:29
    6. Hardware: V1.00
    7. S/N: 480202242
    8. VTarget = 3.300V
    9. Info: Could not measure total IR len. TDO is constant high.
    10. Info: Could not measure total IR len. TDO is constant high.
    11. No devices found on JTAG chain. Trying to find device on SWD.
    12. Info: Found SWD-DP with ID 0x0BB11477
    13. Info: Found SWD-DP with ID 0x0BB11477
    14. No device found on SWD.
    15. Did not find any core.
    16. Failed to identify target. Trying again with slow (4 kHz) speed.
    17. Info: Could not measure total IR len. TDO is constant high.
    18. Info: Could not measure total IR len. TDO is constant high.
    19. No devices found on JTAG chain. Trying to find device on SWD.
    20. Info: Found SWD-DP with ID 0x0BB11477
    21. Info: Found SWD-DP with ID 0x0BB11477
    22. No device found on SWD.
    23. Did not find any core.
    Display All


    So it can connect to the debugger, but not contact the device.

    Throughout these phases, I've always been able to use the "Recover" command in the latest version of nRFgo Studio.

    My questions are:

    1. Does anyone know a sequence of commands that does the same thing as Recover in nRFgo Studio?

    2. Do you have any suggestions for how to get JLinkGDBServer up and running? I was thinking that I could put some commands in a script to be launched with JLinkGDBServer, but I'm not sure what the non-interactive version of selemu is.