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,

    you can recognize the stack of which the exception had been occurred by checking the bit 2 of the EXE_RETRUN code which is stored into r14 (aka. lr).
    Regarding the implementation of the hard fault handler, please refer to Re: Re: error: Hard Fault Handler  .

    Regarding the second issue, there would be no reason to identfy of the hard fault cause. You should imagine by the information of PC, BFAR, CFAR, HFSR, DFSR and AFSR.

    Best Regards,
    Yasuhiko Koumoto.

Reply
  • Hi matic,

    you can recognize the stack of which the exception had been occurred by checking the bit 2 of the EXE_RETRUN code which is stored into r14 (aka. lr).
    Regarding the implementation of the hard fault handler, please refer to Re: Re: error: Hard Fault Handler  .

    Regarding the second issue, there would be no reason to identfy of the hard fault cause. You should imagine by the information of PC, BFAR, CFAR, HFSR, DFSR and AFSR.

    Best Regards,
    Yasuhiko Koumoto.

Children