nrf51 - hangout on linux

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

  • nrf51 - hangout on linux

    Hello,

    I'm using segger jlite to debug an nrf51822 on linux :

    C Source Code

    1. JLinkExe --version
    2. SEGGER J-Link Commander V5.02e ('?' for help)
    3. Compiled Sep 25 2015 18:00:06


    I upload code with JLinkExe using this script :

    C Source Code

    1. power on
    2. r
    3. loadbin RFDUINO_DEBUG/container_node.hex 0x00016000
    4. r
    5. qc


    invoked with :

    C Source Code

    1. JLinkExe -Device nrf51822 -If SWD


    Upload works fine but after if I try to reconnect :

    C Source Code

    1. JLinkExe -Device nrf51822 -If SWD
    2. SEGGER J-Link Commander V5.02e ('?' for help)
    3. Compiled Sep 25 2015 18:00:06
    4. Can not connect to J-Link via USB.


    or :

    C Source Code

    1. JLinkGDBServer -Device nrf51822 -If SWD
    2. SEGGER J-Link GDB Server V5.02e Command Line Version
    4. JLinkARM.dll V5.02e (DLL compiled Sep 25 2015 18:00:01)
    6. -----GDB Server start settings-----
    7. GDBInit file: none
    8. GDB Server Listening port: 2331
    9. SWO raw output listening port: 2332
    10. Terminal I/O port: 2333
    11. Accept remote connection: yes
    12. Generate logfile: off
    13. Verify download: off
    14. Init regs on start: off
    15. Silent mode: off
    16. Single run mode: off
    17. Target connection timeout: 0 ms
    18. ------J-Link related settings------
    19. J-Link Host interface: USB
    20. J-Link script: none
    21. J-Link settings file: none
    22. ------Target related settings------
    23. Target device: nrf51822
    24. Target interface: SWD
    25. Target interface speed: 1000kHz
    26. Target endian: little
    28. Connecting to J-Link...
    29. Connecting to J-Link failed. Connected correctly?
    30. GDBServer will be closed...
    31. Shutting down...
    32. Could not connect to J-Link.
    33. Please check power, connection and settings.
    Display All


    I must disconnect USB in order to reflash or debug.

    How can we solve it?

    Regards

  • Hi Lah,


    can you please describe the output of the status LED of your J-Link Lite? Does the behavior of the status LED change after the download?
    Can your provide a usbmon logfile of a session and / or a lsusb dump of your J-Link?

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Lah,

    could you please give V5.03e a try? segger.com/jlink-software-beta-version.html
    The error causing this faulty behavior should be fixed in this version.

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Niklas,

    Unfortunately, issue has not been solved in V5.03f. I cannot flash twice without unplugging usb cable.

    Below is result when cable is not disconnected between two flashings.

    Source Code

    1. JLink_Linux_V503f_x86_64 :( $ ./JLinkExe -Device nrf51822 -If SWD
    2. SEGGER J-Link Commander V5.03f ('?' for help)
    3. Compiled Oct 27 2015 16:48:15
    4. Info: Device "NRF51822_XXAA" selected.
    5. DLL version V5.03f, compiled Oct 27 2015 16:48:11
    6. Firmware: J-Link Lite-Cortex-M V8 compiled Aug 20 2015 17:57:19
    7. Hardware: V8.00
    8. S/N: 518108796
    9. Feature(s): GDB
    10. Emulator has Trace capability
    11. VTarget = 3.319V
    12. Info: Found SWD-DP with ID 0x0BB11477
    13. Info: Found Cortex-M0 r0p0, Little endian.
    14. Info: FPUnit: 4 code (BP) slots and 0 literal slots
    15. Info: CoreSight components:
    16. Info: ROMTbl 0 @ F0000000
    17. Info: ROMTbl 0 [0]: F00FF000, CID: B105100D, PID: 000BB471 ROM Table
    18. Info: ROMTbl 1 @ E00FF000
    19. Info: ROMTbl 1 [0]: FFF0F000, CID: B105E00D, PID: 000BB008 SCS
    20. Info: ROMTbl 1 [1]: FFF02000, CID: B105E00D, PID: 000BB00A DWT
    21. Info: ROMTbl 1 [2]: FFF03000, CID: B105E00D, PID: 000BB00B FPB
    22. Info: ROMTbl 0 [1]: 00002000, CID: B105900D, PID: 000BB9A3 ???
    23. Cortex-M0 identified.
    24. Target interface speed: 100 kHz
    25. J-Link>power on
    26. J-Link>r
    27. Reset delay: 0 ms
    28. Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
    29. J-Link>loadbin container_node.hex 0x00016000
    30. Downloading file [container_node.hex]...Info: J-Link: Flash download: Flash download skipped. Flash contents already match
    31. O.K.
    32. J-Link>r
    33. Reset delay: 0 ms
    34. Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
    35. J-Link>qc
    36. JLink_Linux_V503f_x86_64 $ ./JLinkExe -Device nrf51822 -If SWD
    37. SEGGER J-Link Commander V5.03f ('?' for help)
    38. Compiled Oct 27 2015 16:48:15
    39. Can not connect to J-Link via USB.
    40. J-Link>
    Display All


    lah

  • Hi lah,


    I am sorry to hear that your still facing issues.
    Unfortunately, our USB-Department could not yet identify the reason for this behavior.
    They currently are busy working on another support case. When they are finished, they will investigate this problem.


    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.