cancel
Showing results for 
Search instead for 
Did you mean: 

How to Debug STM32N645 above 0x34200000

mraehle
Associate II

Hi 
I have setup a small project in CubeMX v6.17.0 with FSBL and an application (secure domain only). As long as I use the default Flash and RAM region, debugging works fine. 

  ROM    (xrw)    : ORIGIN = 0x34000400,   LENGTH = 511K
  RAM    (xrw)    : ORIGIN = 0x34080000,   LENGTH = 1536K


In the future the application will be way bigger (using TouchGFX), therfore I increased the Flash Region to 1.5 MB and the RAM Region will start at 0x34200000 with a length of 1.5 MB as well. 

  ROM    (xrw)    : ORIGIN = 0x34000400,   LENGTH = 1536K
  RAM    (xrw)    : ORIGIN = 0x34200000,   LENGTH = 1536K


Since I made this change it is not possible to step into the application. FSBL works well and is loading the App data from external Flash into SRAM (0x34000000) as requested. After jumping into the app connection to target is lost as soon as SystemInit funciton is called. Debugger can't write any more: 

Cannot remove breakpoints because program is no longer writable.
Further execution is probably impossible.
0x3400095a in SystemInit () at ../Core/Src/system_stm32n6xx_s.c:177

mraehle_1-1777562667042.png

Has someone an idea what the problem could be.

thanks a lot
Markus

0 REPLIES 0