STM32CubeIDE Advanced Debug Features: Part 4

preview_player
Показать описание

Learn how to create your STM32-based application using STM32CubeIDE and use its Advanced Debug Features to enhance your debugging skill set with the NUCLEO-F401RE board and use this knowledge as the basis for your own application using any STM32 with ARM Cortex M3/M4/M7/M23 or M33 cores.

The STM32CubeIDE can be used to create applications for STM32 devices using STM32Cube libraries (HAL and Low Layer versions) and this video series will cover the features for debugging one simple application firmware using that as the basis and augment the debug experience by using the Instrumentation Trace Macrocell (ITM) and the Serial Wire Viewer (SWV) with several different hands-on sessions to explain all possible views and setups in the debug session.

In this video:
Learn how to use:
• printf() in STM32CubeIDE
• Serial Wire Output and the Instrumentation Trace Macrocell (ITM) to redirect the printf()
• SWV ITM Data Console
• Special breakpoints, which can also be used to print information in the debugger console – called dynamic breakpoints

Also included are steps to fully configure your debug perspective for the Serial Wire Viewer Settings, covering:
• Clock Settings
• Trace Events
• PC Sampling
• Data Trace
• ITM Stimulus Ports
Рекомендации по теме
Комментарии
Автор

But is seems SWD printf() doesn't print all messages.
We can see "Loop Counter = XX" skip some values

edouardmalot
Автор

Why cant a multi million dollar company invest a few dollars into a proper microphone, so their engineers don't need to use a potato to record a tutorial video?

Seff
Автор

When I click the on "Configure Trace" for the SWV ITM Data Console nothing happens, I'm using Version: 1.6.1 Build: 9958_20210326_1446 (UTC) on Win 10, and I have also tried it on Linux without success; is this a bug, am I doing something wrong, or is there another way to open the "Serial Wire viewer settings for Debug Debug"?

Steven_Bennett_YT
Автор

Starting the Trace every time is so annoying. How about showing us a proper redirect of printf() to an UART. That would be so much more usefull...

iAnguel
welcome to shbcf.ru