Forced Hardfault (INVPC) Exception Error

Yes, potentially the stack space reserved is too small, and during the execution of the interrupt handler, the EXC_RETURN was pushed to the stack, corrupted by data processing operations, and then POP back from the stack and used for exception return. In many development toolchain you can reported the stack usage of code. You need to add the stack space needed by exception handlers and stack frame to get a good estimation of total required stack space.

If you are using Keil Microcontroller Development Kit (MDK) the stack size is usually defined in the startup code. If you are using an RTOS, the RTOS would also have stack size definitions for each thread and you need to look into the documentation from the RTOS vendor to see how to control the thread's stack sizes.

regards,

Joseph

Yes, potentially the stack space reserved is too small, and during the execution of the interrupt handler, the EXC_RETURN was pushed to the stack, corrupted by data processing operations, and then POP back from the stack and used for exception return. In many development toolchain you can reported the stack usage of code. You need to add the stack space needed by exception handlers and stack frame to get a good estimation of total required stack space.

If you are using Keil Microcontroller Development Kit (MDK) the stack size is usually defined in the startup code. If you are using an RTOS, the RTOS would also have stack size definitions for each thread and you need to look into the documentation from the RTOS vendor to see how to control the thread's stack sizes.

regards,

Joseph