[codex] Add BMX160 auxiliary magnetometer init#232
Draft
TobiasRoeddiger wants to merge 1 commit into
Draft
Conversation
|
Build output available: |
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.
Summary
This PR adds a more in-depth BMX160/BMM150 magnetometer initialization path for BMX160 units whose serial numbers require initialization through the BMI160-style auxiliary interface.
The driver now first probes and configures the BMM150 through the auxiliary interface, then falls back to the existing BMX160 magnetometer setup routine if that path is not available.
Why
Some BMX160 serial numbers do not initialize reliably with the previous magnetometer setup sequence alone. This change adds the deeper auxiliary-interface sequence needed by those units while preserving the older BMX160 routine as a fallback.
Compatibility note
This still needs to be verified on hardware to confirm that the new probe-and-fallback flow does not break compatibility with devices that already worked with the old BMX160 routine.
Validation
git diff --check -- src/SensorManager/BMX160/DFRobot_BMX160.cpp src/SensorManager/BMX160/DFRobot_BMX160.hwest build -b openearable_v2/nrf5340/cpuapp; configuration reached toolchain discovery but could not continue because the local Zephyr SDK/toolchain package is not installed or configured.