The Netduino forums have been replaced by new forums at community.wildernesslabs.co.
This site has been preserved for archival purposes only
and the ability to make new accounts or posts has been turned off.
This SoftwareI2CBus class can be used to help workaround Netduino Plus 2 I2C problems.
I was able to successfully read from my I2C EEPROM. Another advantage is that you can choose to use different pins too.
(Note this leverages a software I2C driver written by our peers over at tinyclr and GHI. Note that a portion must be downloaded from the tinyclr site (link will show when you try to compile). The value I added was to replace the custom APIs with ones more compatible with the standard I2C APIs. Known issue: read/write timeouts are either fixed or otherwise ignored.)
Good luck guys! The Netduino Plus 2 is a great platform, and hopefully this can help one or two folks that hit the early defects in I2C.
Usage comparison between hardware and software I2C:
Lol! I see Chris posted an I2C fix 25 minutes earlier than my workaround.
I am looking forward to trying out the fix, and will probably keep using the workaround to avoid jumpering SCL/SDA until the official Secret Labs mirroring I2C solution is available.
Very cool. Thanks for creating this software I2C solution.
This actually has a lot of uses beyond using A4/A5... If users need 10 I2C buses (for instance if they have 10 I2C devices with the same I2C address) they could use your code for that.
This SoftwareI2CBus class can be used to help workaround Netduino Plus 2 I2C problems.
I was able to successfully read from my I2C EEPROM. Another advantage is that you can choose to use different pins too.
(Note this leverages a software I2C driver written by our peers over at tinyclr and GHI. Note that a portion must be downloaded from the tinyclr site (link will show when you try to compile). The value I added was to replace the custom APIs with ones more compatible with the standard I2C APIs. Known issue: read/write timeouts are either fixed or otherwise ignored.)
Good luck guys! The Netduino Plus 2 is a great platform, and hopefully this can help one or two folks that hit the early defects in I2C.
Usage comparison between hardware and software I2C:
I played around with this a bit. Very useful code. I was able to get a few things up and running just for testing purposes. A few of the sensors I have don't seem to work with the Software solution. I didn't spend much time on it because it would be a major rewrite to get some of my code working. It still proved useful to get the DS1307 running in order to continue prototyping a portion of my project.
I played around with this a bit. Very useful code. I was able to get a few things up and running just for testing purposes. A few of the sensors I have don't seem to work with the Software solution. I didn't spend much time on it because it would be a major rewrite to get some of my code working. It still proved useful to get the DS1307 running in order to continue prototyping a portion of my project.
Thank you for contributing this.
Good to hear the feedback. And I'm lucky to be leveraging someone else's underlying software I2C driver so I can blame them for anything that didn't work :-)
As for the DS1307, I was able to wire a bare DS1307 PDIP-8 package, 32.768kHz crystal, plus 3.3K pull-up resistors, ground VBAT as not used, leaving SQW/OUT unwired, then wired directly to the Plus 2 using the SC/SD pins, and successfully communicated to it using the hardware solution (using NP2 Update 1 of course). I set the time at the top of my program, and on a loop see the time advance.
Have you been able to get the DS1307 to work using the hardware solution? Or are you using the software solution so you can use different pins?
Good to hear the feedback. And I'm lucky to be leveraging someone else's underlying software I2C driver so I can blame them for anything that didn't work :-)
As for the DS1307, I was able to wire a bare DS1307 PDIP-8 package, 32.768kHz crystal, plus 3.3K pull-up resistors, ground VBAT as not used, leaving SQW/OUT unwired, then wired directly to the Plus 2 using the SC/SD pins, and successfully communicated to it using the hardware solution (using NP2 Update 1 of course). I set the time at the top of my program, and on a loop see the time advance.
Have you been able to get the DS1307 to work using the hardware solution? Or are you using the software solution so you can use different pins?
So far I haven't been able to get anything I2C related working with then ND+2 using Hardware I2C.
Basically what I am seeing is the transferred bytes is showing 0 (zero). What I found interesting is when it creates the new I2CDevice (adxl345) the object type in the ND+ shows as {Microsoft.SPOT.Hardware.I2CDevice} but in the ND+2 it shows as {Microsoft.SPOT.Hardware.Battery.ChargerModel}. Also if I run a watch on "new I2CDevice.Configuration(0x53, 400)" you can see that the Address and Speed get reversed in the object although this is the correct parameter order. I get the same results with all I2C modules I have here (listed below the code).
I2CDevice i2c = new I2CDevice(new I2CDevice.Configuration(0x53, 400));
I2CDevice.I2CWriteTransaction write = I2CDevice.CreateWriteTransaction(new Byte[] { 0x00 });
I2CDevice.I2CReadTransaction read = I2CDevice.CreateReadTransaction(_data);
I2CDevice.I2CTransaction[] actions = new I2CDevice.I2CTransaction[] { write, read };
int total = i2c.Execute(actions, 1000);
Debug.Print(total + " bytes transferred successfully over I2C");
Debug.Print(_data[0].ToString());
I'll Give it a shot tomorrow. As you can see from my Earlier Parts list, I'm using the DS1307 breakout from adafruit. I'll have to check the schematic to see what resistors they have but I think it was 2.2k, otherwise the chip and crystal are the same. I'll give your code a shot tomorrow and report back.
Basically what I am seeing is the transferred bytes is showing 0 (zero). What I found interesting is when it creates the new I2CDevice (adxl345) the object type in the ND+ shows as {Microsoft.SPOT.Hardware.I2CDevice} but in the ND+2 it shows as {Microsoft.SPOT.Hardware.Battery.ChargerModel}.
On Battery.ChargerModel...it looks like the debugger link is one method off. This is something we can fix...but it is most likely just cosmetic. We're rebuilding the source one piece at a time to see what's throwing it off.
Regarding I2C...we found one more bug. I2C was working consistently for us when we deployed an app...but when we powered on the board or configured the pins in our app, it no longer worked. This is fixed in the new 4.2.1.2 release (just posted).
At this point, if there are any remaining I2C glitches we'll start analyzing individual configurations. We're happy to do so...but hopefully I2C is working great for everyone (or almost everyone) now--on the SDA/SCL pins.
On Battery.ChargerModel...it looks like the debugger link is one method off. This is something we can fix...but it is most likely just cosmetic. We're rebuilding the source one piece at a time to see what's throwing it off.
Regarding I2C...we found one more bug. I2C was working consistently for us when we deployed an app...but when we powered on the board or configured the pins in our app, it no longer worked. This is fixed in the new 4.2.1.2 release (just posted).
At this point, if there are any remaining I2C glitches we'll start analyzing individual configurations. We're happy to do so...but hopefully I2C is working great for everyone (or almost everyone) now--on the SDA/SCL pins.
Chris
Nice waking up to new releases . I'll flash it and give it a try. I'll post the results in a few hours.
ran across this thread because im running into the same troubles getting I2C to work properly. I flashed my N+2 with the 4.2.1.2 firmware and tried the test program provided a few posts above and im getting nothing back. I thought maybe it was a problem with the DS1307 (from sparkfun) so i tried it on the arduino i have and it works fine.
I doubt that the device is having a hardware issue but unfortunately i dont have any other way to test it.
Ryan
ran across this thread because im running into the same troubles getting I2C to work properly. I flashed my N+2 with the 4.2.1.2 firmware and tried the test program provided a few posts above and im getting nothing back. I thought maybe it was a problem with the DS1307 (from sparkfun) so i tried it on the arduino i have and it works fine.
I doubt that the device is having a hardware issue but unfortunately i dont have any other way to test it.
Ryan
I can verify that DS1307 works with Version 4.2.1.2. So lets walk through your setup. How is it wired? Are you using the new SDA & SCL pins? Is the sensor wired to 5V or 3.3V? Can you post up a sample of your code?
Sure, thanks for the help.
Its wired as 5V -> 5V, GND -> GND, SCL -> SC, SDA -> SD and the code i was using was the one from a few posts up. I plugged it back into the arduino and now im getting nothing back on that board as well. *shrug*
Ive got a second one coming in the mail anyways so ill test that one when it gets here but ill take a look at the solder joints, maybe i messed one up and the connection isnt good.
Ryan
I can verify that DS1307 works with Version 4.2.1.2. So lets walk through your setup. How is it wired? Are you using the new SDA & SCL pins? Is the sensor wired to 5V or 3.3V? Can you post up a sample of your code?
"new SDA & SCL pins" ???
Are we not using 4 and 5 anymore?
I think I need to write an AI data-mining agent to sift through the forums for these bits of info... when/where/why/how were the pins changed?
I think I need to write an AI data-mining agent to sift through the forums for these bits of info... when/where/why/how were the pins changed?
The Netduino Plus 2 has an extended Header that has separate SDA and SCL pins. Right now the firmware only supports these pins. You would need to jump to the A4/A5 pins to use older shields with the Netduino Plus 2. Chris is working on some updates to allow the firmware to be configured to use either setup, but this is too come.
The Netduino Plus 2 has an extended Header that has separate SDA and SCL pins. Right now the firmware only supports these pins. You would need to jump to the A4/A5 pins to use older shields with the Netduino Plus 2. Chris is working on some updates to allow the firmware to be configured to use either setup, but this is too come.
so i touched up the solder joints and the rtc is working again on the arduino but not the netduino. Ive tried the SD/SC pins as well as analog 4 / 5 and no dice. the chipset you are using is the adafruit model which is a bit different than mine so im curious if thats the case.
Its either a hardware issue or a voltage issue. When i measure the voltage on the SD or SC lines when powered from the arduino its 4.97V and on the netduino its returning 0.1v
Kinda frustrating =\
Ryan
I tried the software I2C and was able to read the device (granted only every 3rd read was a success but that may just be the code) but id still like to figure out whats up with the hardware I2C implementation.
Ryan
SoftwareI2CSample.zip 12KB
174 downloads
. I'll flash it and give it a try. I'll post the results in a few hours.
Scared me 
