Fix i2c_joystick_2 failed component mark #75
Open
ItsRebaseTime wants to merge 1 commit intom5stack:mainfrom
Open
Fix i2c_joystick_2 failed component mark #75ItsRebaseTime wants to merge 1 commit intom5stack:mainfrom
ItsRebaseTime wants to merge 1 commit intom5stack:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is caused by power sequencing of PowerHub, but some other m5stack devices with dedicated I2C PMU may be affected too.
Since all of the I2C devices are mostly initialized at the same time the powerhub PMU does not have enough time to stabilize the power going to A and B ports and that means that some I2C peripherals may not be able to initialize right at the start. Changing setup priority does not seem to change much, the issue persists.
Can be reproduced by connecting i2c_joystick_2 to any of the 2 PowerHub ports.
Other more sophisticated solutions are welcome, but just not using the "component failed" flag seems to do the trick.