Support for NeuropixelsV2 BNO055 #61
Merged
Conversation
This file contains 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
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 PR adds configuration and streaming operators for the BNO055 sensor on NeuropixelsV2 headstages, both beta and non-beta versions. The active polling I2C interface required solving multiple synchronization issues at both the software and kernel driver levels. The current solution requires the latest kernel driver 6.1.0.2 to operate correctly.
To allow reuse in both beta and non-beta headstages, the sensor configuration was abstracted by using a new option for registering virtual passthrough devices exposed via the raw DS90UB9X serializer interface. This is not meant as a long-term solution and is expected to remain internal.
ContextTaskwas refactored to allow for "transactions", i.e. block operations on device registers where there is a guarantee that the device context will not be asynchronously disposed mid-transaction. The transaction is cancelled if the device has been disposed upon entering the register lock.Fixes #38