Skip to main content
Visitor II
November 2, 2021
Solved

STM32CubeIDE, STM32U5 : unable to launch the debugger (gdbserver)

  • November 2, 2021
  • 6 replies
  • 4295 views

Impossible to launch the debugger with the following configuration:

  • STM32CubeIde1.7.0
  • Target Nucleo-U575ZI-Q
  • ST-link :
  1. Version: V3J8M3
  2. Build:  Apr 9 2021 20:49:40

See log files

STm32cubeProg 2.8.1 can connect to the board successfully.

What is wrong ?

BUG ?

    This topic has been closed for replies.
    Best answer by mattias norlander

    Stay below the 8MHz as specified in the errata: https://wiki.st.com/stm32mcu/wiki/STM32CubeIDE:STM32CubeIDE_errata_1.7.0#STM32U5

    The lower the better stability.

    6 replies

    Graduate II
    November 2, 2021

    maybe you didnt closed the STM32CubeProg session so the gdb server is busy? it happens to me sometimes

    MFred.2Author
    Visitor II
    November 2, 2021

    0693W00000GWFHpQAP.pngI admit that I have also made this mistake more than once, but not in this case.

    thanks

    ST Employee
    November 2, 2021

    Hello,

    Can you try to decrease the STLink SWD frequency.

    If not better, can you try with OpenOcd gdb server.

    Rgds,

    Laurent

    ST Employee
    November 5, 2021

    @MFred.2​ , did you solve the issue with Laurent's advice?

    MFred.2Author
    Visitor II
    November 5, 2021

    Hi,

    Indeed, decreasing the frequency of the St-link seems to improve the connection, but it is not very stable.

    The frequency of successful connection varies between 8Mhz and 21Mhz !

    I have not encountered this problem on other Nucleo board references.

    Regards

    Frederic

    ST Employee
    November 5, 2021

    Stay below the 8MHz as specified in the errata: https://wiki.st.com/stm32mcu/wiki/STM32CubeIDE:STM32CubeIDE_errata_1.7.0#STM32U5

    The lower the better stability.

    Technical Moderator
    November 10, 2021

    Thanks @mattias norlander​  for sharing this STM32CubeIDE errata reference. It is helpful to make our community aware about it.

    MFred.2Author
    Visitor II
    November 5, 2021

    thank you for this information,

    This problem is therefore already known

    I didn't think about reading this errata sheet, sorry