printf SWO, stlink
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-04-08 11:40 PM - edited 2024-04-11 08:14 AM
Hello everyone,
I program on stm32h757 with stm32cube IDE on macOS Sonoma. (stlink v3 minie)
Until recently, I debugged with the st link and displayed printf in the swv console without any problem.
For technical reasons, I made the program work with the st link and the J trace. Since then, printf only works with the J Trace.
When I use the st link, I get an error message at start-up (see attached image)
Can anyone help me?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-04-09 05:01 AM
Hello @MA4 and welcome to the community,
Could you please try the following tips to resolve this issue:
- Ensure that the ST-LINK USB drivers are installed or reinstall from here
- Check that the USB cable is properly connected to the PC.
- Download the SEGGER STLinkReflash utility from this link
- Start the STLinkReflash utility and restore ST-LINK
- Agree to the license terms
- Connect to CubeIDE and perform an ST-link firmware upgrade
- In the debug configuration, change the debugger to ST-LINK GDB Server. Do not forget to apply and close.
Hope this helps!
Thanks,
Rim.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-04-09 06:11 AM
Hello, thank you for your answer.
I still have the problem, same error message and the st link stops responding(Target is not responding, retrying... Shutting down... Target is not responding, retrying...)
I tried with another st link and same thing.
Is it possible that I have a problem with initialisation?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-04-09 07:34 AM - edited 2024-04-11 08:12 AM
Same error if I create a new project, if I upgrade de link, if I follow tuto only with printf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-04-11 03:03 AM - edited 2024-04-11 05:13 AM
I modified my debug configuration by checking "limit to clock" and setting 2000 kHz to max and now I get the error:
SWO trace already running on another core.
Any Idea ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2024-04-11 08:13 AM
after few try error comme back ...