Skip to main content
devtty
Associate III
March 30, 2022
Question

Break at address "0x1fff523e" with no debug information available

  • March 30, 2022
  • 4 replies
  • 2545 views

I am using STMCubeIDE to program a nucleo-L4R5ZI. When i go to debug i get "Break at address "0x1fff523e" with no debug information available, or outside of program code." This only happens with my L4R5ZI boards. The code doesn't run unless I disconnect the board and then reconnect (then the program actually launches). Debug works fine on my l476rg.

I tried applying the fix in this thread:

https://community.st.com/s/question/0D53W00000raYd2SAE/intermittent-break-at-address-0x1fff51f4-with-no-debug

but it didnt work. Anyone have any ideas what could be going wrong?

Thanks.

This topic has been closed for replies.

4 replies

Tesla DeLorean
Guru
March 30, 2022

Power cycle and Reset behave differently, states are latched based on the viability of the image in flash, and simple resets won't clear that.

What you're seeing is indicative of code running from ROM

Would suggest that you make sure that the FLASH is properly mapped into the Zero Address space, and the SCB->VTOR is set appropriately. Put code to facilitate this in the Reset_Handler, so it's the first thing run.

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
devtty
devttyAuthor
Associate III
April 1, 2022

I worked around it by unchecking nSWBOOT0 option byte which meant BOOT0 was taken from option bit nBOOT0 instead of from PH3/BOOT0 pin. I then was able to debug without an issue, I then rechecked "nSWBOOT0" and programmed and its still working fine. Not sure why this worked but I will still investigate and make sure flash is properly mapped into zero address space and scb->vtor is set correctly jussst in case.

Thanks.

BAdmi.1
Associate
April 25, 2022

Solved it for me aswell, the option can be found in STM32CubeProgrammer -> Option bytes -> User Configuration

devtty
devttyAuthor
Associate III
April 26, 2022

Setting SCB->VTOR to 0x08000000 in SystemInit() within the system_stm32l4xx.c also seems to do the trick for me.