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

handling interrupts when running outside of application

Hello,
I am facing a problem: my product is going to have 3 parts. a bootloader, firmware to handle most interrupts and application where RTX is running. how here is the catch: when an interrupt is handled in firmware, the return address is in the application which has a separate region of internal RAM. so, when an interrupt service routine in firmware tries to push data into the IRQ stack, a data abort occurs as R13 points into RAM that not in the realm of the firmware!
If I could only use a shared stack, or set the R13 based on the interrupt source without destroying the content of my task - my problem would be solved.
Do you have concrete ideas?

0