ATmega128A Atmel Corporation, ATmega128A Datasheet - Page 210

no-image

ATmega128A

Manufacturer Part Number
ATmega128A
Description
Manufacturer
Atmel Corporation
Datasheets

Specifications of ATmega128A

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

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
ATmega128A XC6SLXFGG484CTV BCM7366ZBK W2SG0008I-T
Manufacturer:
XILINX
0
Part Number:
ATmega128A-16AU
Manufacturer:
ATMEL
Quantity:
6
Part Number:
ATmega128A-16AU
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
Company:
Part Number:
ATmega128A-16AU
Quantity:
100
Part Number:
ATmega128A-16MU
Quantity:
10
Part Number:
ATmega128A-AN
Manufacturer:
Atmel
Quantity:
10 000
Part Number:
ATmega128A-ANR
Manufacturer:
Atmel
Quantity:
10 000
Part Number:
ATmega128A-AU
Manufacturer:
ATMEL
Quantity:
9 000
Part Number:
ATmega128A-AU
Manufacturer:
ATMEL
Quantity:
3 480
Part Number:
ATmega128A-AU
Manufacturer:
ATMEL
Quantity:
3 512
Part Number:
ATmega128A-AU
Manufacturer:
Atmel
Quantity:
10 000
Part Number:
ATmega128A-AU
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
Company:
Part Number:
ATmega128A-AU
Quantity:
6 944
Part Number:
ATmega128A-AUR
Manufacturer:
ATMEL
Quantity:
3 000
Part Number:
ATmega128A-AUR
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
8151H–AVR–02/11
Even though this example is simple, it shows the principles involved in all TWI transmissions.
These can be summarized as follows:
After all TWI Register updates and other pending application software tasks have been com-
pleted, TWCR is written. When writing TWCR, the TWINT bit should be set. Writing a one to
TWINT clears the flag. The TWI will then commence executing whatever operation was speci-
fied by the TWCR setting.
4. When the address packet has been transmitted, the TWINT flag in TWCR is set, and
5. The application software should now examine the value of TWSR, to make sure that the
6. When the data packet has been transmitted, the TWINT flag in TWCR is set, and
7. The application software should now examine the value of TWSR, to make sure that the
• When the TWI has finished an operation and expects application response, the TWINT flag is
• When the TWINT flag is set, the user must update all TWI Registers with the value relevant
set. The SCL line is pulled low until TWINT is cleared.
for the next TWI bus cycle. As an example, TWDR must be loaded with the value to be
transmitted in the next bus cycle.
cation software might take some special action, like calling an error routine. Assuming
that the status code is as expected, the application must load SLA+W into TWDR.
Remember that TWDR is used both for address and data. After TWDR has been
loaded with the desired SLA+W, a specific value must be written to TWCR, instructing
the TWI hardware to transmit the SLA+W present in TWDR. Which value to write is
described later on. However, it is important that the TWINT bit is set in the value written.
Writing a one to TWINT clears the flag. The TWI will not start any operation as long as
the TWINT bit in TWCR is set. Immediately after the application has cleared TWINT,
the TWI will initiate transmission of the address packet.
TWSR is updated with a status code indicating that the address packet has success-
fully been sent. The status code will also reflect whether a slave acknowledged the
packet or not.
address packet was successfully transmitted, and that the value of the ACK bit was as
expected. If TWSR indicates otherwise, the application software might take some spe-
cial action, like calling an error routine. Assuming that the status code is as expected,
the application must load a data packet into TWDR. Subsequently, a specific value
must be written to TWCR, instructing the TWI hardware to transmit the data packet
present in TWDR. Which value to write is described later on. However, it is important
that the TWINT bit is set in the value written. Writing a one to TWINT clears the flag.
The TWI will not start any operation as long as the TWINT bit in TWCR is set. Immedi-
ately after the application has cleared TWINT, the TWI will initiate transmission of the
data packet.
TWSR is updated with a status code indicating that the data packet has successfully
been sent. The status code will also reflect whether a slave acknowledged the packet or
not.
data packet was successfully transmitted, and that the value of the ACK bit was as
expected. If TWSR indicates otherwise, the application software might take some spe-
cial action, like calling an error routine. Assuming that the status code is as expected,
the application must write a specific value to TWCR, instructing the TWI hardware to
transmit a STOP condition. Which value to write is described later on. However, it is
important that the TWINT bit is set in the value written. Writing a one to TWINT clears
the flag. The TWI will not start any operation as long as the TWINT bit in TWCR is set.
Immediately after the application has cleared TWINT, the TWI will initiate transmission
of the STOP condition. Note that TWINT is NOT set after a STOP condition has been
sent.
ATmega128A
210

Related parts for ATmega128A