I think this can only mean that a device isn't responding to the address you're providing. Did you set the i2c device address to the same value used with i2ctest?
On Thu, Aug 14, 2014 at 10:09 AM, Akhil Panyamparambil < akhilpana...@gmail.com> wrote: > Hi all. Can you guys help me.I am using beaglebone black i2c2 pin 19 and > 20 of p9. Somewhere in the net it was told i2c2 has told accessed with > i2c-1 in /dev folder. I am booting default amstrom linux from emmc. > Hardware is completely checked and verified. I have connected 3 io > expansion modules to i2c bus. I can communicate to them by i2ctest commands > from command line. But the problem is with the file writes. I cant write to > /dev/i2c-1 file with "write" function. The file descriptor doeant have an > error. Also the ioctl calls doest make any errors. But the write function > is having problem. And thus I cant access i2c bus in application layer. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/vbuM-4oShS8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
