This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

I2C remote I/O with bigger transfers

Hello,

I have a C++ program that uses IOCTL to communicate over I²C. All goes well when I uses small transfers < 100 bytes. But from the moment I want to transfer bigger chunks, like chunks the size of 110 bytes, I get "Remote I/O" errors and I see that the last 2 bytes are actually removed from the transfer.

Could this be due too a buffer limit or something? I'd guess that the system can cope with about any size I throw at it? The other side is also a custom board with a PIC microcontroller as I2C slave. This device supports clock stretching, but the amount of clock stretching is never longer then 2~3 ms...so I don't think this actually has anything to do with it, as the device even releases the line after the "STOP" has been issued.

I've tried to do the same thing through pyhton, and there I didn't see a problem.

Our hardware:

Custom AM335X based board ( resembles the BeagleBone ).

Tested python on X86 PC with buspirate, so my PIC works as it should!

Kind regards,

Arend