Skip to main content
Pavel A.
Super User
July 14, 2021
Solved

[SOLVED] Weird behavior debugging STM32H753

  • July 14, 2021
  • 2 replies
  • 955 views

Dear experts,

I hit a strange problem when debugging in CubeIDE code with a bootloader on Nucleo STM32H753.

The bootloader sits in sector 14. The boot address of STM32H7 is redirected there via the option bytes. The main code starts at sector 0 (a.k.a. the default start address 0x08000000).

Very often after starting debug session the bootloader gets hardfault very early.

The debugger in use is ST-LINK server, with all settings default.

Without debugger connected, the bootloader works as expected and jumps to main code.

Also, in a different arrangement with bootloader in sector 0 and main code elsewhere, debug session usually starts well.

Anybody seen this behavior and can offer some advise?

--pa

This topic has been closed for replies.
Best answer by waclawek.jan

> Very often after starting debug session the bootloader gets hardfault very early.

Debug the hardfault as usually.

JW

2 replies

waclawek.jan
waclawek.janBest answer
Super User
July 15, 2021

> Very often after starting debug session the bootloader gets hardfault very early.

Debug the hardfault as usually.

JW

Pavel A.
Pavel A.Author
Super User
July 16, 2021

Sorry. It was a stupid error in my debug config ((. It happens.