XC2700 Datasheet, PDF (23/62 Pages) Infineon Technologies AG – 16/32-Bit Single-Chip Microcontroller

XC2700 Derivatives
XC2000 Family / Alpha Line
Detailed Errata Description
• when T3 is counting down, FFFF_H or FFFE_H may be read from T3 directly after an
underflow, although the reload value in T2/T4 is lower (FFFE_H may be read in
particular if BPS1 = 01_B and T3I = 000_B).
Note: All timings derived from T3 in this configuration (e.g. distance between interrupt
requests, PWM waveform on T3OUT, etc.) are accurate except for the specific
case described under 2.) below.
Workaround:
• When T3 counts up, and value_x < reload value is read from T3, value_x should be
replaced with the reload value for further calculations.
• When T3 counts down, and value_x > reload value is read from T3, value_x should
be replaced with the reload value for further calculations.
Alternatively, if the intention is to identify the overflow/underflow of T3, the T3 interrupt
request may be used.
2.) Reload of T3 from T2 with setting BPS1 = 01_B and T3I = 000_B
When T2 is used to reload T3 in the configuration with BPS1 = 01_B and T3I = 000_B (i.e.
fastest configuration/highest resolution of T3), the reload of T3 is performed with a delay
of one basic clock cycle.
Workaround 1:
To compensate the delay and achieve correct timing,
• increment the reload value in T2 by 1 when T3 is configured to count up,
• decrement the reload value in T2 by 1 when T3 is configured to count down.
Workaround 2:
Alternatively, use T4 instead of T2 as reload register for T3. In this configuration the
reload of T3 is not delayed, i.e. the effect described above does not occur with T4.
GSC_X.001 Clearing of Request Triggers by the GSC
After a request from sources with priority 5..10 (ESR0...GPT12E, see table in Chapter
“Global State Controller (GSC)” of the current User’s Manual), the following problem will
occur:
A trigger for a command request (Wake-up, Clock-off, Suspend Mode) that is enabled in
register GSCEN remains pending in the GSC after the arbitration has been finished and
the command has been requested. As a consequence, further request triggers with the
same or a lower priority will be ignored (14 = lowest priority).
Errata Sheet
23
V1.7, 2014-10