This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Interrupt Latency of AM3517/05 running WEC7

What is the interrupt latency timing, starting from when  the interrupt is generated, to the ISR execution while running Windows Embedded Compact 7?

Background..
In normal operation, ARM processors will take an interrupt exception when the currently executing instruction completes. This could be a load-multiple operation which could cause page table walks, cache linefills and write-back of  dirty data, each potentially taking a number of cycles to complete. Some processors provide support for a low-latency interrupt mode. When this is selected, the processor can abandon multiple loads or stores to Normal memory upon receiving an interrupt. After processing the interrupt it returns to the original instruction and re-executes it from the start. This can give significantly lower interrupt latency, at the cost of reduced overall processor performance.

  • This is the processor latency and has little to do with OS i.e it will most likely be the same in WinCE or Linux or any other OS. As you correctly pointed out, it will really depend upon the operation that got interrupted - worst case scenario you can probably calculate by hand. In reality, what matters is the latency b/w actual interrupt and  its handling in IST - on WinCE you can measure this for your application using iltiming tool. The numbers you get will vary but over period of time you can reasonably numbers for max, min and average.

    thanks

    Atul