cancel
Showing results for 
Search instead for 
Did you mean: 

Break at address "0x8000B2C" with no debug information

Duc
Associate III

Hi all,

I followed this STM32CubeIDE tutorial to debug an STM32H7S3L8 project running from external flash (OSPI NOR). After flashing and starting the debug session, I get the following error:

Break at address "0x8000B2C" with no debug information available, or outside of program code.

Here is the log from STM32CubeProgrammer:

STMicroelectronics ST-LINK GDB server. Version 7.11.0
Copyright (c) 2025, STMicroelectronics. All rights reserved.

Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
InitWhile : Enabled

Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
-------------------------------------------------------------------
STM32CubeProgrammer v2.20.0
-------------------------------------------------------------------

Log output file: C:\Users\Admin\AppData\Local\Temp\STM32CubeProgrammer_a10720.log
ST-LINK SN : 004B00273433511737363934
ST-LINK FW : V3J16M9
Board : NUCLEO-H7S3L8
Voltage : 3.29V
SWD freq : 8000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x485
Revision ID : Rev B
Device name : STM32H7RSxx
Flash size : 64 KBytes (default)
Device type : MCU
Device CPU : Cortex-M7
BL Version : 0xE4

Opening and parsing file: ST-LINK_GDB_server_a10720.srec

Memory Programming ...
File : ST-LINK_GDB_server_a10720.srec
Size : 15.16 KB
Address : 0x70000000

Erasing memory corresponding to segment 0:
Erasing external memory sector 0
Download in Progress:

File download complete
Time elapsed during download operation: 00:00:00.404
-------------------------------------------------------------------
STM32CubeProgrammer v2.20.0
-------------------------------------------------------------------

Log output file: C:\Users\Admin\AppData\Local\Temp\STM32CubeProgrammer_a10720.log
ST-LINK SN : 004B00273433511737363934
ST-LINK FW : V3J16M9
Board : NUCLEO-H7S3L8
Voltage : 3.29V
SWD freq : 8000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x485
Revision ID : Rev B
Device name : STM32H7RSxx
Flash size : 64 KBytes (default)
Device type : MCU
Device CPU : Cortex-M7
BL Version : 0xE4

Opening and parsing file: ST-LINK_GDB_server_a10720.srec

Memory Programming ...
File : ST-LINK_GDB_server_a10720.srec
Size : 43.75 KB
Address : 0x08000000

Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 5]
Download in Progress:

File download complete

My question: Why does the program break at 0x8000B2C after following this tutorial? How can I fix this issue and get debugging working with external flash?

Thanks in advance!

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Duc
Associate III

Hi @MHoll.2 ,

Enabling the "Load symbols" option has resolved the initial issue.

Duc_0-1754125849170.png

However, there's a new issue with the code generated by CubeMX. It seems to get stuck at the SCB_EnableDCache() function for a while before jumping to the Error_Handler(void). I suspect there might be a configuration problem with the template code for the NUCLEO-H7S3L8.

View solution in original post

4 REPLIES 4
PhucXDoan
Associate III

Just spitting here: it's possible that no debug information is being made.

Does your program work (e.g. blinking LED)?

If so, then see if you can pass a compiler flag so that the compiler puts debug information in the ELF file.

Duc
Associate III

Hi @PhucXDoan ,

No, my program isn’t working. The NUCLEO-H7S3L8 is new to me, and I’m trying to get it set up, but the issue is the first thing that’s blocking me from moving forward with it.

MHoll.2
Senior III

0x08000B2C is in the internal user Flash, so You probably have some problem inside the bootloader (who init's the OSPI Flash).

What happens if You click run?

Duc
Associate III

Hi @MHoll.2 ,

Enabling the "Load symbols" option has resolved the initial issue.

Duc_0-1754125849170.png

However, there's a new issue with the code generated by CubeMX. It seems to get stuck at the SCB_EnableDCache() function for a while before jumping to the Error_Handler(void). I suspect there might be a configuration problem with the template code for the NUCLEO-H7S3L8.