JLink (V6.00g, deb) Error: Could not connect to target

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

  • JLink (V6.00g, deb) Error: Could not connect to target

    Dear all,

    I could not connect my STM32F103ZE board and STM32F407VG Discovery board via Segger J-Link Plus (EDU version) on Ubuntu 14.04.5 LTS, while I can happily debug other boards on WIndows 7. ?(

    Jlink Software packs I used are both of the latest version V6.00g.

    Source Code

    1. $ JLinkGDBServer -device STM32F103ZE -if SWD -speed 1000


    Source Code

    1. SEGGER J-Link GDB Server V6.00g Command Line Version
    3. JLinkARM.dll V6.00g (DLL compiled Aug 17 2016 13:20:32)
    5. -----GDB Server start settings-----
    6. GDBInit file: none
    7. GDB Server Listening port: 2331
    8. SWO raw output listening port: 2332
    9. Terminal I/O port: 2333
    10. Accept remote connection: yes
    11. Generate logfile: off
    12. Verify download: off
    13. Init regs on start: off
    14. Silent mode: off
    15. Single run mode: off
    16. Target connection timeout: 0 ms
    17. ------J-Link related settings------
    18. J-Link Host interface: USB
    19. J-Link script: none
    20. J-Link settings file: none
    21. ------Target related settings------
    22. Target device: STM32F103ZE
    23. Target interface: SWD
    24. Target interface speed: 1000kHz
    25. Target endian: little
    27. Connecting to J-Link...
    28. J-Link is connected.
    29. Firmware: J-Link V9 compiled Aug 17 2016 11:20:49
    30. Hardware: V9.30
    31. S/N: 269306079
    32. OEM: SEGGER-EDU
    33. Feature(s): FlashBP, GDB
    34. Checking target voltage...
    35. Target voltage: 3.28 V
    36. Listening on TCP/IP port 2331
    37. Connecting to target...ERROR: STM32: Connecting to CPU via connect under reset failed.
    38. ERROR: STM32: Connecting to CPU via connect under reset failed.
    39. ERROR: Could not connect to target.
    40. Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
    41. Shutting down...
    42. Could not connect to target.
    43. Please check power, connection and settings.
    Display All


    Thank you and Best regards,
    Honig

  • STM32F407VG Discovery Board

    Source Code

    1. $ JLinkGDBServer -device STM32F407VG -if SWD


    Source Code

    1. SEGGER J-Link GDB Server V6.00g Command Line Version
    3. JLinkARM.dll V6.00g (DLL compiled Aug 17 2016 13:20:32)
    5. -----GDB Server start settings-----
    6. GDBInit file: none
    7. GDB Server Listening port: 2331
    8. SWO raw output listening port: 2332
    9. Terminal I/O port: 2333
    10. Accept remote connection: yes
    11. Generate logfile: off
    12. Verify download: off
    13. Init regs on start: off
    14. Silent mode: off
    15. Single run mode: off
    16. Target connection timeout: 0 ms
    17. ------J-Link related settings------
    18. J-Link Host interface: USB
    19. J-Link script: none
    20. J-Link settings file: none
    21. ------Target related settings------
    22. Target device: STM32F407VG
    23. Target interface: SWD
    24. Target interface speed: 1000kHz
    25. Target endian: little
    27. Connecting to J-Link...
    28. J-Link is connected.
    29. Firmware: J-Link V9 compiled Aug 17 2016 11:20:49
    30. Hardware: V9.30
    31. S/N: 269306079
    32. OEM: SEGGER-EDU
    33. Feature(s): FlashBP, GDB
    34. Checking target voltage...
    35. Target voltage: 3.29 V
    36. Listening on TCP/IP port 2331
    37. Connecting to target...Connected to target
    38. Waiting for GDB connection...
    Display All


    still Waiting ... for over 30 min.

    Thank you and Best regards,
    Honig

  • Update 1

    Dear all,

    Downloaded (V512j, .deb) , remove V600g and install this older version.

    STM32F4Disc Board connected successful, step into Debug perspective in Eclipse.

    STM32F103 still not work, the same error message as before:

    Source Code

    1. ERROR: STM32: Connecting to CPU via connect under reset failed.
    2. ERROR: STM32: Connecting to CPU via connect under reset failed.
    3. ERROR: Could not connect to target.

  • Hi,

    We are not aware of any issues with ST STM32F4 or ST STM32F1 series devices.
    According to your latest update, you are up and running with the ST STM32F4 board, correct?

    Regarding ST STM32F103:
    Do you use a custom hardware or an evaluation board? In latter case, which one?
    Can you please give it a try using the latest version V6.12? The version is available for download here: segger.com/downloads/jlink
    Please follow the instructions from the following troubleshoot article: wiki.segger.com/J-Link_can%27t…the_CPU#Target_connection
    If you run into any issues, please provide us the screenshot of the entire J-Link Commander output.


    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.