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

lpcware — Wed, 15 Jun 2016 18:27:18 GMT

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?

Regards,
Adrian

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

lpcware — Wed, 15 Jun 2016 18:27:19 GMT

Content originally posted in LPCWare by lpcxpresso-support on Wed Dec 11 07:38:16 MST 2013
I'm sorry, but I do not know of any way around this restriction. To step through stubs/veneers you have to single-step the assembler.

We will raise this issue with the ld maintainers.

LPC MicrocontrollersのトピックStep Into Function when functions are different memory areas (LPCXPresso IDE)

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

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