SPRUGR9H November 2010 – April 2015 66AK2E05 , 66AK2H06 , 66AK2H12 , 66AK2H14 , 66AK2L06 , AM5K2E02 , AM5K2E04 , SM320C6678-HIREL , TMS320C6652 , TMS320C6654 , TMS320C6655 , TMS320C6657 , TMS320C6670 , TMS320C6671 , TMS320C6672 , TMS320C6674 , TMS320C6678
Each accumulator channel will always trigger an interrupt when all the entries in the current buffer page are filled. It is also possible to trigger interrupts more quickly by configuring the interrupt pacing mode. The interrupt pacing mode allows for interrupts to be generated on a partially filled page, based on configurable packet activity and a configurable amount of elapsed time. Note that the pacing is per channel, and not per interrupt. So, if two channels are using the same host interrupt, then the host interrupt can be triggered as each channel independently requires.
The available interrupt pacing modes are based on one of the following events:
The above event setting determines when the interrupt counter will be loaded and begin its countdown. An interrupt will trigger only when both the timing condition is met and there are packets available to forward to the host. If the timer expires with no packet activity, then the next incoming packet will trigger an immediate interrupt.
The time delay from the configured event is programmable, using the global timer value multiplied by. A timer setting of 0 seconds is useful in cases where the user wishes to trigger interrupts without delay based on any packet activity. Note that a delay of 0 seconds will always trigger an immediate interrupt on the first received packet no matter which of the three configurable pacing events are used.