ATmega16HVB Atmel Corporation, ATmega16HVB Datasheet - Page 178

• Manufacturer Part Number: ATmega16HVB
• Manufacturer: Atmel Corporation

Specifications of ATmega16HVB

• Flash (kbytes): 16 Kbytes
• Pin Count: 44
• Max. Operating Frequency: 8 MHz
• Cpu: 8-bit AVR
• # Of Touch Channels: 8
• Hardware Qtouch Acquisition: No
• Max I/o Pins: 17
• Ext Interrupts: 15
• Usb Speed: No
• Usb Interface: No
• Spi: 1
• Twi (i2c): 1
• Graphic Lcd: No
• Video Decoder: No
• Camera Interface: No
• Adc Channels: 8
• Adc Resolution (bits): 12
• Adc Speed (ksps): 1.9
• Resistive Touch Screen: No
• Temp. Sensor: Yes
• Crypto Engine: No
• Sram (kbytes): 1
• Eeprom (bytes): 512
• Self Program Memory: YES
• Dram Memory: No
• Nand Interface: No
• Picopower: No
• Temp. Range (deg C): -40 to 85
• I/o Supply Class: 4.0 to 25
• Operating Voltage (vcc): 4.0 to 25
• Fpu: No
• Mpu / Mmu: no / no
• Timers: 2
• Output Compare Channels: 4
• Input Capture Channels: 2
• 32khz Rtc: No
• Calibrated Rc Oscillator: Yes

27.8
178
Multi-master systems and arbitration
ATmega16HVB/32HVB
Note that data is transmitted both from Master to Slave and vice versa. The Master must instruct
the slave what location it wants to read, requiring the use of the MT mode. Subsequently, data
must be read from the slave, implying the use of the MR mode. Thus, the transfer direction must
be changed. The Master must keep control of the bus during all these steps, and the steps
should be carried out as an atomic operation. If this principle is violated in a multi-master sys-
tem, another master can alter the data pointer in the EEPROM between steps 2 and 3, and the
master will read the wrong data location. Such a change in transfer direction is accomplished by
transmitting a REPEATED START between the transmission of the address byte and reception
of the data. After a REPEATED START, the master keeps ownership of the bus. The following
figure shows the flow in this transfer.
Figure 27-19. Combining Several TWI Modes to Access a Serial EEPROM.
If multiple masters are connected to the same bus, transmissions may be initiated simultane-
ously by one or more of them. The TWI standard ensures that such situations are handled in
such a way that one of the masters will be allowed to proceed with the transfer, and that no data
will be lost in the process. An example of an arbitration situation is depicted below, where two
masters are trying to transmit data to a slave receiver.
Figure 27-20. An arbitration example.
Several different scenarios may arise during arbitration, as described below:
• Two or more masters are performing identical communication with the same slave. In this case,
• Two or more masters are accessing the same slave with different data or direction bit. In this
neither the slave nor any of the masters will know about the bus contention
case, arbitration will occur, either in the READ/WRITE bit or in the data bits. The masters trying
SDA
SCL
S
S = START
Transmitted from master to slave
TRANSMITTER
SLA+W
Device 1
MASTER
A
TRANSMITTER
Device 2
MASTER
Master Transmitter
ADDRESS
Device 3
RECEIVER
SLAVE
A
Rs = REPEATED START
Rs
Transmitted from slave to master
........
SLA+R
Device n
V
BUS
A
Master Receiver
R1
DATA
R2
P = STOP
8042D–AVR–10/11
A
P