Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The dedicated option SKIP_WDT_TASK is defined in main.h in order to quickly enable/disable WDT in the project. To disable WDT set this option to 1 and rebuild the project:

    image-20241002-132222.png
  2. Click the Debug button at the top panel to start debugging:

    image-20241002-132244.png
  3. Select Remember my decision and switch to the Debug Perspective if prompted:

    image-20241002-132304.png
  4. Wait for the STM32CubeIDE to write the firmware image to the target via ST-Link and stop at the main() function:

    image-20241002-132349.pngImage Removed

    .

    At this point SDRAM is not initialized yet. Only the code that is located in the internal Flash or internal RAM is available for setting breakpoints. If there were breakpoints set by a previous debug session which refer to SDRAM, they need to be deactivated. The breakpoints in SDRAM can be re-activated later, when the initialization code has been performed.

    image-20241002-132349.pngImage Added
  5. Set a breakpoint after the MX_QUADSPI_Init() function is done:

    image-20241002-132421.pngImage Modified
  6. Proceed to execute the program.

  7. When the program stops at the breakpoint set in the 2 steps above, the QUADSPI interface is initialized and the application code is copied to SDRAM, so you can use breakpoints in the application code. Let's set a breakpoint at the prvHelpCommand() function in the CLI driver:

    image-20241002-132443.pngImage Modified
  8. Proceed to execute the program.

  9. Switch to the terminal with the serial console and type the help command:

    Code Block
    STM32H7 SOM FreeRTOS CLI, www.emcraft.com
    Type help to view a list of available commands.
    CLI> help
    
  10. Switch back to the debug session in the STM32CubeIDE. Make sure the execution is stopped at the breakpoint in the prvHelpCommand() function. Use the Step Over button to proceed the execution in a step-wise fashion:

    image-20241002-132501.pngImage Modified
  11. Proceed to execute the program in a step-wise fashion, set up breakpoints, examine variables and so on.

8. Known Problems and Limitations

...