SWCU185G January 2018 – June 2024 CC1312PSIP , CC1312R , CC1352P , CC1352R , CC2642R , CC2642R-Q1 , CC2652P , CC2652PSIP , CC2652R , CC2652RB , CC2652RSIP , CC2662R-Q1
An asynchronous event is either detected by a synchronizer or the event is used as clock to set a detection flag, which then gets synchronized. Table 20-35 lists the detection schemes used for the subscribers.
Subscribers | Detection Scheme |
---|---|
TDC Prescaler | Event as clock |
TDC High-Speed Counter | Synchronizer |
Timer 2 | Synchronizer |
ADC Interface | Event as clock |
AUX Programmable Wakeup | Event as clock |
Any event of asynchronous origin, such as AUX I/O or COMPA event, may be too short to allow proper synchronizer detection at a given clock frequency. Similarly, any Timer2 event may be too short to allow proper synchronization to a slower AUX SCE clock. In general, the pulse width of an asynchronous event must be longer than the sample clock period to allow proper synchronizer detection.
To assure that the event subscriber catches the synchronized event, either of the following must be true:
When an asynchronous event is used as clock to set a detection flag, the tolerated event pulse width is a lot less than for synchronizers.