You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the I2C fails (such as when there is no I2C chip connected on that address), the actual timeout is almost 1 second exactly. The timeout ticks setting seems to be ignored, and is in any case completely wrong.
What is the actual behavior?
A 50 ms timeout setting should result in a 50 ms timeout, not 1000 ms.
Steps to reproduce.
Use i2c_master_write_to_device with a timeout and an address that isn't present on the bus. Time it.
Debug Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
ESP32-S3 i2c_master_write_to_device timeout is incorrect
ESP32-S3 i2c_master_write_to_device timeout is incorrect (IDFGH-10347)
Jun 6, 2023
Answers checklist.
IDF version.
ca8bf60
Operating System used.
Linux
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
None
Development Kit.
Custom board
Power Supply used.
External 3.3V
What is the expected behavior?
I'm using i2c_master_write_to_device() with a 50 millisecond timeout:
i2c_master_write_to_device( I2C_PORT, dev_addr, (uint8_t *)src, len, pdMS_TO_TICKS(50) );
When the I2C fails (such as when there is no I2C chip connected on that address), the actual timeout is almost 1 second exactly. The timeout ticks setting seems to be ignored, and is in any case completely wrong.
What is the actual behavior?
A 50 ms timeout setting should result in a 50 ms timeout, not 1000 ms.
Steps to reproduce.
Use i2c_master_write_to_device with a timeout and an address that isn't present on the bus. Time it.
Debug Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: