This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How and when to use separate stack pointers in a non-RTOS application?

Hi,

We are developing a safety critical product based on Cortex-M4 CPU. In the Definitive Guide for ARM Cortex-M3/4 I read that it is recommended to use both (MSP and SPS) stacks even, if program does not use RTOS. By using both stacks, the program is supposed to be more robust. I also see in the book how this should be implemented in the startup file, but I don't understand in which cases these separate stacks would be more beneficial than just one stack (MSP).

I would be very grateful, if someone could explain this a little bit.

Best regards.

Parents
  • Hi matic,

    Do you also suggest to have both stacks (MSP and PSP) guarded by the MPU at their bottom?

    Yes I do.
    I also recommend to make the stack regions never executable.

    If I understand well, then this would be advisable to detect stack overflow on any of stacks, right?

    No, it is not for the stack overflow but also for guarding the malicious program execution on each stack.

    Best regards,
    Yasuhiko Koumoto.

Reply
  • Hi matic,

    Do you also suggest to have both stacks (MSP and PSP) guarded by the MPU at their bottom?

    Yes I do.
    I also recommend to make the stack regions never executable.

    If I understand well, then this would be advisable to detect stack overflow on any of stacks, right?

    No, it is not for the stack overflow but also for guarding the malicious program execution on each stack.

    Best regards,
    Yasuhiko Koumoto.

Children