SPRUJ28E November 2021 – September 2024 AM68 , AM68A , TDA4AL-Q1 , TDA4VE-Q1 , TDA4VL-Q1
This mode is functional regardless of the ratio between the configuration interface frequency and the functional clock frequency. The recommended functional frequency range is freq(timer) < freq(interface clock)/4.
Read posted mode is used if TIMER_TSICR[2] POSTED = 0x1 or TIMER_TSICR[3] READ_MODE is set to 0. This mode uses a posted-read scheme for reading any internal timer register. The read transaction is immediately acknowledged on the configuration interface, prior to the value to be read has been resynchronized. With this method, neither the interconnect nor the device that requested the read transaction are stalled.
Read posted mode applies to TIMER_TCRR, TIMER_TCAR1, TIMER_TCAR2, TIMER_TCVR, and TIMER_TOWR, which needs resynchronization from functional to interface clock domains.
Note that in Posted mode, if the TIMER_TCRR is read immediately after wake-up and the interface clock is off during idle state, then it is possible to get an old value from just before going to idle state due to the fact the interface clock is needed for synchronization.
In order to avoid this situation, another synchronization mechanism is used for the first read operation after idle state. The TIMER_TSICR[4] READ_AFTER_IDLE bit is used to enable/disable the mechanism.
When the synchronization mechanism is disabled (READ_AFTER_IDLE bit is set to 1), first read transaction takes only 2 interface clock cycles, but the read value of TIMER_TCRR could be wrong.
When the synchronization mechanism is enabled (READ_AFTER_IDLE bit is set to 0), first read value of TIMER_TCRR is correct, but the read transaction takes more than 2 interface clock cycles.