Skip to content
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

Espressif: I2C timeouts calculated based on tick rate. #9538

Closed
wants to merge 1 commit into from

Conversation

bill88t
Copy link

@bill88t bill88t commented Aug 19, 2024

100 * tick rate / 1000

Does not affect or fix #9535 unfortunately.

Copy link
Collaborator

@dhalbert dhalbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In V5.3, i2c_master_write_to_device() is deprecated and replaced with i2c_master_transmit(), which takes the timout in ms. I think it would be good to upgrade to that.

We changed CONFIG_FREERTOS_HZ from 100 to 1000 for most boards in #9134. So the old timeout was 100 10ms ticks = 1 second, not 100ms, which is what it is with the new CONFIG_FREERTOS_HZ . That may be the problem in #9535. Your change in this PR keeps it at 100 ticks (100 ms).

Copy link
Collaborator

@dhalbert dhalbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried in 9.1.x lengthening all the timeouts to 1000 ticks. This did not help #9535 either.

@bill88t
Copy link
Author

bill88t commented Aug 21, 2024

Closing this, as we'll eventually switch to the new adc api.

@bill88t bill88t closed this Aug 21, 2024
@bill88t bill88t deleted the i2cticktime branch August 21, 2024 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ESP32-S3 I2C timeout with seesaw
2 participants