![](http://datasheet.mmic.net.cn/100000/IF180C52TXXX-20R_datasheet_3493957/IF180C52TXXX-20R_833.png)
833
32099I–01/2012
AT32UC3L016/32/64
Fix/Workaround
None.
5.
MGCFG2.ACCTRL bit is stuck at zero
The ACCTRL bit in the MGCFG2 register is stuck at zero and cannot be written to one. The
analog comparators will be constantly enabled.
Fix/Workaround
None.
6.
CAT asynchronous wake will be delayed by one AST event period
If the CAT detects a condition the should asynchronously wake the device in static mode,
the asynchronous wake will not occur until the next AST event. For example, if the AST is
generating events to the CAT every 50ms, and the CAT detects a touch at t=9200ms, the
asynchronous wake will occur at t=9250ms.
Fix/Workaround
None.
7.
VERSION register reads 0x100
The VERSION register reads 0x100 instead of 0x200.
Fix/Workaround
None.
8.
CAT module does not terminate QTouch burst on detect
The CAT module does not terminate a QTouch burst when the detection voltage is
reached on the sense capacitor. This can cause the sense capacitor to be charged more
than necessary. Depending on the dielectric absorption characteristics of the capacitor, this
can lead to unstable measurements.
Fix/Workaround
Use the minimum possible value for the MAX field in the ATCFG1, TG0CFG1, and
TG1CFG1 registers.
9.
Autonomous CAT acquisition must be longer than AST source clock period
When using the AST to trigger CAT autonomous touch acquisition in sleep modes where the
CAT bus clock is turned off, the CAT will start several acquisitions if the period of the AST
source clock is larger than one CAT acquisition. One AST clock period after the AST trigger,
the CAT clock will automatically stop and the CAT acquisition can be stopped prematurely,
ruining the result.
Fix/Workaround
Always ensure that the ATCFG1.max field is set so that the duration of the autonomous
touch acquisition is greater than one clock period of the AST source clock.
35.4.20
GLOC
1.
GLOC is non-functional
Glue Logic Controller (GLOC) is non-functional.
Fix/Workaround
None.
35.4.21
aWire
1.
SAB multiaccess reads are not working
Reading more than one word, halfword, or byte in one command is not working correctly.
Fix/Workaround
Split the access into several single word, halfword, or byte accesses.