next topic »

[Reply #15 on:]

Ive captured the SCL and SDA and I DO see the Ack and levels are good. But for some reason the Due is not seeing it . This is with the wire library. Ive since used the MPU6050 code with the I2Cdev library and it works. But I would like to get to the heart of the problem. Trying scan by using  error=I2Cdev::readbyte(addr++,0,buff);  in a loop still doesnt work find the Ack.

[Reply #16 on:]

I am also experiencing problems with I2C between two Dues. Nothing working at all so far, I even went back to the basic examples and nothing happened. Are the designers aware of this potential issue with either the pullups or the library (I hope it's the latter!!)? Please acknowledge.

[Reply #17 on:]

Ive captured the SCL and SDA and I DO see the Ack and levels are good. But for some reason the Due is not seeing it . This is with the wire library. Ive since used the MPU6050 code with the I2Cdev library and it works. But I would like to get to the heart of the problem. Trying scan by using  error=I2Cdev::readbyte(addr++,0,buff);  in a loop still doesnt work find the Ack.

The heart of the problem is that each time the wire library checks the TWI status register, the NACK bit is automatically cleared by hardware (34.11.6 TWI Status Register, page 748 in the SAM3X8E datasheet).  The wire library is broken in this regard.  If you need to detect NACK's, you will need to wait for updates, or spin your own interface.

However, it looks like you have trouble detecting ACK's.  I suspect that you probably have some other issue going on.  Try posting your code...

Do not connect two Due's together on a common I2C bus without a buffer of some sort.  The combination of both boards, and their pull-up resistors in parallel, will unnecessarily stress the DUE's TWI pins.  I recommend that the on-board pull-ups be removed from the DUE's pcb by default.  Use larger external pull-up resistors.

How big?  Check this out:
http://www.edn.com/design/analog/4371297/Design-calculations-for-robust-I2C-communications

-Chris

[Reply #18 on:]

Hi, I also have some trouble with the I2C: I am very new to this communication protocol, So I was trying to see how it works, and I tried making my Due and my Uno talk to each other. It worked, but when I send charters from the Due to the Uno, half is lost.
Here are my codes:
for the Uno (slave):

Code:

#include <Wire.h>
char buffer[64];
byte serialpos=0, wirepos=0;
void setup() {
  // put your setup code here, to run once:
   Wire.begin(0x02);
   Serial.begin(115200);
   Serial.println("I2C test Starting...");
   Wire.onRequest(handler);
   Wire.onReceive(receiver);
}

void loop() {
  if(Serial.available())
  {
    buffer[serialpos]=Serial.read();
    serialpos++;if(serialpos>64)serialpos=0;
  }
  // put your main code here, to run repeatedly:
 
}
void handler()
{
  if(wirepos<serialpos)
  {
  Wire.write(buffer[wirepos]);
  wirepos++;if(wirepos>64)wirepos=0;
  }
}
void receiver(int num)
{
  while(Wire.available())
  {
    char c=Wire.read();
    Serial.println(c);
  }
}

and for the Due (master):

Code:

#include <Wire.h>
int old, now;
void setup() {
  // put your setup code here, to run once:
   Wire.begin();
   Serial.begin(115200);
   Serial.println("I2C test starting...");
   old=millis();now=millis();
}

void loop() {
  if(Serial.available())
  {
    Wire.beginTransmission(0x02);
    Wire.write(Serial.read());
    Wire.endTransmission();
  }
  now=millis();
  if(now-old>1001)
  {
    old=now;
    Wire.requestFrom(0x02,1);
    delay(10);
    while(Wire.available())
    {
      char c=Wire.read();
      if(c>31)Serial.println(c);
    }
  }
  // put your main code here, to run repeatedly:
 
}

Any help will be appreciated. Thanks.

[Reply #19 on:]

I'm not even getting a clock signal on SCL1, just running the example file "master reader"! SCL1 just sits low at 0V (referenced to a gnd pin) and SCL(21) does the opposite (3.3V). I was surprised by how easy it was to pull SCL1 high even with a 100k resistor, as though it is not trying to pull down the line at all, ever. Is my Due faulty? Is there some special way that SCL should be terminated that I missed which is causing this behaviour? I would really appreciate a developer looking into this as my current project was designed around lots of Dues talking I2C.... oh dear :-( The previous posts suggest that both the Wire library is in error AND that the hardware has been badly designed with too small pullup resistors and that Dues therefore cannot be connected on a single I2C bus. Please confirm. This is such a fundamental (and disappointing) issue!

[Reply #20 on:]

Actually, it's my code which was bad, I modified it and all worked fine for me Sorry for disturbing.

[Reply #21 on:]

Actually, it's my code which was bad, I modified it and all worked fine for me Sorry for disturbing.

It would be nice if you share your new code with us.

[Reply #22 on:]

yep sorry. here it goes: for the Due (master)

Code:

#include <Wire.h>
int old, now;
void setup() {
  // put your setup code here, to run once:
   Wire.begin();
   Serial.begin(115200);
   Serial.println("I2C test starting...");
   old=millis();now=millis();
}

void loop() {
  if(Serial.available())
  {
    Wire.beginTransmission(0x02);
    Wire.write(Serial.read());
    Wire.endTransmission();
  }
    old=now;
    Wire.requestFrom(0x02,1);
    //delay(1);
    while(Wire.available())
    {
      char c=Wire.read();
      if(c>31)Serial.println(c);
    }
  // put your main code here, to run repeatedly:
 
}

and for the Uno:

Code:

#include <Wire.h>
char buffer[256];
byte serialpos=0, wirepos=0;
void setup() {
  // put your setup code here, to run once:
   Wire.begin(0x02);
   Serial.begin(115200);
   Serial.println("I2C test Starting...");
   Wire.onRequest(handler);
   Wire.onReceive(receiver);
}

void loop() {  // put your main code here, to run repeatedly:
 
}
void handler()
{
  if(Serial.available())
  {
    char c=Serial.read();
    Wire.write(c);
  }
}
void receiver(int num)
{
  while(Wire.available())
  {
    char c=Wire.read();
    Serial.println(c);
  }
}

Hope this helps