
QADC
REFERENCE MANUAL
DIGITAL CONTROL
MOTOROLA
7-23
TOR1 — Queue 1 Trigger Overrun
TOR1 indicates that an unexpected trigger event has occurred for queue 1. TOR1 can
be set only while queue 1 is in the active state.
A trigger event generated by a transition on the external trigger pin or by the periodic/
interval timer may be recorded as a trigger overrun. TOR1 can only occur when using
an external trigger mode. TOR1 cannot occur when the software initiated single-scan
mode and the software initiated continuous-scan mode are selected.
TOR1 occurs when a trigger event is received while a queue is executing and before
the scan has completed or paused. TOR1 can also occur when a trigger event has oc-
curred on a queue, but execution has not yet begun. TOR1 has no effect on the queue
execution.
After a trigger event has occurred for queue 1, and before the scan has completed or
paused, additional queue 1 trigger events are not retained. Such trigger events are
considered unexpected, and the QADC sets the TOR1 error status bit. An unexpected
trigger event may be a system overrun situation, indicating a system loading mis-
match. The software acknowledges that it has detected a trigger overrun being set by
writing a zero to the trigger overrun, after the bit was read as a one. Once set, only
software or reset can clear TOR1.
0 = No unexpected queue 1 trigger events have occurred.
1 = At least one unexpected queue 1 trigger event has occurred.
TOR2 — Queue 2 Trigger Overrun
TOR2 indicates that an unexpected trigger event has occurred for queue 2. TOR2 can
be set when queue 2 is in the active, suspended, and trigger pending states.
The TOR2 trigger overrun can only occur when using an external trigger mode or a
periodic/interval timer mode. Trigger overruns cannot occur when the software initiat-
ed single-scan mode and the software initiated continuous-scan mode are selected.
TOR2 occurs when a trigger event is received while a queue is executing and before
the scan has completed or paused. TOR2 also occurs when a trigger event has oc-
curred on a queue, but execution has not yet begun. TOR2 has no effect on the queue
execution. A trigger event that causes a trigger overrun is not retained since it is con-
sidered unexpected.
After a trigger event has occurred for queue 2, and before the scan has completed or
paused, additional queue 2 trigger events are not retained, and are considered unex-
pected. Also, when a queue 2 trigger event is pending, but queue 1 is active, additional
queue 2 trigger events are considered unexpected. In both cases, the QADC sets the
TOR2 error status bit.
An unexpected trigger event may be a system overrun situation, indicating a system
loading mismatch. The software acknowledges that it has detected a trigger overrun
being set by writing a zero to the trigger overrun, after the bit was read as a one. Once
set, only software or reset can clear TOR2.
0 = No unexpected queue 2 trigger events have occurred.
1 = At least one unexpected queue 2 trigger event has occurred.
F
Freescale Semiconductor, Inc.
For More Information On This Product,
Go to: www.freescale.com
n
.