2021-11-02 09:17 AM
Impossible to launch the debugger with the following configuration:
See log files
STm32cubeProg 2.8.1 can connect to the board successfully.
What is wrong ?
BUG ?
Solved! Go to Solution.
2021-11-05 03:16 AM
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.
2021-11-02 09:21 AM
maybe you didnt closed the STM32CubeProg session so the gdb server is busy? it happens to me sometimes
2021-11-02 10:43 AM
I admit that I have also made this mistake more than once, but not in this case.
thanks
2021-11-02 11:12 AM
Hello,
Can you try to decrease the STLink SWD frequency.
If not better, can you try with OpenOcd gdb server.
Rgds,
Laurent
2021-11-05 02:36 AM
@MFred.2 , did you solve the issue with Laurent's advice?
2021-11-05 03:05 AM
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
2021-11-05 03:16 AM
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.
2021-11-05 03:36 AM
thank you for this information,
This problem is therefore already known
I didn't think about reading this errata sheet, sorry
2021-11-10 02:32 AM
Thanks @mattias norlander for sharing this STM32CubeIDE errata reference. It is helpful to make our community aware about it.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.