Index: ChangeLog =================================================================== RCS file: /cvsroot/avr-libc/avr-libc/ChangeLog,v retrieving revision 1.333 diff -u -u -r1.333 ChangeLog --- ChangeLog 19 Feb 2004 10:58:31 -0000 1.333 +++ ChangeLog 22 Feb 2004 20:07:21 -0000 @@ -1,3 +1,7 @@ +2004-02-22 Joerg Wunsch + + * doc/examples/twitest/twitest.dox: Fix more formatting bugs. + 2004-02-19 Joerg Wunsch * doc/examples/twitest/twitest.dox: Fix formatting bugs. Index: doc/examples/twitest/twitest.dox =================================================================== RCS file: /cvsroot/avr-libc/avr-libc/doc/examples/twitest/twitest.dox,v retrieving revision 1.2 diff -u -u -r1.2 twitest.dox --- doc/examples/twitest/twitest.dox 19 Feb 2004 10:58:31 -0000 1.2 +++ doc/examples/twitest/twitest.dox 22 Feb 2004 20:07:22 -0000 @@ -54,7 +54,7 @@ implementation can act as either master or slave at different times. Devices are addressed using a 7-bit address (coordinated by Philips) transfered as the first byte after the so-called start condition. The -LSB of that byte is R/¬W, i. e. it determines whether the request to +LSB of that byte is R/~W, i. e. it determines whether the request to the slave is to read or write data during the next cycles. (There is also an option to have devices using 10-bit addresses but that is not covered by this example.) @@ -138,7 +138,7 @@ \par Note [6] When reading the EEPROM, a first device selection must be made with -write intent (R/¬W bit set to 0 indicating a write operation) in order +write intent (R/~W bit set to 0 indicating a write operation) in order to transfer the EEPROM address to start reading from. This is called master transmitter mode. Each completion of a particular step in TWI communication is indicated by an asserted TWINT bit in @@ -171,7 +171,7 @@ Next, the device slave is going to be reselected (using a so-called repeated start condition which is meant to guarantee that the bus arbitration will remain at the current master) using the same slave -address (SLA), but this time with read intent (R/¬W bit set to 1) in +address (SLA), but this time with read intent (R/~W bit set to 1) in order to request the device slave to start transfering data from the slave to the master in the next packet. @@ -229,7 +229,7 @@ \par Note [14] -24Cxx devices can become write-protected by strapping their ¬WC pin to +24Cxx devices can become write-protected by strapping their ~WC pin to logic high. (Leaving it unconnected is explicitly allowed, and constitutes logic low level, i. e. no write protection.) In case of a write protected device, all data transfer attempts will be NACKed by