The fastest you can respond to a high-priority interrupt is 5-6 instruction cycles (assuming there's a GOTO at the vector location), so at 64MHz that's 375ns before your ISR code begins to execute.
...
No, I don't think it could.
It will tell you the size of the code (ie how much FLASH it occupies). It doesn't tell you anything about which system variables the code uses.
Hi,
OK, the simple band-aid would be to up the frequency but since you're running at 64MHz already that won't work. You said you re-wrote one of the handler in ASM but did you also change the...
I'm currently running this Pic at 64mhz. No Longs are being used so that's not an issue here I would think. I have multiple interrupts being handled thru...
It depends on a couple of things. The device family (18 series in your case), if LONGs are being used, if your program has resulted in PBP using any of its T-variables, if you're using a PBP handler...
My question is: Does anyone know the minimum time it takes for the interrupt handler (DT_Ints) to kick in and start processing the interrupt? I currently have one interrupt on...
Menu
Re: DT_ints handling time.
The fastest you can respond to a high-priority interrupt is 5-6 instruction cycles (assuming there's a GOTO at the vector location), so at 64MHz that's 375ns before your ISR code begins to execute.
tumbleweed Today, 15:22...