1 reply to this topic

[bsilvereagle]

2. For existing shields which use I2C, you'll want to connect jumper wires between SDA/SCL and A4/A5 for the moment. We're working on an enhancement for the I2C class which will mirror the I2C data on A4/A5 by default (and also turn off the mirroring...so you can get two extra GPIOs instead). That new feature will be available in a December firmware update, giving us the best of both worlds. The same firmware update will bring I2C to Shield Base.

I am using a Shield Base with a Netduino go and was wondering when I2C was going to be implemented. Is there a firmer date than "December" from the above quote? Or if there was an alpha/beta firmware that already implemented I2C for the shield base.

Thanks for all the good work.

[Chris Walker]

Hi bsilvereagle,

I am using a Shield Base with a Netduino go and was wondering when I2C was going to be implemented. Is there a firmer date than "December" from the above quote? Or if there was an alpha/beta firmware that already implemented I2C for the shield base.

We're working on smoothing out a glitch in the SDA/SCL I2C drivers on Netduino Plus 2 right now...and then we'll finish up all the code for A4/A5 I2C (for both Netduino Plus 2 and Shield Base). We expect to start in late November and complete them by the holiday break.

Chris

P.S. A4/A5 and SDA/SCL are tied together on Shield Base...so we'll get I2C on both of them in the same firmware drop.

P.P.S. Once I2C is on Shield Base, the last thing to do before bringing it out of beta is switching it to native code and the GoBus SPI transport. We're almost there; I'm very excited.