Datasheet

SAM9G20
DS60001516A-page 778  2017 Microchip Technology Inc.
44.1.7.4 SSC: Periodic Transmission Limitations in Master Mode
If Last Significant Bit is sent first (MSBF = 0) the first TAG during the frame synchro is not sent.
Problem Fix/Workaround
None.
44.1.8 Shutdown Controller (SHDWC)
44.1.8.1 SHDWC: SHDN Signal may be Driven to Low Level Voltage During Device Power-on
If only VDDBU is powered during boot sequence (No VDDCORE), the SHDN signal may be driven to low level voltage after a delay.This
delay is linked to the startup time of the slow clock selected by OSCSEL signal.
If SHDN pin is connected to the Enable pin (EN) of the VDDCORE regulator, VDDCORE establishment does not occur and the system
does not start.
Problem Fix/Workaround
1. VDDCORE must be established within the delay corresponding to the startup time of the slow clock selected by OSCSEL.
2. Add a glue logic to latch the rising edge of the SHDN signal. The reset of the latch output (EN_REG) can be connected to a PIO
and used to enter the shutdown mode.
44.1.9 Static Memory Controller (SMC)
44.1.9.1 SMC: Chip Select Parameters Modification
The user must not change the configuration parameters of an SMC Chip Select (Setup, Pulse, Cycle, Mode) if accesses are performed
on this CS during the modification.
For example, the modification of the Chip Select 0 (CS0) parameters, while fetching the code from a memory connected on this CS0, may
lead to unpredictable behavior.
Problem Fix/Workaround
The code used to modify the parameters of an SMC Chip Select can be executed from the internal RAM or from a memory connected to
another Chip Select
44.1.10 System Controller (SYSC)
44.1.10.1 SYSC: Possible Event Loss when reading RTT_SR
If an event (RTTINC or ALMS) occurs within the same slow clock cycle as when the RTT_SR is read, the corresponding bit might be
cleared. This can lead to the loss of this event.
Problem Fix/Workaround
The software must handle an RTT event as an interrupt and should not poll RTT_SR.
44.1.11 Two-wire Interface (TWI)
44.1.11.1 TWI: RXRDY Flag is not reset by a SOFTWARE Reset
The RXRDY Flag is not reset when a Software reset is performed.
Problem Fix/Workaround
After a Software Reset, the Register TWI_RHR must be read.
44.1.12 UHP
44.1.12.1 UHP: Non-ISO IN Transfers
Conditions:
Consider the following sequence:
1. The Host controller issues an IN token.
2. The Device provides the IN data in a short packet.
3. The Host controller writes the received data to the system memory.
4. The Host controller is now supposed to carry out two Write transactions (TD status write and TD retirement write) to the system
memory in order to complete the status update.