Different reboots leads to different i2c address for the touch module #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
Sometimes at some boots, the touch feature doesn't work.
It seems the touch module has 2 different addresses on the I2C bus (checked with i2cdetect on a raspberry 4 + screen).
Touch module ok
Log :
I2C address :
Touche module ko
Log :
I2C address :
I don't know exactly why but there is an interesting discussion here : pimoroni/hyperpixel4#41
Thanks @Gadgetoid for the idea to duplicate the related overlay !