ATmega32A datasheet(185/352 Pages) ATMEL

185 / 352 page

185

8155B–AVR–07/09

ATmega32A

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.

When the address packet has been transmitted, the TWINT Flag in TWCR is set, and

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.

The application software should now examine the value of TWSR, to make sure that the

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.

When the data packet has been transmitted, the TWINT Flag in TWCR is set, and

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.

The application software should now examine the value of TWSR, to make sure that the

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.

Even though this example is simple, it shows the principles involved in all TWI transmissions.

These can be summarized as follows:

• When the TWI has finished an operation and expects application response, the TWINT Flag

is set. The SCL line is pulled low until TWINT is cleared.

• When the TWINT Flag is set, the user must update all TWI Registers with the value relevant

for the next TWI bus cycle. As an example, TWDR must be loaded with the value to be

transmitted in the next bus cycle.

• After all TWI Register updates and other pending application software tasks have been

completed, 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 specified by the TWCR setting.

In the following an assembly and C implementation of the example is given. Note that the code

below assumes that several definitions have been made, for example by using include-files.

ATmega32A Datasheet(PDF) 185 Page - ATMEL Corporation

ATmega32A Datasheet(HTML) 185 Page - ATMEL Corporation

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Download

Link URL