3 ms·
‘If the flash wait states are a major problem, it may be possible to copy the interrupt handler code to RAM and run it from there. I’m assuming the internal RAM
by felixgallo 9y ago
‘If the flash wait states are a major problem, it may be possible to copy the interrupt handler code to RAM and run it from there. I’m assuming the internal RAM has zero wait states, but I might be wrong on that point.‘
- baybal2 9y agoSimpler MCUs have real hardwired SRAM access registers. On more complex systems, even SRAM access goes through some stateful scheduling circuitry. So, interrupt latency on mainstream MCUs can't be reduced much. If you want XIP with adequate latency, there is no alternative to spending money on Everspin MRAM. You will have accommodate the latency of SPI access, but that was never an issue in my practice.
- MrBuddyCasino 9y agoWhat about TCM (Tightly-Coupled Memory) on ARM?
- baybal2 9y agoIf you have it, then use it. Its purpose is exactly to hold latency sensitive code, like interrupt handlers. The challenge is of course is to fit your code into it as it is usually small.
- monocasa 9y agoThere's also parallel versions of MRAM that you can hookup just like SRAM.
- baybal2 9y agoIndeed, just the amount of mainstream MCUs with external memory bus connection is smaller with each year.
- chillingeffect 9y agoBwah hah, that reminds of me the ADSP-21xx series... They had a second register file for the interrupts. No pushing or popping. Interrupts happens, bam, all of your accesses are exactly where you left them! And when you're done, return to main thread and all registers are exactly where you left them on the next clock cycle!!!