I2C_OneBoard_Communication_IT_Init Example Description

How to handle the reception of one data byte from an I2C slave device by an I2C master device. Both devices operate in interrupt mode. The peripheral is initialized with LL initialization function to demonstrate LL init usage.

This example guides you through the different configuration steps by mean of LL API to configure GPIO and I2C peripherals using only one NUCLEO-C071RB.

The user can disable internal pull-up by opening ioc file.

For that, user can follow the procedure :

  1. Double click on the I2C_OneBoard_Communication_IT_Init.ioc file
  2. When CUBEMX tool is opened, select System Core category
  3. Then in the configuration of GPIO/I2C1, change Pull-up to No pull-up and no pull-down for the both pins
  4. Same action in the configuration of GPIO/I2C2, change Pull-up to No pull-up and no pull-down for the both pins
  5. Last step, generate new code thanks to button “GENERATE CODE”

The example is updated with no pull on each pin used for I2C communication.

I2C1 Peripheral is configured in Slave mode with EXTI (Clock 400Khz, Own address 7-bit enabled). I2C2 Peripheral is configured in Master mode with EXTI (Clock 400Khz). GPIO associated to User push-button is linked with EXTI.

LED1 blinks quickly to wait for user-button press.

Example execution:

Press the User push-button to initiate a read request by Master.

This action will generate an I2C start condition with the Slave address and a read bit condition. When address Slave match code is received on I2C1, an ADDR interrupt occurs. I2C1 IRQ Handler routine is then checking Address Match Code and direction Read. This will allow Slave to enter in transmitter mode and then send a byte when TXIS interrupt occurs. When byte is received on I2C2, an RXNE interrupt occurs. When RXDR register is read, Master auto-generate a NACK and STOP condition to inform the Slave that the transfer is finished. The NACK condition generate a NACK interrupt in Slave side treated in the I2C1 IRQ handler routine by a clear of NACK flag. The STOP condition generate a STOP interrupt in both side (Slave and Master). I2C1 and I2C2 IRQ handler routine are then clearing the STOP flag in both side.

LED1 is On if data is well received.

In case of errors, LED1 is blinking slowly (1s).

Keywords

Connectivity, Communication, I2C, Master, Slave, Transmission, Reception, Fast mode

Directory contents

- I2C/I2C_OneBoard_Communication_IT_Init/Inc/stm32c0xx_it.h          Interrupt handlers header file
- I2C/I2C_OneBoard_Communication_IT_Init/Inc/main.h                  Header for main.c module
- I2C/I2C_OneBoard_Communication_IT_Init/Inc/stm32_assert.h          Template file to include assert_failed function
- I2C/I2C_OneBoard_Communication_IT_Init/Src/stm32c0xx_it.c          Interrupt handlers
- I2C/I2C_OneBoard_Communication_IT_Init/Src/main.c                  Main program
- I2C/I2C_OneBoard_Communication_IT_Init/Src/system_stm32c0xx.c      STM32C0xx system source file

Hardware and Software environment

How to use it ?

In order to make the program work, you must do the following :