Скачать или смотреть Enhancing I2C Communication Between STM32 Boards in Interrupt Mode

Discover how to implement and enhance I2C communication between two STM32 boards using interrupt mode and STM32CubeMX's low-layer functions.
---
This video is based on the question https://stackoverflow.com/q/63500335/ asked by the user 'Amin Darestani' ( https://stackoverflow.com/u/11110078/ ) and on the answer https://stackoverflow.com/a/63536064/ provided by the user 'Zoltán Dolenský' ( https://stackoverflow.com/u/12931378/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: I2C communication between two stm32 board in interrupt mode by low layer functions of STM32CUBEMX

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Enhancing I2C Communication Between STM32 Boards in Interrupt Mode

I2C communication is crucial in many embedded systems, particularly when multiple microcontrollers need to share data. In this guide, we will tackle a common issue faced during I2C communication between two STM32 boards—the STM32F103RB and STM32F429ZG—using interrupt mode with the low-layer functions of STM32CubeMX.

The Problem

You’re working on a project that involves data transmission between two STM32 boards, yet you're facing a challenge: the I2C communication works for only one byte at a time before it ceases to operate. The objective is to allow for repeated transmissions with each button press, but after the initial transfer, communication halts.

Solution Breakdown

To resolve this issue, let's explore the components of the provided master completion callback function and identify the crucial areas to enhance communication flow.

Re-examine Interrupt Handling

A key point to note is the management of interrupts. When you use the function:

[[See Video to Reveal this Text or Code Snippet]]

this disables the event interrupts for your I2C communication. It’s essential to ensure that these interrupts are enabled again before the next transmission. If you're not re-enabling them, the communication will stop after the first round.

Suggested Code Modifications

The callback function is where you control your I2C communication flow. Consider modifying it in the following way:

[[See Video to Reveal this Text or Code Snippet]]

Key Changes:

Re-enable Interrupts: Always ensure that you enable the interrupts before expecting the next transmission to ensure that your controller is listening for incoming data.

Clarity in Data Processing: After confirming the data successfully received, you can proceed to prepare for the next transmission, but don’t forget to re-enable the I2C event interrupts.

Testing and Validation

After implementing the enhancements, you should retest the communication between your STM32 boards:

Code Validation: Ensure the logic flow of your callback function aligns with the expected operation.

Check Waveforms: Use an oscilloscope to examine the transmitted signals. This will help confirm whether the SCL pin returns to a high state after each transmission.

Button Integration: by pressing the buttons for master and slave communication, ensure that the data is transmitted repetitively without interruptions.

Conclusion

I2C communication between two STM32 boards using interrupt mode can be tricky, especially when configuring low-layer functions. By re-evaluating your interrupt handling and ensuring they are correctly enabled before new transmissions, you can solve the issue of repeated failures after the first byte. Implement these changes and your communication should become seamless, allowing for effective data exchange between your devices.

Happy coding! If you have further questions or run into additional issues, feel free to reach out or leave a comment below.