diff options
Diffstat (limited to 'Projects/P-NUCLEO-WB55.Nucleo/Examples_LL/I2C/I2C_OneBoard_Communication_IT_Init/readme.txt')
| -rw-r--r-- | Projects/P-NUCLEO-WB55.Nucleo/Examples_LL/I2C/I2C_OneBoard_Communication_IT_Init/readme.txt | 101 |
1 files changed, 101 insertions, 0 deletions
diff --git a/Projects/P-NUCLEO-WB55.Nucleo/Examples_LL/I2C/I2C_OneBoard_Communication_IT_Init/readme.txt b/Projects/P-NUCLEO-WB55.Nucleo/Examples_LL/I2C/I2C_OneBoard_Communication_IT_Init/readme.txt new file mode 100644 index 000000000..a6fa05009 --- /dev/null +++ b/Projects/P-NUCLEO-WB55.Nucleo/Examples_LL/I2C/I2C_OneBoard_Communication_IT_Init/readme.txt @@ -0,0 +1,101 @@ +/** + @page I2C_OneBoard_Communication_IT_Init I2C example (IT Mode) + + @verbatim + ****************************************************************************** + * @file Examples_LL/I2C/I2C_OneBoard_Communication_IT_Init/readme.txt + * @author MCD Application Team + * @brief Description of the I2C_OneBoard_Communication_IT_Init I2C example (IT Mode). + ****************************************************************************** + * + * Copyright (c) 2019 STMicroelectronics. All rights reserved. + * + * This software component is licensed by ST under BSD 3-Clause license, + * the "License"; You may not use this file except in compliance with the + * License. You may obtain a copy of the License at: + * opensource.org/licenses/BSD-3-Clause + * + ****************************************************************************** + @endverbatim + +@par 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 P-NUCLEO-WB55. + +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/I2C3, 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). +I2C3 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 (SW1) 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 I2C3, 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 I2C3 IRQ handler routine are then +clearing the STOP flag in both side. + +LED2 is On if data is well received. + +In case of errors, LED2 is blinking slowly (1s). + +@par Keywords + +Connectivity, Communication, I2C, Master, Slave, Transmission, Reception, Fast mode + + +@par Directory contents + + - I2C/I2C_OneBoard_Communication_IT_Init/Inc/stm32wbxx_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/stm32wbxx_it.c Interrupt handlers + - I2C/I2C_OneBoard_Communication_IT_Init/Src/main.c Main program + - I2C/I2C_OneBoard_Communication_IT_Init/Src/system_stm32wbxx.c STM32WBxx system source file + +@par Hardware and Software environment + + - This example runs on STM32WB55RGVx devices. + + - This example has been tested with P-NUCLEO-WB55 board and can be + easily tailored to any other supported device and development board. + + - P-NUCLEO-WB55 Set-up + - Connect GPIOs connected to I2C1 SCL/SDA (PB.8 and PB.9) + to respectively SCL and SDA pins of I2C3 (PC.0 and PC.1). + - I2C1_SCL PB.8 (CN10, pin 3) : connected to I2C3_SCL PC.0 (CN7, pin 28) + - I2C1_SDA PB.9 (CN10, pin 5) : connected to I2C3_SDA PC.1 (CN7, pin 30) + + - Launch the program + - Press User push-button (SW1) to initiate a read request by Master + then Slave send a byte. + +@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 + + * <h3><center>© COPYRIGHT STMicroelectronics</center></h3> + */ |