Step Into Function when functions are different memory areas (LPCXPresso IDE)

Discussion created by lpcware Employee on Jun 15, 2016
Latest reply on Jun 15, 2016 by lpcware
Content originally posted in LPCWare by ajones on Wed Dec 11 05:01:22 MST 2013
I am using the LPCXPresso IDE.

I have code that is configured to execute from internal SRAM and external SDRAM.

The linker places a __FunctionName_veneer function to handle the large address offset required by the function being in different memory areas.

The debugger won't step into the veneer function when debugging at the C code level - it will do it when I instruction step in the Disassembler Window.

I presume the problem is that the veneer function has no debug information and hence debugger chooses to step over rather than step into.

Any ideas on convincing the debugger to perform a step into the function in this situation?