Two-Wire Interface (TWI) driver — Configuration and implementation details of TWI (I²C®) driver
The AT91RM9200 processor HAL contains a driver for the Two-Wire Interface
(TWI) controller on the AT91RM9200. This type of bus is also known as
I²C®. The API
for this may be found within the
I²C®/TWI driver configuration
The I²C® driver uses
the AT91RM9200's internal Two-Wire Interface (TWI)
support. This is controlled within the AT91RM9200 processor HAL
CYGPKG_HAL_AT91RM9200_TWI CDL component controls whether the
TWI driver is enabled. Within that component, there are two sub-options:
CYGNUM_HAL_AT91RM9200_TWI_CLOCKsets the speed of the TWI bus clock in Hz. This is usually 100kHz, but can be set up to 400kHz if the devices on the bus support this speed, also known as fast mode. However other values below 400kHz can also be chosen, subject to the accuracy of the clock waveform generation parameters.
The second option within the
CYGNUM_HAL_AT91RM9200_TWI_CKDIV. This is the clock divider used when configuring the TWI_CWGR register. Consult the AT91RM9200 datasheet description of the TWI_CWGR register for the formula used to determine the clock frequency. Increasing the divider will decrease the accuracy in practice of the generated I²C bus clock compared to
CYGNUM_HAL_AT91RM9200_TWI_CLOCK. But the divider must also be sufficiently low that the relevant factors do not overflow valid values for CHDIV/CLDIV in TWI_CWGR. Note that when the AT91RM9200 is using a 60MHz MCK, then for 100kHz operation, a value for this option of 1 is most appropriate. For 400kHz, a value for this option of 0 is most appropriate. The default value of this CDL is an appropriate value for CKDIV assuming a 60MHz MCK and a TWI clock between 29kHz and 400kHz.
To be specific, the CLDIV/CHDIV fields of the TWI_CWGR are considered equal. The value of, for example, CLDIV, can be expressed as:
To use the I²C/TWI driver, the generic
I²C driver package
must be used. Documentation for its API may be found elsewhere.
This driver only operates in interrupt mode. It does not operate in polled mode, and thus does not operate when interrupts are disabled. It cannot therefore be used in an initialization context, before the eCos kernel thread scheduler starts. And it cannot be used with RedBoot.
Due to the characteristics of the AT91RM9200's operation, it is not possible to provide support for repeated starts with the I²C package API. Similarly indicating a NACK when performing a receive is equivalent to also sending a STOP.
A test application for use with the
I²C/SPI Activity Board is provided within the
tests subdirectory of the
CYGPKG_HAL_AT91RM9200 package. This test communicates with
the I²C EEPROM on the board to perform read and
write operations using I²C. This test is not
built by default. It may be built by enabling the configuration option
CYGBLD_HAL_ARM_ARM9_AT91RM9200_TEST_TWI_AT24C02A within the
AT91RM9200 processor HAL.
|2019-06-13||eCosPro Non-Commercial Public License|