Hi
I'm having trouble trying to get the stack pointer to be where I want it using MCUExpresso with the imxrt1052.
I'm using version 10.2.1 of the IDE and version 2.5.0 of the EVKB-IMXRT1050 SDK.
My memory is configured thus which is pretty standard:
And I've configured the linker to link the application to RAM and to set the heap and stack to SDRAM as shown below:
However when I set a breakpoint in the ResetISR function the stack pointer (r13) is always in the internal SRAM_OC area:
The linker map file shows exactly what I expect it to show as shown here:
/* Reserve and place Heap within memory map */
_HeapSize = 0x800000;
.heap : ALIGN(4)
{
_pvHeapStart = .;
. += _HeapSize;
. = ALIGN(4);
_pvHeapLimit = .;
} > BOARD_SDRAM
_StackSize = 0x200000;
/* Reserve space in memory for Stack */
.heap2stackfill :
{
. += _StackSize;
} > BOARD_SDRAM
/* Locate actual Stack in memory map */
.stack ORIGIN(BOARD_SDRAM) + LENGTH(BOARD_SDRAM) - _StackSize - 0: ALIGN(4)
{
_vStackBase = .;
. = ALIGN(4);
_vStackTop = . + _StackSize;
} > BOARD_SDRAM
I've tried cleaning the build and also creating a small application with no frills straight from the SDK and that doesn't help. I've also tried removing the BOARD_FLASH memory and also the internal SRAMs so that I only have SDRAM and that makes no difference.
If you look carefully at the code snippet in the last pic you can see where I've commented out manually setting the sp using the _vStackTop value set by the linker. This kinda does work in that the stack pointer gets set properly, but I find that the application dies after a while due to stack corruption of a C++ object that was created on the stack within main.
Any ideas?
Hi Gary,
The issue you are seeing is a consequence of debugging a RAM based image with SEGGER and is described correctly by SEGGER in that their debug environment does not set the initial stack pointer based on the image - instead it is inherited from the previous application (likely the bootROM).
In contrast a LinkServer/CMSIS-DAP debug (the default if using the OpenSDA debug probe) will identify that you are debugging from RAM and setup the stack based on the setting in the image - e.g. see text snip from a LinkServer debug log below:
Starting execution using soft reset with PC 0x200002F1 SP 0x20020000 from load at 0x20000000
Note: in this example, the SP is set to the top of the first RAM bank i.e. the top of the D_TCM in this case.
If you look at the binary values at the start of the image in RAM, you will see the linker has correctly inserted the SP value (first entry) based on the managed linkerscript settings and also the entry point for the image:
If an image is run using an actual reset (e.g. from Flash) then the bootROM would mimic the cortex hardware setup and set the stack based on the image.
I hope this helps,
Yours,
MCUXpresso IDE Support
Hi，
I would recommend customer to refer MCUXpresso SDK [hello world] project for MIMXRT1050-EVKB.
During SDK example project importing, please select [Link application to RAM].
Please refer the <evkbimxrt1050_hello_world_Debug.ld> file, I could check the heap and stack located at BOARD_SDRAM.
During debug, the stack pointer located at SDRAM memory:
I would recommend customer to update MCUXpresso IDE software.
Below is my MCUXpresso IDE software version info:
MCUXpresso IDE v10.3.0_prc3 [Build 2187] [2018-11-18]
Wish it helps.
Have a great day,
Mike
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi
Thanks for the reply. I did try that before but I did it again just to be sure. I imported the helloworld example from the latest SDK and made sure to select 'Link application to RAM' in the wizard. However it still shows the SP as being in the wrong place as shown in the follow screenshot...
Hi
I have tried installing version 10.3.0 and the problem is still there. I checked the release notes for 10.3.0 and it doesn't mention anything about this issue anyway.
I tried importing the helloworld demo that I had created in the previous version and that still showed the incorrect stack and so I completely deleted this project and created it new with the new IDE. This still shows the wrong stack:
Hi,
Could you check the board jumper setting?
BTW: The SW7 value is 0110.
During the debug, I am using on board OpenSDA.
Have a great day,
Mike
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi,
I can regenerate the issue with a standalone Segger J-Link Plus tool.
The stack point at 0x20200fe8.
I am checking with Segger about this issue.
I will let you know when there with any feedback.
Thanks for the patience.
Have a great day,
Mike
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi Gary,
Sorry for the later reply.
I got below feedback from Segger engineer:
best regards,
Mike
