/**
@page I2C_OneBoard_Communication_IT I2C example (IT Mode)
@verbatim
******************** (C) COPYRIGHT 2017 STMicroelectronics *******************
* @file Examples_LL/I2C/I2C_OneBoard_Communication_IT/readme.txt
* @author MCD Application Team
* @brief Description of the I2C_OneBoard_Communication_IT I2C example (IT Mode).
******************************************************************************
* @attention
*
* Copyright (c) 2017 STMicroelectronics.
* All rights reserved.
*
* This software is licensed under terms that can be found in the LICENSE file
* in the root directory of this software component.
* If no LICENSE file comes with this software, it is provided AS-IS.
*
******************************************************************************
@endverbatim
@par Example Description
This example describes how to receive one data byte from an I2C Slave device to an
I2C Master device. Both devices operate in Interrupt mode. Peripheral initialization
is done using LL unitary services functions for optimization purpose (performance and size).
This example guides you through the different configuration steps by mean of LL API
to configure GPIO and I2C peripherals using only one NUCLEO-F411RE.
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.
LED2 blinks quickly to wait for user-button press.
Example execution:
Press the User push-button to initiate a Start condition by Master.
This action will generate an I2C start condition on the I2C bus.
When the I2C start condition is sent on I2C2, a SB interrupt occurs.
I2C2 IRQ Handler routine is then sending the Slave address with a read bit condition.
When address Slave match code is received on I2C1, the Slave acknowledge the address.
When this acknowledge is received on I2C2, an ADDR interrupt occurs.
I2C2 IRQ Handler routine is then preparing the enable of data acknowledge and interrupts for next statement.
When address Slave match code is received on I2C1, an ADDR interrupt occurs.
I2C1 IRQ Handler routine is then checking the slave direction at Write (mean read direction for Master).
This will allow Slave to enter in transmitter mode and then send a byte when TXE interrupt occurs.
When byte is received on I2C2, an RXNE interrupt occurs.
When DR register is read, Master disable all I2C2 interrupts and generate a Non-acknowledge then a STOP condition
to inform the Slave that the transfer is finished.
The Non-acknowledge condition generate a AF interrupt in Slave side treated in the I2C1 IRQ handler routine by a clear of NACK flag
and disable all I2C1 interrupts.
LED2 is On if data is well received.
In case of errors, LED2 is blinking.
@par Keywords
Connectivity, Communication, I2C, IT , Master, Slave, Transmission, Reception, Fast mode,
@par Directory contents
- I2C/I2C_OneBoard_Communication_IT/Inc/stm32f4xx_it.h Interrupt handlers header file
- I2C/I2C_OneBoard_Communication_IT/Inc/main.h Header for main.c module
- I2C/I2C_OneBoard_Communication_IT/Inc/stm32_assert.h Template file to include assert_failed function
- I2C/I2C_OneBoard_Communication_IT/Src/stm32f4xx_it.c Interrupt handlers
- I2C/I2C_OneBoard_Communication_IT/Src/main.c Main program
- I2C/I2C_OneBoard_Communication_IT/Src/system_stm32f4xx.c STM32F4xx system source file
@par Hardware and Software environment
- This example runs on STM32F411xx devices.
- This example has been tested with NUCLEO-F411RE board and can be
easily tailored to any other supported device and development board.
- NUCLEO-F411RE Set-up
- Connect GPIOs connected to I2C1 SCL/SDA (PB.6 and PB.7)
to respectively SCL and SDA pins of I2C2 (PB.10 and PB.3).
- I2C1_SCL PB.6 (CN10, pin 17) : connected to I2C2_SCL PB.10 (CN10, pin 25)
- I2C1_SDA PB.7 (CN7, pin 21) : connected to I2C2_SDA PB.3 (CN10, pin 31)
- Launch the program. Press User push-button to initiate a read request by Master
then Slave send a byte.
- User can easily change the number of data to transfer by modifying
the initialization of variables ubNbDataToTransmit and ubNbDataToReceive.
@par How to use it ?
In order to make the program work, you must do the following :
- Open your preferred toolchain
- Rebuild all files and load your image into target memory
- Run the example
*/
3d6be4bd40