-
Notifications
You must be signed in to change notification settings - Fork 39
Bug In I2C Library #173
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
Crazy. Yep. Looks like it is currently only affecting a few variants:
Everything else with a count of 1 or 2 shouldn't have issue. RedBoard has the primary set to IOM 4 and Wire1 at IOM 2. So Wire2 and Wire3 were really pointing at Wire1. I don't think many people use 'Wire2' or 'Wire3' and/or they are instantiating their own class. How did you find this bug? |
Found it while answering this forum question: Basically logging this issue for when I can get to it. Glad it doesn't have much impact (that's probably why we haven't seen it before) but a bug's a bug. |
Ehhh what am I saying this is so easy to fix... >>> import timeit
>>> timeit.timeit('owen.fix_bug()', number=10000) |
Seems like all the
Wire
objects use the macroAP3_Wire1_IOM
when they should useSee the source code here
The text was updated successfully, but these errors were encountered: