STM32F4硬件i2c通信（使用HAL库）

/** @page I2C_OneBoard_ComSlave7_10bits_IT I2C One Board Communication Slave 10-Bit then Slave 7-Bit IT example @verbatim ******************** (C) COPYRIGHT 2017 STMicroelectronics ******************* * @file Examples_MIX/I2C/I2C_OneBoard_ComSlave7_10bits_IT/readme.txt * @author MCD Application Team * @brief Description of the I2C One Board Master Communication with * a Slave 10-Bit address then a Slave 7-Bit address example. ****************************************************************************** * * Redistribution and use in source and binary forms, with or without modification, * are permitted provided that the following conditions are met: * 1. Redistributions of source code must retain the above copyright notice, * this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright notice, * this list of conditions and the following disclaimer in the documentation * and/or other materials provided with the distribution. * 3. Neither the name of STMicroelectronics nor the names of its contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * ****************************************************************************** @endverbatim @par Example Description This example describes how to perform I2C data buffer transmission/reception between one master and 2 slaves with different address sizes (7-bit or 10-bit) and different Max speed support (400Khz or 100Khz). This example uses the STM32F4xx I2C HAL and LL API (LL API usage for performance improvement) and an interrupt. Board: NUCLEO-F411RE (embeds a STM32F411xx device) SCL MASTER Pin: PB.10 (CN10, pin 25) SDA MASTER Pin: PB.3 (CN10, pin 31) SCL SLAVE Pin: PB.6 (CN10, pin 17) SDA SLAVE Pin: PB.7 (CN7, pin 21) ____________________________________________ | ____________ ____________ | | | I2C2 | | I2C1 | | | | | | | | | | SCL_MASTER|________|SCL_SLAVE | | | | | | | | | | | | | | | | SDA_MASTER|________|SDA_SLAVE | | | |____________| |____________| | | __ | | |__| | | USER | | | |___________NUCLEO-F411RE_________| At the beginning of the main program the HAL_Init() function is called to reset all the peripherals, initialize the Flash interface and the systick. Then the SystemClock_Config() function is used to configure the system clock (SYSCLK) to run at 100 MHz. The I2C peripheral configuration is ensured by the HAL_I2C_Init() function. This later is calling the HAL_I2C_MspInit()function which core is implementing the configuration of the needed I2C resources according to the used hardware (CLOCK, GPIO and NVIC). You may update this function to change I2C configuration. For this example two buffers are used - aTxBuffer buffer contains the data to be transmitted - aRxBuffer buffer is used to save the received data Note that both buffers have same size Example execution: First step, press the User push-button, this action initiates a reception process (aRxBuffer) for I2C Slave1 or Slave2 address through HAL_I2C_Slave_Receive_IT(). Then I2C Master starts the communication by sending aTxBuffer through HAL_I2C_Master_Transmit_IT() for Slave1 (10-Bit address) at max speed supported 400Khz. The end of this step is monitored through the HAL_I2C_GetState() function result. Finally, aTxBuffer and aRxBuffer are compared through Buffercmp() in order to check buffers correctness. Toggle LED2 when data is received correctly, otherwise LED2 is slowly blinking (1 sec. period) and communication is stopped (using infinite loop) Second step, press the User push-button, this action initiates a transmission process (aTxBuffer) for I2C Slave1 or Slave2 address through HAL_I2C_Slave_Transmit_IT(). Then I2C Master starts the communication by receiving aRxBuffer through HAL_I2C_Master_Transmit_IT() from Slave2 (7-Bit address) at max speed supported 100Khz. The end of this two steps are monitored through the HAL_I2C_GetState() function result. Finally, aTxBuffer and aRxBuffer are compared through Buffercmp() in order to check buffers correctness. Toggle LED2 when data is received correctly, otherwise LED2 is slowly blinking (1 sec. period) and communication is stopped (using infinite loop) @note In Master side, only Acknowledge failure error is handled. When this error occurs Master restart the current operation until Slave acknowledges it's address. @note I2C2 and I2C1 instance used and associated resources can be updated in "main.h" file depending hardware configuration used. @note Care must be taken when using HAL_Delay(), this function provides accurate delay (in milliseconds) based on variable incremented in SysTick ISR. This implies that if HAL_Delay() is called from a peripheral ISR process, then the SysTick interrupt must have higher priority (numerically lower) than the peripheral interrupt. Otherwise the caller ISR process will be blocked. To change the SysTick interrupt priority you have to use HAL_NVIC_SetPriority() function. @note The application need to ensure that the SysTick time base is always set to 1 millisecond to have correct HAL operation. @par Directory contents - Examples_MIX/I2C/I2C_OneBoard_ComSlave7_10bits_IT/Inc/stm32f4xx_hal_conf.h HAL configuration file - Examples_MIX/I2C/I2C_OneBoard_ComSlave7_10bits_IT/Inc/stm32f4xx_it.h I2C interrupt handlers header file - Examples_MIX/I2C/I2C_OneBoard_ComSlave7_10bits_IT/Inc/main.h Header for main.c module - Examples_MIX/I2C/I2C_OneBoard_ComSlave7_10bits_IT/Src/stm32f4xx_it.c I2C interrupt handlers - Examples_MIX/I2C/I2C_OneBoard_ComSlave7_10bits_IT/Src/main.c Main program - Examples_MIX/I2C/I2C_OneBoard_ComSlave7_10bits_IT/Src/system_stm32f4xx.c STM32F4xx system source file - Examples_MIX/I2C/I2C_OneBoard_ComSlave7_10bits_IT/Src/stm32f4xx_hal_msp.c HAL MSP file @par Hardware and Software environment - This example runs on STM32F411RE 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-but