From: mike2323 <mmi...@gm...> - 2009-02-16 15:22:35
|
Here's some more information regarding the robostix 111 error that I was hoping might be helpful. I apologize for the verbosity of the message as I am still new to all of this. I seem to get better results when connecting the robostix to a connex board. Also, I'm using the i2c-Boot-m128-16MHz.hex and i2c-io.hex binaries from Dave Hyland's website. I still get the 111 error, but a lot less frequently. The most frequent error occurs while trying to load the i2c-io.hex file using i2c-load --reset 0x0b write i2c-io.hex as part of a startup script as shown below. I removed the repeated portions of the output for brevity. # ./rs_reboot.sh mknod: /dev/robostix: File exists insmod: error inserting '/rs/robostix_drv.ko': -1 File exists Atmel AVR ATmega128 is found. Fuse Low Byte set to 0xbf Fuse High Byte set to 0xc2 Fuse Extended Byte set to 0xff Atmel AVR ATmega128 is found. Erasing device ... Reinitializing device Atmel AVR ATmega128 is found. Uploading: flash Detected ATMega128 Write: ##ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused (111) ERROR: Error writing 4 bytes to 0x4fc # ./rs_reboot.sh Write: #ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused (111) ERROR: Error writing 28 bytes to 0x38 # ./rs_reboot.sh Write: ## Verify: #ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: BootLoaderRead: I2cReadBlock failed: Connection refused (111) ERROR: Error reading 28 bytes from 0x2a0 # ./rs_reboot.sh Write: #ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused (111) ERROR: Error writing 28 bytes to 0x0 # ./rs_reboot.sh Write: #ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused (111) ERROR: Error writing 28 bytes to 0x0 # ./rs_reboot.sh Write: ## Verify: ## Verify sucessful Write sucessful, rebooting... Once loaded, I was unable to get the 111 error on the i2-io 0x0b info command after issuing 50 of them in a row. Below is the repeated output. version: 2 minVersion: 1 SVN Revision: 1134 I followed that with twenty i2c-load 0x0b info commands without error until the 21st one. Below is the output for the last two commands. # i2c-load 0x0b info I2C Dev Addr: 0x00 Version: 1 MinVersion: 1 Part Number: 0x9702 (ATMega128) Reg Size: 256 RAM Size: 4096 EEPROM Size: 4096 Page Size: 256 Flash Size: 128k Node Name: not set Boot Delay: unset, defaults to 5 seconds I2C Addr: unset, defaults to 0x0b # i2c-load 0x0b info I2C Dev Addr: 0x00 Version: 1 MinVersion: 1 Part Number: 0x9702 (ATMega128) Reg Size: 256 RAM Size: 4096 EEPROM Size: 4096 Page Size: 256 Flash Size: 128k Node Name: not set ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: BootLoaderRead: I2cReadBlock failed: Connection refused (111) Boot Delay: 0 seconds ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: BootLoaderRead: I2cReadBlock failed: Connection refused (111) I2C Addr: 0x00 After that, I issued several more successful i2c-load 0x0b info commands until getting the error again as shown below. # i2c-load 0x0b info I2C Dev Addr: 0x00 Version: 1 MinVersion: 1 Part Number: 0x9702 (ATMega128) Reg Size: 256 RAM Size: 4096 EEPROM Size: 4096 Page Size: 256 Flash Size: 128k ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: BootLoaderRead: I2cReadBlock failed: Connection refused (111) Node Name: '(P' ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: BootLoaderRead: I2cReadBlock failed: Connection refused (111) Boot Delay: 0 seconds ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: BootLoaderRead: I2cReadBlock failed: Connection refused (111) I2C Addr: 0x00 Anyway, I hope someone will find this added information useful. Thanks for your help, - Mike Miller mike2323 wrote: > > Hello, > > I'm hoping that someone can help me with this. I'm a robostix novice. In > the past, I've been able to get the i2c working with the robostix, but > have recently come up against a problem that I just can't get past. I did > quite a bit of searching for an answer, and I did come across one post > that discussed the error, but I never found a resolution. > > I'm getting a 111 error when I use i2c-io or i2c-load. It happens about > every other time I issue the command. Sometimes I'll get two successive > non-error executions, but mostly it alternates between working correctly > and getting the error. > > Below is a screenshot of 6 successive i2c-io executions on my Verdex: > > root@verdex2:/$ i2c-io 0x0b info > version: 2 > minVersion: 1 > SVN Revision: 1604 > root@verdex2:/$ i2c-io 0x0b info > ERROR: I2cTransfer: ioctl failed: Connection refused (111) > ERROR: I2cReadBlock failed > ERROR: Unable to retrieve information from i2c address 0x0b > root@verdex2:/$ i2c-io 0x0b info > version: 2 > minVersion: 1 > SVN Revision: 1604 > root@verdex2:/$ i2c-io 0x0b info > ERROR: I2cTransfer: ioctl failed: Connection refused (111) > ERROR: I2cReadBlock failed > ERROR: Unable to retrieve information from i2c address 0x0b > root@verdex2:/$ i2c-io 0x0b info > version: 2 > minVersion: 1 > SVN Revision: 1604 > root@verdex2:/$ i2c-io 0x0b info > version: 2 > minVersion: 1 > SVN Revision: 1604 > root@verdex2:/$ > > Here's my gumstix-version info: > > Revision 318M > Built on Tue Feb 10 13:35:25 CST 2009 > Build machine: dell-desktop > Target machine: gumstix-custom-verdex > libc: glibc > > Any ideas would be greatly appreciated. > > Thanks, > > - Mike > > -- View this message in context: http://www.nabble.com/i2c-robostix-problem-tp22003358p22039249.html Sent from the Gumstix mailing list archive at Nabble.com. |