-
Notifications
You must be signed in to change notification settings - Fork 3k
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
STM32: I2C write takes a long time #14732
Comments
Closed/reopened to retrigger the github action for issue handling. |
Hi
Quick check with this I2C test application : https://github.com/ARMmbed/ci-test-shield/blob/master/TESTS/API/I2C/I2C.cpp Before #14557 Add #14557 Add #14776 |
Description of defect
#14557 introduced I2C timing capabilities which wastes 2K of RAM (not really good on small RAM CPUs in my opinion) compared to previous commit 8f2c45c but not only that, if you write to a bus in order to find I2C device address or to check if the "slave" is alive, it takes around 2s. Is this intended? of so this is a breaking change.
Log from the example below
compared to previous it's a huge difference
Target(s) affected by this defect ?
all STM32 i guess, tested on STM32G474RC
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM
What version of Mbed-os are you using (tag or sha) ?
0738aab
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli
How is this defect reproduced ?
The text was updated successfully, but these errors were encountered: