I2C_TwoBoards_WakeUpFromStop_IT_Init Example Description

How to handle the reception of a data byte from an I2C slave device in Stop0 mode by an I2C master device, both using interrupt mode. The peripheral is initialized with LL unitary service functions to optimize for performance and size.

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

   Boards: NUCLEO-C031C6 (embeds a STM32C031C6 device)
   - SCL Pin: PB.8 (CN10, pin 3)
   - SDA Pin: PB.9 (CN10, pin 5)

The project is split in two parts the Master Board and the Slave Board :

The user can choose between Master and Slave through “#define SLAVE_BOARD” in the “main.h” file:

The user can disable internal pull-up by opening ioc file. For that, user can follow the procedure :

1- Double click on the I2C_TwoBoards_WakeUpFromStop_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- Last step, generate new code thanks to button “GENERATE CODE”

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

A first program launch, BOARD SLAVE is in Stop0 mode and BOARD MASTER is waiting User action on User push-button. LED4 blinks quickly on BOARD MASTER to wait for user-button press.

Example execution:

Press the User push-button on BOARD MASTER 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 of BOARD SLAVE, a wake up is initiate and an ADDR interrupt occurs. I2C1 Slave 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 I2C1 of BOARD MASTER, 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 Slave IRQ handler routine by a clear of NACK flag. The STOP condition generate a STOP interrupt in both side (Slave and Master). Both I2C1 IRQ handler routine are then clearing the STOP flag in both side.

LED4 is ON on Slave side if the byte is well transmitted.

LED4 is ON on Master side if the expected byte is well received.

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

Keywords

Connectivity, I2C, Communication, Transmission, Reception, SCL, SDA, Wake up, Interrupt

Directory contents

Hardware and Software environment

How to use it ?

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