-
Notifications
You must be signed in to change notification settings - Fork 53
mode setter appears wrong #26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hmmm...I think you are correct. Adafruit CircuitPython 3.1.2 on 2019-01-07; Adafruit ItsyBitsy M4 Express with samd51g19
>>> import adafruit_bno055
>>> from busio import I2C
>>> from board import SDA, SCL
>>> i2c = I2C(SCL, SDA)
>>> imu = adafruit_bno055.BNO055(i2c)
>>> imu.mode
12
>>> imu.mode = 5
>>> imu.mode
12
>>> imu.mode = 0
>>> imu.mode
0
>>> imu.mode = 5
>>> imu.mode
5
>>> |
Thank you for confirming. I'll submit a PR in a day or two. |
Fixed by #27 Thanks @peterhinch! |
@peterhinch email me ([email protected]) if you'd like some hardware to test CircuitPython with. We really appreciate your fixes to the drivers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm writing a MicroPython driver for your board. In my testing it is only possible to change the device mode if you first change the mode to
_CONFIG_MODE
. Unfortunately I don't have any hardware capable of running CircuitPython but I think the following test will fail:The need to set
_CONFIG_MODE
prior to setting any other mode is contradicted in the chip datasheet (section 3.3.1). Consequently before I submit a PR I would be grateful if someone could perform the above test to confirm my findings.For reference this is my mode setting code. This includes delays mandated by the device datasheet.
The text was updated successfully, but these errors were encountered: