{"id":4946,"date":"2021-01-23T04:57:06","date_gmt":"2021-01-23T04:57:06","guid":{"rendered":"http:\/\/fastbitlab.com\/?p=4946"},"modified":"2022-11-23T10:36:36","modified_gmt":"2022-11-23T05:06:36","slug":"stm32-i2c-lecture-57-i2c-slave-support-in-driver","status":"publish","type":"post","link":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-57-i2c-slave-support-in-driver\/","title":{"rendered":"STM32 I2C Lecture 57: I2C slave support in driver"},"content":{"rendered":"
\n
\n
\n
\n

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

\n

I2C slave support in driver<\/span><\/h1>\n
\n
\n

 <\/p>\n

<\/div>\n

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

\n
\n<\/div>\n

Now let\u2019s implement all the callback events for slave transmitter and slave receiver.<\/span><\/p>\n

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

1. Go to the event IRQ handling section of the driver file shown in Figure 1.<\/span><\/p>\n

\"I2C
Figure 1. I2C_EV_IRQHandling() API.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

2. In the TXE event, check for the device mode. If the device is master, then the code in Figure 2 will get executed.<\/span><\/span><\/p>\n

\"I2C
Figure 2. Code to be executed when the device mode is master.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

The code to be executed when the device mode is a slave is implemented as follows:<\/span><\/p>\n