cancel
Showing results for 
Search instead for 
Did you mean: 

error on address

creeper
Associate II

I'm trying to use the LCD screen in STM32N6570DK, but it has an error like this`Break at address "0x18003a1a" with no debug information available, or outside of program code.`. But when I tried to view the vector table generated by disassembly, It will produce such a result ` Failed to execute MI command:
-data-disassemble -s 34181902 -e 34182090 -- 2
Error message from debugger back end:
Cannot access memory at address 0x209930e`, 

creeper_0-1746500539292.png

But these errors don't happen every time

2 REPLIES 2
KDJEM.1
ST Employee

Hello @creeper ;

 

Do you get the same issue when running an LCD example from STM32CubeN6 package like as LTDC_Horizontal_Mirroring?

To execute this project, I recommend you to follow the steps shared in the readme.

KDJEM1_0-1747318472068.png

Thank you.

Kaouthar

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Yes, because there's no code/data from the built application there, or the memory location doesn't exist in the hardware.

It's vectored off to some junk address, most likely because your code has trashed the stack.

What you need to do is inspect and unwind the stack, and determine how it got to this location.

Add instrumentation, perhaps as UART or SWV output, so you can trace the dynamic execution immediately prior to the failure.

Look at code with large local/auto variable allocation, those with insufficient, and situations where you copy unbounded data or strings into the stack.

The Vector Table is NOT CODE, it's pointers to subroutines in a list / tabular form. Disassembling it won't help, dump as uint32_t's

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..