From: Dave H. <dhy...@gm...> - 2009-10-21 20:47:10
|
Hi, On Wed, Oct 21, 2009 at 12:52 PM, VaibhavGhadiok <vai...@gm...> wrote: > > That solved the problem. I just had one more issue. Hopefully the last one!! > > I tried to search in the forums but surprisingly found nothing. > > On executing "i2c-load --reset 0x0b write i2c-io.hex" from my Gumstix, I get > an error: > ERROR: I2cTransfer: ioctl failed: Remote I/O error (121) > ERROR: I2cReadBlock failed > ERROR: Unable to retreive boot information from i2c address 0x0b I think that error 121 means that the remote device didn't respond. > Has this got anything to do with: > #define I2C_IO_SerialPWM_4 0x0B No - that's a command 0x0B. The address 0x0b is the i2c address of the device. > Everything used to be just fine. So, it is not hardware thing because things > used to work. Sometimes, the i2c driver gets messed up, and you need to reboot. i2c-load only talks with the bootloader, and you shouldn't need to change the bootloader if you rebuild i2c-io. So it should be talking to the identical same bootloader as before. Are lights blinking on the robostix? i.e. is the robostix running? If the robostix was being held in reset, then it won't respond to i2c commands. > On doing ./i2c-test, I get: > gumstix: SCL: 1 SDA: 1 > and then it just waits. This page describes i2c-test <http://docwiki.gumstix.com/index.php/Robostix_i2c_test> You should see LEDs flashing on the robostix. If not, then the robostix isn't running. i2c-test toggles the blue LED once per second. The i2c bootloader uses the red LED. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |