ATSAM3U-EK Atmel, ATSAM3U-EK Datasheet - Page 637

• Manufacturer Part Number: ATSAM3U-EK
• Description: KIT EVAL FOR AT91SAM3U CORTEX
• Manufacturer: Atmel
• Type: MCUr

Specifications of ATSAM3U-EK

• Contents: Board
• Processor To Be Evaluated: SAM3U
• Data Bus Width: 32 bit
• Interface Type: RS-232, USB
• Operating Supply Voltage: 3 V
• Silicon Manufacturer: Atmel
• Core Architecture: ARM
• Core Sub-architecture: Cortex - M3
• Silicon Core Number: SAM3U4E
• Silicon Family Name: SAM3U
• Kit Contents: Board CD Docs
• Rohs Compliant: Yes
• For Use With/related Products: AT91SAM3U
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

33.8
33.8.1
33.8.2
33.8.2.1
33.8.2.2
6430D–ATARM–25-Mar-11
Multi-master Mode
Definition
Different Multi-master Modes
TWI as Master Only
TWI as Master or Slave
More than one master may handle the bus at the same time without data corruption by using
arbitration.
Arbitration starts as soon as two or more masters place information on the bus at the same time,
and stops (arbitration is lost) for the master that intends to send a logical one while the other
master sends a logical zero.
As soon as arbitration is lost by a master, it stops sending data and listens to the bus in order to
detect a stop. When the stop is detected, the master who has lost arbitration may put its data on
the bus by respecting arbitration.
Arbitration is illustrated in
Two multi-master modes may be distinguished:
Note:
In this mode, TWI is considered as a Master only (MSEN is always at one) and must be driven
like a Master with the ARBLST (ARBitration Lost) flag in addition.
If arbitration is lost (ARBLST = 1), the programmer must reinitiate the data transfer.
If the user starts a transfer (ex.: DADR + START + W + Write in THR) and if the bus is busy, the
TWI automatically waits for a STOP condition on the bus to initiate the transfer (see
21 on page
Note:
The automatic reversal from Master to Slave is not supported in case of a lost arbitration.
Then, in the case where TWI may be either a Master or a Slave, the programmer must manage
the pseudo Multi-master mode described in the steps below.
1. TWI is considered as a Master only and will never be addressed.
2. TWI may be either a Master or a Slave and may be addressed.
1. Program TWI in Slave mode (SADR + MSDIS + SVEN) and perform Slave Access (if
2. If TWI has to be set in Master mode, wait until TXCOMP flag is at 1.
3. Program Master mode (DADR + SVDIS + MSEN) and start the transfer (ex: START +
4. As soon as the Master mode is enabled, TWI scans the bus in order to detect if it is
5. As soon as the transfer is initiated and until a STOP condition is sent, the arbitration
6. If the arbitration is lost (ARBLST is set to 1), the user must program the TWI in Slave
7. If TWI has to be set in Slave mode, wait until TXCOMP flag is at 1 and then program the
TWI is addressed).
Write in THR).
busy or free. When the bus is considered as free, TWI initiates the transfer.
becomes relevant and the user must monitor the ARBLST flag.
mode in the case where the Master that won the arbitration wanted to access the TWI.
Slave mode.
In both Multi-master modes arbitration is supported.
The state of the bus (busy or free) is not indicated in the user interface.
638).
Figure 33-22 on page
638.
SAM3U Series
Figure 33-
637