[SOLVED] Nucleo-F303RE - CPU could not be halted

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

  • [SOLVED] Nucleo-F303RE - CPU could not be halted

    Hello,

    I am using STM32 Nucleo-F446RE board to program and debug a custom STM32F3 board through J-Link and it works fine. To be able to debug the communication between 2 of my custom boards I wanted to debug them both simultaneously, so I bought a second Nucleo board, this time STM32 Nucleo-F303RE. However I can't make the new Nucleo flash and debug my microcontroller.

    I used the Reflash Utility to convert the ST-Link into J-link. I tested it and it didn't work, so I updated the firmware, but no result.

    I use the exactly same setup with both Nucleos: same target board, same cables, same jumper configuration. I use Eclipse IDE as a programming environment. Here are both SEGGER logs (working and not working) that I get:

    SEGGER Log for Nucleo-F446RE (working):

    Brainfuck Source Code

    1. SEGGER J-Link GDB Server V6.60f Command Line Version
    3. JLinkARM.dll V6.60f (DLL compiled Jan 20 2020 16:15:17)
    5. Command line: -if swd -device STM32F303CB -endian little -speed 1000 -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0 -nogui
    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: localhost only
    12. Generate logfile: off
    13. Verify download: on
    14. Init regs on start: on
    15. Silent mode: off
    16. Single run mode: on
    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: STM32F303CB
    24. Target interface: SWD
    25. Target interface speed: 1000kHz
    26. Target endian: little
    28. Connecting to J-Link...
    29. J-Link is connected.
    30. Firmware: J-Link STLink V21 compiled Jun 26 2017 10:35:16
    31. Hardware: V1.00
    32. S/N: 774801057
    33. Checking target voltage...
    34. Target voltage: 3.30 V
    35. Listening on TCP/IP port 2331
    36. Connecting to target...
    37. Connected to target
    38. Waiting for GDB connection...Connected to 127.0.0.1
    39. Reading all registers
    40. Read 4 bytes @ address 0x00000000 (Data = 0x2000A000)
    41. Read 2 bytes @ address 0x00000000 (Data = 0xA000)
    42. Received monitor command: speed 1000
    43. Target interface speed set to 1000 kHz
    44. Received monitor command: clrbp
    45. Received monitor command: reset
    46. Resetting target
    47. Received monitor command: halt
    48. Halting target CPU...
    49. ...Target halted (PC = 0x0000029C)
    50. Received monitor command: regs
    51. R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
    52. R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
    53. R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
    54. R12= 00000000, R13= 2000A000, MSP= 2000A000, PSP= 00000000
    55. R14(LR) = FFFFFFFF, R15(PC) = 0000029C
    56. XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    57. CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    58. Reading all registers
    59. Read 4 bytes @ address 0x0000029C (Data = 0xF7FFB508)
    60. Read 2 bytes @ address 0x0000029C (Data = 0xB508)
    61. Received monitor command: speed auto
    62. Select auto target interface speed (2000 kHz)
    63. Received monitor command: flash breakpoints 0
    64. Flash breakpoints disabled
    65. Received monitor command: semihosting enable
    66. Semi-hosting enabled (Handle on BKPT)
    67. Received monitor command: semihosting IOClient 3
    68. Semihosting I/O set to TELNET and GDB Client
    69. Read 4 bytes @ address 0x0000029C (Data = 0xF7FFB508)
    70. Downloading 928 bytes @ address 0x00000000 - Verified OK
    71. Downloading 40 bytes @ address 0x000003A0 - Verified OK
    72. Downloading 4096 bytes @ address 0x000003D0 - Verified OK
    73. Downloading 4096 bytes @ address 0x000013D0 - Verified OK
    74. Downloading 4096 bytes @ address 0x000023D0 - Verified OK
    75. Downloading 4096 bytes @ address 0x000033D0 - Verified OK
    76. Downloading 4096 bytes @ address 0x000043D0 - Verified OK
    77. Downloading 4096 bytes @ address 0x000053D0 - Verified OK
    78. Downloading 4096 bytes @ address 0x000063D0 - Verified OK
    79. Downloading 4096 bytes @ address 0x000073D0 - Verified OK
    80. Downloading 2011 bytes @ address 0x000083D0 - Verified OK
    81. Downloading 8 bytes @ address 0x00008BAC - Verified OK
    82. Downloading 1548 bytes @ address 0x00008BB4 - Verified OK
    83. Comparing flash [....................] Done.
    84. Writing register (PC = 0x 188)
    85. Read 4 bytes @ address 0x00000188 (Data = 0xB083B500)
    86. Received monitor command: clrbp
    87. Received monitor command: reset
    88. Resetting target
    89. Received monitor command: halt
    90. Halting target CPU...
    91. ...Target halted (PC = 0x0000029C)
    92. Received monitor command: regs
    93. R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
    94. R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
    95. R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
    96. R12= 00000000, R13= 2000A000, MSP= 2000A000, PSP= 00000000
    97. R14(LR) = FFFFFFFF, R15(PC) = 0000029C
    98. XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    99. CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    100. Reading all registers
    101. Read 4 bytes @ address 0x0000029C (Data = 0xF7FFB508)
    102. Starting target CPU...
    Display All

    SEGGER Log for Nucleo-F303RE (not working):

    Source Code

    1. Could not connect to target.
    2. Please check power, connection and settings.SEGGER J-Link GDB Server V6.60f Command Line Version
    4. JLinkARM.dll V6.60f (DLL compiled Jan 20 2020 16:15:17)
    6. Command line: -if swd -device STM32F303CB -endian little -speed 1000 -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0 -nogui
    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: localhost only
    13. Generate logfile: off
    14. Verify download: on
    15. Init regs on start: on
    16. Silent mode: off
    17. Single run mode: on
    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: STM32F303CB
    25. Target interface: SWD
    26. Target interface speed: 1000kHz
    27. Target endian: little
    29. Connecting to J-Link...
    30. J-Link is connected.
    31. Firmware: J-Link STLink V21 compiled Aug 12 2019 10:29:20
    32. Hardware: V1.00
    33. S/N: 775245505
    34. Checking target voltage...
    35. Target voltage: 3.30 V
    36. Listening on TCP/IP port 2331
    37. Connecting to target...
    38. WARNING: CPU could not be halted
    39. Halting target device failed. Trying again with reset
    40. WARNING: CPU could not be halted
    41. WARNING: CPU could not be halted
    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...
    Display All


    When I use the J-Link Commander I get a similar message that the CPU could not be halted.

    I tried to upload the Blinky example to the on-board STM32F303RE controller and it works fine.

    What could be causing this behaviour? Any help would be appreciated.

    The post was edited 2 times, last by s7iVuR ().

  • Hi,
    Thank you for your inquiry.

    Please note that the usage of the J-Link on the ST board in such way is a license violation and illegal.
    You can read the license agreement in the daily pop-up and here:
    segger.com/products/debug-prob…nk-on-board/#terms-of-use

    Since you seem to be using this setup in an educational purpose please find information about our official products for educational use here:
    Small/cheaper version: segger.com/products/debug-prob…k/models/j-link-edu-mini/
    More robust version with more features: segger.com/products/debug-probes/j-link/models/j-link-edu/

    Pros:
    - Use is legal for private and educational purposes.
    - Cheaper than most evaluation boards, so it should be affordable for any budget.
    - Supports all our supported devices.

    We will close this thread now.
    Please do not open further threads regarding this topic or we will have to remove you from this forum.

    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.