[ABANDONED] Can't connect to M4 core of STM32MP1 (STM32MP157)

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

  • [ABANDONED] Can't connect to M4 core of STM32MP1 (STM32MP157)

    I can successfully connect to both A7 cores of my STM32MP157 board with either of these commands:

    Source Code

    1. JLinkGDBServer -device STM32MP15xx_A7_0_DualFlash
    2. JLinkGDBServer -device STM32MP15xx_A7_1_DualFlash


    However, I cannot connect to the M4 core of the processor. If I attempt to default to the JTAG interface, it just says "ERROR: Could not connect to target" — if I connect via SWD, it shows more promise:

    Source Code

    1. $ JLinkGDBServer -device STM32MP15xx_M4_DualFlash -if swd
    2. SEGGER J-Link GDB Server V6.80d Command Line Version
    4. JLinkARM.dll V6.80d (DLL compiled Jun 26 2020 17:19:40)
    6. Command line: -device STM32MP15xx_M4_DualFlash -if swd
    7. -----GDB Server start settings-----
    8. GDBInit file: none
    9. GDB Server Listening port: 2331
    10. SWO raw output listening port: 2332
    11. Terminal I/O port: 2333
    12. Accept remote connection: yes
    13. Generate logfile: off
    14. Verify download: off
    15. Init regs on start: off
    16. Silent mode: off
    17. Single run mode: off
    18. Target connection timeout: 0 ms
    19. ------J-Link related settings------
    20. J-Link Host interface: USB
    21. J-Link script: none
    22. J-Link settings file: none
    23. ------Target related settings------
    24. Target device: STM32MP15xx_M4_DualFlash
    25. Target interface: SWD
    26. Target interface speed: 4000kHz
    27. Target endian: little
    29. Connecting to J-Link...
    30. J-Link is connected.
    31. Firmware: J-Trace PRO V2 Cortex compiled Jun 9 2020 13:39:29
    32. Hardware: V2.00
    33. S/N: 932000281
    34. Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
    35. Checking target voltage...
    36. Target voltage: 3.31 V
    37. Listening on TCP/IP port 2331
    38. Connecting to target...
    39. WARNING: Identified core does not match configuration. (Found: Cortex-M0, Configured: Cortex-M4)
    40. WARNING: CPU could not be halted
    41. Halting target device failed. Trying again with reset
    42. WARNING: CPU could not be halted
    43. WARNING: CPU could not be halted
    44. WARNING: CPU could not be halted
    45. ERROR: Failed to halt CPU.
    46. WARNING: CPU could not be halted
    47. Failed to halt target device on connect
    48. ERROR: Could not connect to target.
    49. Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
    50. Shutting down...
    51. Could not connect to target.
    52. Please check power, connection and settings.
    Display All
    I also tried upgrading to the latest version of J-Link software (6.86d), but that also didn't fix things (and ended up presenting a different error):

    Source Code

    1. Connecting to target...
    2. Halting target device failed. Trying again with reset
    3. ERROR: Failed to halt CPU.
    4. Failed to halt target device on connect
    5. ERROR: Could not connect to target.
    6. Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
    7. Shutting down...
    8. Could not connect to target.
    Any ideas what's going on? I was wondering if there was some sort of clock gating / power gating thing I had to enable on the Linux side of things to get the processor to work, but I didn't see anything from ST about this.

  • Hi,
    Thank you for your inquiry.

    Unfortunately, we were not able to recreate this issue:


    Setup:
    - J-Link Plus V10
    - J-Link GDB Server v6.86d
    - STM32MP15X-EVAL evaluation board (STM32MP157AAA3).

    Could you please retry with the latest J-Link Version? You can download it here.
    Are you using an evaluation board or custom hardware?
    If evaluation board, which one? If custom hardware, are you able to reproduce this on an evaluation board?

    Could you please send us a J-Link log file? How to enable:
    wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File

    Best regards,
    Fabian
    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.