Bug In I2C Library

[oclyke]

Seems like all the Wire objects use the macro AP3_Wire1_IOM when they should use

AP3_Wire1_IOM
AP3_Wire2_IOM
AP3_Wire3_IOM
AP3_Wire4_IOM
AP3_Wire5_IOM

See the source code here

[nseidle]

Crazy. Yep. Looks like it is currently only affecting a few variants:

• Artemis module (count = 6)
• RedBoard Artemis (count = 4)
• Edge/Edge2 (count = 3)

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?

[oclyke]

Found it while answering this forum question:
https://forum.sparkfun.com/viewtopic.php?f=169&t=51004

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.

[oclyke]

Ehhh what am I saying this is so easy to fix...

>>> import timeit
>>> timeit.timeit('owen.fix_bug()', number=10000)