Skip to content

STM32: Fix I2C stop condition #8280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 8, 2018
Merged

STM32: Fix I2C stop condition #8280

merged 1 commit into from
Oct 8, 2018

Conversation

bcostm
Copy link
Contributor

@bcostm bcostm commented Sep 28, 2018

Description

Need to ensure the transmission has been started before sending a STOP condition. Issue found with ci-test shield I2C test when a high frequency system clock is in used.

Tested OK on the following NUCLEO boards + all toolchains: F091, F103, F207, F303, F446, F767, L073, L152, L476

Pull request type

[X] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Breaking change

Need to ensure the transmission has been started before sending a STOP condition.

Issue found on the NUCLEO_H743ZI due certainly to the high-speed clock used.

But this is normally needed also on all STM32 devices using the I2C peripheral version 2.
@NirSonnenschein
Copy link
Contributor

/morph build

@mbed-ci
Copy link

mbed-ci commented Oct 7, 2018

Build : SUCCESS

Build number : 3270
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8280/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

@mbed-ci
Copy link

mbed-ci commented Oct 7, 2018

@mbed-ci
Copy link

mbed-ci commented Oct 7, 2018

@cmonr cmonr merged commit 8fd9944 into ARMmbed:master Oct 8, 2018
@bcostm bcostm deleted the fix_i2c_stop branch October 9, 2018 11:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants