Fixes MPU6500 not being detected on Arduino Nano ESP32#120
Open
slavicd wants to merge 1 commit into
Open
Conversation
Owner
|
@slavicd Thanks for this pull-request. However, I can not merge it because it treats the symptom but does not cure the underlying decease. The proper way to fix the reported issue would be to find out why 0x30 is received instead of the 0x70 which the MPU is sending, and fix it such a way that correct 0x70 is received. |
Author
|
Well, I tried finding out and I could not. Tried lowering SPI clock to half speed, tried doubling the register read, in case it's not ready. No success so far. Perhaps someone else can chime in. |
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
2 participants
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.
More of a workaround than fix, but for some reason, as per the discussion, MPU6500's response is seen as 0x30 in Madflight. The reason I say "in Madflight" is because a test with I2C (non-Madflight) returns the expected 0x70.