From: David W. <dw...@da...> - 2008-12-06 19:35:49
|
check this page: http://docwiki.gumstix.org/index.php/Robostix_power especially the third paragraph in the second heading "Robostix Voltages". Both sources must be the same voltage. David Warman Computer Systems Architect dw...@da... http://www.davidwarman.net http://www.linkedin.com/in/davidjwarman P: 206-780-9963 M: 206-407-7050 F: 206-842-4958 Skype: david.warman On Dec 6, 2008, at 11:21 AM, Linus Casassa wrote: > I have power only the Robotix and the netpro-vx work well. > I also have power only the netpro-vx and all is the same except the > the uisp doesn't work. > > Are you should I have to power both? Will do a short circuit and burn? > Both expansion will power up the gumstix... > > 2008/12/6 David Warman <dw...@da...>: >> Do you have power applied to both the Robostix and the Netpro, 5v >> each? >> David Warman >> Computer Systems Architect >> dw...@da... >> http://www.davidwarman.net >> http://www.linkedin.com/in/davidjwarman >> P: 206-780-9963 >> M: 206-407-7050 >> F: 206-842-4958 >> Skype: david.warman >> >> >> >> On Dec 6, 2008, at 10:04 AM, Linus Casassa wrote: >> >> Sometimes it works sometimes it doesn't... >> When the error occurs on random bits... so it can't be a problem of >> clocks... >> So that other thing can it be? >> ---------------- >> root@gumstix-custom-verdex:~$ i2c-load --reset 0x0b write i2c-io.hex >> Detected ATMega128 >> Write: #ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused >> (111) >> ERROR: Error writing 28 bytes to 0x2c4 >> root@gumstix-custom-verdex:~$ i2c-load --reset 0x0b write i2c-io.hex >> Detected ATMega128 >> Write: #ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused >> (111) >> ERROR: Error writing 28 bytes to 0x0 >> root@gumstix-custom-verdex:~$ i2c-load --reset 0x0b write i2c-io.hex >> Detected ATMega128 >> Write: ##ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused >> (111) >> ERROR: Error writing 28 bytes to 0x400 >> root@gumstix-custom-verdex:~$ i2c-load --reset 0x0b write i2c-io.hex >> Detected ATMega128 >> Write: #ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused >> (111) >> ERROR: Error writing 28 bytes to 0x0 >> root@gumstix-custom-verdex:~$ i2c-load --reset 0x0b write i2c-io.hex >> Detected ATMega128 >> Write: #ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused >> (111) >> ERROR: Error writing 28 bytes to 0x300 >> root@gumstix-custom-verdex:~$ i2c-load --reset 0x0b write i2c-io.hex >> Detected ATMega128 >> Write: #ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused >> (111) >> ERROR: Error writing 28 bytes to 0x38c >> root@gumstix-custom-verdex:~$ i2c-load --reset 0x0b write i2c-io.hex >> Detected ATMega128 >> Write: ## >> Verify: ## >> Verify sucessful >> Write sucessful, rebooting... >> root@gumstix-custom-verdex:~$ >> >> 2008/12/6 Linus Casassa <li...@li...>: >> >> This is what I get with i2c-test: >> root@gumstix-custom-verdex:~$ ./i2c-test >> gumstix: SCL: 1 SDA: 1 >> gumstix: SCL: 1 SDA: 1 >> robostix: SCLw: 1 SCLr: 1 SDAw: Z SDAr: 1 DDRD: 1 PIND: 3, PORTD: 1 >> gumstix: SCL: 1 SDA: 1 >> robostix: SCLw: 0 SCLr: 0 SDAw: Z SDAr: 1 DDRD: 1 PIND: 2, PORTD: 0 >> gumstix: SCL: 0 SDA: 1 >> gumstix: SCL: 0 SDA: 1 >> robostix: SCLw: Z SCLr: 1 SDAw: Z SDAr: 1 DDRD: 0 PIND: 3, PORTD: 0 >> gumstix: SCL: 1 SDA: 1 >> gumstix: SCL: 1 SDA: 1 >> robostix: SCLw: Z SCLr: 1 SDAw: 1 SDAr: 1 DDRD: 2 PIND: 3, PORTD: 2 >> gumstix: SCL: 1 SDA: 1 >> robostix: SCLw: Z SCLr: 1 SDAw: 0 SDAr: 0 DDRD: 2 PIND: 1, PORTD: 0 >> gumstix: SCL: 1 SDA: 0 >> gumstix: SCL: 1 SDA: 0 >> robostix: SCLw: Z SCLr: 1 SDAw: Z SDAr: 1 DDRD: 0 PIND: 3, PORTD: 0 >> gumstix: SCL: 1 SDA: 1 >> Shutting down... >> root@gumstix-custom-verdex:~$ >> >> On the robostix line, the SCLw: Z means that the robostix has >> tri-stated the SCL line, and it should be pulled high by the pull up >> resistors. SCLw: 1 means that the robostix is driving the line high, >> and SCLw: 0 means that the robostix is driving the line low. The >> SCLr: >> shows what the robostix is reading on the SCL line. The SDA values >> are >> similar. >> In other words: >> if >> (robostic: SCLw == gumstix: SCL || (robostic: SCLw==Z AND gumstix: >> SCL == >> 1)) >> AND >> (robostic: SDAw == gumstix: SDA || (robostic: SDAw==Z AND gumstix: >> SDA == >> 1)) >> then your i2c lines or ok. >> So my i2c lines are working great. :) >> Then why is the i2c-io not working? I am thinking it could be a >> problem of clocks? What should the i2c clock be on both sides? >> What other problem could it be? >> 2008/12/5 David Warman <dw...@da...>: >> >> Hi Steve, >> I am also currently struggling to get talking to the Robostix to >> read the >> A2D inputs. I'd be most grateful if you could share details on how >> you >> worked around these issues? >> General related question for group: >> I'm really looking for a how-to on reading A2D into a Gumstix >> program at >> maximum rate, all the steps from powering up the boards as >> received from >> Gumstix. Like, where to put the code on both sides both in the >> gumstix-oe >> tree and the rootfs, how to get the Robostix up and responding the >> A2D read >> requests from the Gumstix, how to set things up so that the >> Robostix A2D >> application is automatically started at boot, etc. There seems to >> be no >> gumstix.net wiki information on how to do any of this. Just a note >> that >> there is no content yet. Except for the Hello World tutorial, >> which covers >> the Linux side but not the Robostix interactions or start-up. >> Also need some pointers on how to get custom code built on the >> Debian devsys >> side and merged into the rootfs when there are ipkg-installed apps >> on the >> Gumstix side, without having to go through a painful manual >> sequence every >> time. How to update fellow worker's Gumstix, given that once >> delivered all >> their rootfs start diverging immediately. Basically all the post- >> POC project >> management stuff. If such exists. If not, I guess I'll have to >> figure out my >> own way, but it would be nice if there is a community standard >> methodology >> for this. >> I'd point out I am not a newbie when it comes to coding in general >> and >> embedded in particular, just a newbie to OE and the Gumstix way of >> doing >> things. Give a code snippet or two and example directory tree >> paths and >> command lines and I'm happy. >> Thanks, >> David Warman >> Computer Systems Architect >> dw...@da... >> http://www.davidwarman.net >> http://www.linkedin.com/in/davidjwarman >> P: 206-780-9963 >> M: 206-407-7050 >> F: 206-842-4958 >> Skype: david.warman >> >> >> On Dec 5, 2008, at 9:44 AM, Steve McLaughlin wrote: >> I originally posted that. At least that makes me feel like I'm >> not crazy. >> I never did fix that problem...I'm working around it by using the >> UART >> instead of I2C...I imagine the problem is not high priority now >> that the >> overo is out... >> -----Original Message----- >> From: Linus Casassa [mailto:li...@li...] >> Sent: Thursday, December 04, 2008 10:39 PM >> To: General mailing list for gumstix users. >> Subject: [Gumstix-users] i2c problem >> Hi >> I have the same problem as: >> http://www.nabble.com/verdex-to-robostix-i2c-load-errors-(111-112)- >> td19884751.html#a19884751 >> I have gumstix verdex pro XM4, robostix and netpro-vx. >> How can I fix this? >> Thanks >> ---------- >> Welcome to gumstix! >> For information on how to customize or update this software please >> visit: >> http://www.gumstix.net >> root@gumstix-custom-verdex:~$ i2c-io 0x0b setdir g.3 out >> ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: I2C_IO_SetGPIODir: I2cWriteBlock failed: Connection refused >> (111) >> ERROR: Failed to set dir for G.3 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b setdir g.3 out >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 0 >> ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: I2C_IO_SetGPIO: I2cWriteBlock failed: Connection refused (111) >> ERROR: Failed to set value for G.3 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 0 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 1 >> ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: I2C_IO_SetGPIO: I2cWriteBlock failed: Connection refused (111) >> ERROR: Failed to set value for G.3 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 1 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 0 >> ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: I2C_IO_SetGPIO: I2cWriteBlock failed: Connection refused (111) >> ERROR: Failed to set value for G.3 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 0 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 1 >> ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: I2C_IO_SetGPIO: I2cWriteBlock failed: Connection refused (111) >> ERROR: Failed to set value for G.3 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 1 >> Welcome to gumstix! >> For information on how to customize or update this software please >> visit: >> http://www.gumstix.net >> root@gumstix-custom-verdex:~$ i2c-io 0x0b setdir g.3 out >> ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: I2C_IO_SetGPIODir: I2cWriteBlock failed: Connection refused >> (111) >> ERROR: Failed to set dir for G.3 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b setdir g.3 out >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 0 >> ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: I2C_IO_SetGPIO: I2cWriteBlock failed: Connection refused (111) >> ERROR: Failed to set value for G.3 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 0 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 1 >> ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: I2C_IO_SetGPIO: I2cWriteBlock failed: Connection refused (111) >> ERROR: Failed to set value for G.3 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 1 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 0 >> ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: I2C_IO_SetGPIO: I2cWriteBlock failed: Connection refused (111) >> ERROR: Failed to set value for G.3 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 0 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 1 >> ERROR: I2cTransfer: ioctl failed: Connection refused (111) >> ERROR: I2C_IO_SetGPIO: I2cWriteBlock failed: Connection refused (111) >> ERROR: Failed to set value for G.3 >> root@gumstix-custom-verdex:~$ i2c-io 0x0b set g.3 1 >> root@gumstix-custom-verdex:~$ >> -- >> Linus Casassa >> Estudiante Ingeniería Civil Electrónica >> Fono: 56-9-97776941 >> --------------------------------------------------------------------- >> --------- >> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las >> Vegas, Nevada. >> The future of the web can't happen without you. Join us at MIX09 >> to help >> pave the way to the Next Web now. Learn more and register at >> http://ad.doubleclick.net/clk;208669438;13503038;i?http:// >> 2009.visitmix.com/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> This e-mail transmission and the information contained in this >> communication >> is confidential and may be legally privileged, proprietary >> information >> intended for the individual or entity to whom it is addressed. If >> you have >> received it in error, you are on notice of its status. The >> unauthorized use, >> distribution or disclosure of this communication is strictly >> prohibited. >> Please notify us immediately by reply e-mail and then delete this >> message >> from your system. Thank you for your cooperation. >> --------------------------------------------------------------------- >> --------- >> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las >> Vegas, Nevada. >> The future of the web can't happen without you. Join us at MIX09 >> to help >> pave the way to the Next Web now. Learn more and register at >> http://ad.doubleclick.net/clk;208669438;13503038;i?http:// >> 2009.visitmix.com/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> --------------------------------------------------------------------- >> --------- >> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las >> Vegas, Nevada. >> The future of the web can't happen without you. Join us at MIX09 >> to help >> pave the way to the Next Web now. Learn more and register at >> http://ad.doubleclick.net/clk;208669438;13503038;i?http:// >> 2009.visitmix.com/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> >> -- >> Linus Casassa >> Estudiante Ingeniería Civil Electrónica >> Fono: 56-9-97776941 >> >> >> >> -- >> Linus Casassa >> Estudiante Ingeniería Civil Electrónica >> Fono: 56-9-97776941 >> --------------------------------------------------------------------- >> --------- >> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las >> Vegas, Nevada. >> The future of the web can't happen without you. Join us at MIX09 >> to help >> pave the way to the Next Web now. Learn more and register at >> http://ad.doubleclick.net/clk;208669438;13503038;i?http:// >> 2009.visitmix.com/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> --------------------------------------------------------------------- >> --------- >> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las >> Vegas, Nevada. >> The future of the web can't happen without you. Join us at MIX09 >> to help >> pave the way to the Next Web now. Learn more and register at >> http://ad.doubleclick.net/clk;208669438;13503038;i?http:// >> 2009.visitmix.com/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > > > -- > Linus Casassa > Estudiante Ingeniería Civil Electrónica > Fono: 56-9-97776941 > > ---------------------------------------------------------------------- > -------- > SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, > Nevada. > The future of the web can't happen without you. Join us at MIX09 > to help > pave the way to the Next Web now. Learn more and register at > http://ad.doubleclick.net/clk;208669438;13503038;i?http:// > 2009.visitmix.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |