72
32099DS–06/2010
AT32UC3L016/32/64
Before going to sleep modes where RCSYS is stopped, make sure the division factor
between the CPU/HSB and PBx frequencies is less than or equal to 4.
2.
Disabling POR33 may generate spurious resest
Depending on operating conditions, POR33 may generate a spurious reset in one of the fol-
lowing cases:
- When POR33 is disabled from the user interface.
- When SM33 supply monitor is enabled.
- When entering Shutdown mode while debugging the chip using JTAG or aWire interface.
In the listed cases, writing a one to the bit VREGCR.POR33MASK in the System Control
Interface (SCIF) to mask the POR33 reset will be ineffective.
Fix/Workaround
- Do not disable POR33 using the user interface.
- Do not use the SM33 supply monitor.
- Do not enter Shutdown mode if a debugger is connected to the chip.
3.
CONFIG register reads 0x4F
The CONFIG register reads 0x4F instead of 0x43.
Fix/Workaround
None.
4.
PB writes via debugger in sleep modes are blocked during sleepwalking
During sleepwalking, PB writes performed by a debugger will be discarded by all PB mod-
ules except the module that is requesting the clock.
Fix/Workaround
None.
5.
VERSION register reads 0x400
The VERSION register reads 0x400 instead of 0x411.
Fix/Workaround
None.
6.
WCAUSE register should not be used
The WCAUSE register should not be used.
Fix/Workaround
None.
7.
Static mode cannot be entered if the WDT is using OSC32K
If the WDT is using OSC32K as clock source and the user tries to enter Static mode, the
Deepstop mode will be entered instead.
Fix/Workaround
None.
8.
It is not possible to mask the request clock requests
It is not possible to mask the request clock requests using PPCR.
Fix/Workaround
None.
9.
Clock failure detector (CFD) does not work
The clock failure detector does not work.
Fix/Workaround
None.
10. Instability when exiting sleep walking