From: Chris E. <ch...@ns...> - 2006-12-22 20:37:44
|
I am writing code for the robostix and moving it from the gumstix with i2c-load. # i2c-load --reboot 0x0b write Servo-Test.hex Detected ATMega128 Write: ## Verify: ## Verify sucessful Write sucessful, rebooting... Okay, it works. I play around with the board for a couple of minutes, make a few changes to my code and... # i2c-load --reboot 0x0b write Servo-Test.hex ERROR: I2cTransfer: ioctl failed: Remote I/O error (121) ERROR: I2cReadBlock failed ERROR: Unable to retrieve boot information from i2c address 0x0b Now I get this message upon all further invocations of i2c-load. The only way I have found to fix it is to reinstall i2c-load entirely. What am I doing wrong here? |
From: Jason v. N. <ja...@vo...> - 2006-12-22 20:39:22
|
I don't have my copy handy at the moment to check, but the command is --reset, not --reboot. Perhaps it's an alias for it, but I don't think so. Probably your Robostix is not being reset into the bootloader so that i2c-load can talk to it. Jason Chris Evans wrote: > I am writing code for the robostix and moving it from the gumstix with > i2c-load. > > # i2c-load --reboot 0x0b write Servo-Test.hex > Detected ATMega128 > Write: ## > Verify: ## > Verify sucessful > Write sucessful, rebooting... > > Okay, it works. I play around with the board for a couple of minutes, > make a few changes to my code and... > > # i2c-load --reboot 0x0b write Servo-Test.hex > ERROR: I2cTransfer: ioctl failed: Remote I/O error (121) > ERROR: I2cReadBlock failed > ERROR: Unable to retrieve boot information from i2c address 0x0b > > Now I get this message upon all further invocations of i2c-load. The > only way I have found to fix it is to reinstall i2c-load entirely. > What am I doing wrong here? > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Chris E. <ch...@ns...> - 2006-12-22 20:50:24
|
Doh. You're correct. --reset resets the robostix itself, whereas --reboot tells the BootLoader to reboot via I2C. On 12/22/06, Jason von Nieda <ja...@vo...> wrote: > > I don't have my copy handy at the moment to check, but the command is > --reset, not --reboot. Perhaps it's an alias for it, but I don't think so. > Probably your Robostix is not being reset into the bootloader so that > i2c-load can talk to it. > > Jason > > > Chris Evans wrote: > > I am writing code for the robostix and moving it from the gumstix with > i2c-load. > > # i2c-load --reboot 0x0b write Servo-Test.hex > Detected ATMega128 > Write: ## > Verify: ## > Verify sucessful > Write sucessful, rebooting... > > Okay, it works. I play around with the board for a couple of minutes, make > a few changes to my code and... > > # i2c-load --reboot 0x0b write Servo-Test.hex > ERROR: I2cTransfer: ioctl failed: Remote I/O error (121) > ERROR: I2cReadBlock failed > ERROR: Unable to retrieve boot information from i2c address 0x0b > > Now I get this message upon all further invocations of i2c-load. The only > way I have found to fix it is to reinstall i2c-load entirely. What am I > doing wrong here? > > ------------------------------ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > ------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li...https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > |
From: Dave H. <dhy...@gm...> - 2006-12-22 21:18:17
|
Hi Chris, On 12/22/06, Chris Evans <ch...@ns...> wrote: > Doh. You're correct. --reset resets the robostix itself, whereas --reboot > tells the BootLoader to reboot via I2C. Yeah - so if you're running a program (like Simple Servo) that doesn't have the i2c stuff in it, then once the bootloader has finished and SimpleServo starts running, you can no longer talk to the robostix via i2c. If you're using a program like i2c-io, you can continue to talk to the robostix over i2c even after the bootlaoder has finished. Using --reset causes a connected robostix (this only works for the one that the gumstix is plugged into) to be reset - hence entering the bootloader for a few seconds. If any i2c command is received in the few second window during the bootloader, then the bootloader stays active and doesn't run the loaded program. The difference between reboot and reset is that reboot is an i2c command send ove the i2c bus, where reset toggle the reset gpio line. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |