Skip to content

I2C Scans for all! (S2 users having ESP_ERR_TIMEOUT: I2C Bus Busy) #710

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 3 commits into from
Closed

I2C Scans for all! (S2 users having ESP_ERR_TIMEOUT: I2C Bus Busy) #710

wants to merge 3 commits into from

Conversation

tyeth
Copy link
Member

@tyeth tyeth commented Mar 7, 2025

This is a draft to keep open with latest build assets for S2 based boards until I2C scans are fixed

@tyeth tyeth mentioned this pull request Mar 7, 2025
Closed
@tyeth tyeth marked this pull request as ready for review March 11, 2025 18:41
@tyeth
Copy link
Member Author

tyeth commented Mar 11, 2025

I'm aware we're closing this, but wanted to test if a frequency change mattered (clock stretching related).

@tyeth
Copy link
Member Author

tyeth commented Mar 11, 2025

Closing this after further fixes in #712
Original symptoms were scan failing, then when logged and retried it reported:

second scan slightly different addresses, and one less timeout:
 I2C Scan Request
 EXEC: I2C Scan
 Found I2C Device at 0x54
 ESP_ERR_TIMEOUT: I2C Bus Busy - (Address: 0x5E - Error Count: 1 of 1)Found I2C Device at 0x119
 ESP_ERR_TIMEOUT: I2C Bus Busy - (Address: 0x7C - Error Count: 1 of 2)I2C Devices Found: 2
 Publishing Message: I2CResponse...Published!

@tyeth tyeth closed this Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@tyeth