{"id":4908,"date":"2021-01-13T08:42:46","date_gmt":"2021-01-13T08:42:46","guid":{"rendered":"http:\/\/fastbitlab.com\/?p=4908"},"modified":"2022-11-23T10:22:03","modified_gmt":"2022-11-23T04:52:03","slug":"i2c-slave-programming-discussion","status":"publish","type":"post","link":"https:\/\/fastbitlab.com\/blog\/i2c-slave-programming-discussion\/","title":{"rendered":"STM32 I2C Lecture 55: I2C slave programming discussion"},"content":{"rendered":"
\n
\n
\n
\n

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

\n
\n

I2C slave programming discussion<\/span><\/h1>\n
\n
\n
\n

 <\/p>\n

<\/div>\n

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

In this article, let\u2019s understand how to program for I2C slave. <\/span><\/p>\n

Now let\u2019s change the mode (Figure 1). For example, consider the Arduino board as master and STM32 as a slave device.<\/span><\/p>\n

\"I2C
Figure 1. Master slave communication.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

Differences between the I2C master and the I2C slave (Figure 2):<\/b><\/span><\/p>\n

\"I2C
Figure 2. Difference between I2C master and slave.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

\"\"<\/p>\n

<\/div>\n

 <\/p>\n

For example, when the I2C master executes a read transaction, that is nothing but a request for data. It indicates that the master wants to read some data from the slave. When an I2C master executes or initiates a write transaction, that is nothing but a receive data for the slave. <\/span><\/p>\n

The slave has to serve only two events, one is request for data, which is nothing but a read transaction from the master and another event is receive data, which happens whenever an I2C master wants to write some data to the slave. Therefore, in the I2C slave code, you have to receive only two events. They are – request for data and receive data, and then the action is taken according to the event received.<\/span><\/p>\n

    \n
  1. You have to create a send data API to request data from the master. <\/span><\/li>\n
  2. You have to create a receive data API to receive the data from the master.<\/span><\/li>\n<\/ol>\n

    In slave mode, the I2C driver (STM32 I2C driver) will send a request for data and receive data events to the slave application, as shown in Figure 3. Once the application receives a request for data, it will send the data and then receives the data from the master.<\/span><\/p>\n

    \"I2C
    Figure 3. Events received by the slave.<\/span><\/figcaption><\/figure>\n

     <\/p>\n

    Now let\u2019s create the APIs for a request for data and receive data events. <\/span><\/p>\n

    Steps:<\/b><\/span><\/p>\n

    1. Go to the driver.h file and create a prototype of APIs for request for data and receive data events, as shown in Figure 4.<\/span><\/p>\n

    \"I2C
    Figure 4. Prototype of the APIs.<\/span><\/figcaption><\/figure>\n

     <\/p>\n

    2. Whenever the request is received, then only the slave will send the data. The length and other information passed as the arguments of the API are not necessary since the slave sends the data byte by byte. Therefore, remove all the things passed as an argument of I2C_SlaveSendData() API shown in Figure 4.<\/span><\/p>\n

    The I2C_SlaveSendData() API will accept only two parameters (Figure 5), one is the I2C RegDef pointer, and another is the value or data to be sent.<\/span><\/p>\n

    \"I2C
    Figure 5. Prototype of I2C_SlaveSendData() API.<\/span><\/figcaption><\/figure>\n

     <\/p>\n

    3. Whenever a receive data event is received from the master, a slave is going to receive the data. Therefore, you don\u2019t need pass length and other information only pass I2C RegDef pointer as a parameter of I2C_SlaveReceiveData() API, as shown in Figure 6. <\/span><\/span><\/p>\n

    Since I2C_SlaveReceiveData() API returns the data received from the master, the return type will be uint8_t.<\/span><\/span><\/p>\n

    \"I2C
    Figure 6. Prototype of I2C_SlaveReceiveData() API.<\/span><\/figcaption><\/figure>\n

     <\/p>\n

    4. Implement the I2C_SlaveSendData() and I2C_SlaveReceiveData() APIs in the driver.c file before I2C event IRQ handling.<\/span><\/p>\n

    Steps of implementation:<\/strong><\/span><\/p>\n