{"id":4520,"date":"2020-12-28T04:07:12","date_gmt":"2020-12-28T04:07:12","guid":{"rendered":"http:\/\/fastbitlab.com\/?p=4520"},"modified":"2023-09-07T16:14:41","modified_gmt":"2023-09-07T10:44:41","slug":"i2c-handle-structure-modification","status":"publish","type":"post","link":"https:\/\/fastbitlab.com\/blog\/i2c-handle-structure-modification\/","title":{"rendered":"STM32 I2C Lecture 40: I2C handle structure modification"},"content":{"rendered":"
\n
\n
\n
\n

 <\/p>\n<\/div>\n

\n

I2C handle structure modification<\/span><\/h1>\n
\n
\n
\n

 <\/p>\n

<\/div>\n

 <\/p>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n<\/div>\n

In this article, let\u2019s develop master send data API with interrupt and master receive data API with interrupt. The master send data, and the master receive data APIs that we develop now are the interrupt flavors or non-blocking flavors of APIs developed in earlier parts.<\/span><\/p>\n

Similar to what we have done in the SPI section, here also modify the handle structure (Figure 1) to store various data like other transmission buffer addresses, received buffer addresses, length information, the slave address information, etc.<\/span><\/p>\n

\"I2C
Figure 1. Modifying handle structure to store placeholder variables.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

The handle structure must be modified according to the information in Figure 1. <\/span><\/p>\n

Remember that, unlike SPI, the I2C is half-duplex communication. Therefore, in I2C, only one variable is enough to store the transmission and reception state, and it is combinely called TxRxState, as shown in Figure 1. Because in I2C, you cannot receive data while transmitting, and even it is not possible to transmit the data while receiving. The application states may be I2C_READY, I2C_BUSY_IN_RX, or I2C_BUSY_IN_TX.<\/span><\/p>\n

Look at Figure 1,<\/span><\/p>\n