ATmega128 datasheet(209/386 Pages) ATMEL

209 / 386 page

209

2467S–AVR–07/09

ATmega128

abstract, a more detailed explanation follows later in this section. A simple code example imple-

menting the desired behavior is also presented.

Figure 95. Interfacing the Application to the TWI in a Typical Transmission

The first step in a TWI transmission is to transmit a START condition. This is done by

writing a specific value into TWCR, instructing the TWI hardware to transmit a START

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 START condition.

When the START condition has been transmitted, the TWINT flag in TWCR is set, and

TWSR is updated with a status code indicating that the START condition has success-

fully been sent.

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

START condition was successfully transmitted. If TWSR indicates otherwise, the applica-

tion 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.

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 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

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 special

action, like calling an error routine. Assuming that the status code is as expected, the

START

SLA+W

Data

STOP

1. Application

writes to TWCR

to initiate

transmission of

START

2. TWINT set.

Status code indicates

START condition sent

4. TWINT set.

Status code indicates

SLA+W sendt, ACK

received

6. TWINT set.

Status code indicates

data sent, ACK received

3. Check TWSR to see if START

was sent. Application loads

SLA+W into TWDR, and loads

appropriate control signals into

TWCR, making sure that TWINT

is written to one, and TWSTA is

written to zero.

5. Check TWSR to see if SLA+W

was sent and ACK received.

Application loads data into TWDR,

and loads appropriate control signals

into TWCR, making sure that TWINT

is written to one.

7. Check TWSR to see if data

was sent and ACK received.

Application loads appropriate

control signals to send STOP

into TWCR, making sure that

TWINT is written to one

TWI bus

Indicates

TWINT set

TWI

Hardware

Action

ATmega128 датащи(PDF) 209 Page - ATMEL Corporation

ATmega128 датащи(HTML) 209 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

датащи скачать

ссылки URL