From: Linus C. <li...@li...> - 2008-12-05 06:38:42
|
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 |
From: Dave H. <dhy...@gm...> - 2008-12-05 07:25:06
|
Hi Linus, On Thu, Dec 4, 2008 at 10:38 PM, Linus Casassa <li...@li...> wrote: > 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. Is it the exact same problem? i.e. it works for a bit and then stops working? Or is it just not working? Is the robostix running? Are the LEDs flashing? What's the flashing pattern? -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Linus C. <li...@li...> - 2008-12-05 07:39:52
|
Yes, it works for a bit and then stops working and then starts again and stops and so on... All the commands posted are executed in less then a minute. What can it be? 2008/12/5 Dave Hylands <dhy...@gm...>: > Hi Linus, > > On Thu, Dec 4, 2008 at 10:38 PM, Linus Casassa <li...@li...> wrote: >> 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. > > Is it the exact same problem? i.e. it works for a bit and then stops > working? Or is it just not working? > > Is the robostix running? Are the LEDs flashing? What's the flashing pattern? > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > 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 |
From: Dave H. <dhy...@gm...> - 2008-12-05 08:02:35
|
Hi Linus, On Thu, Dec 4, 2008 at 11:39 PM, Linus Casassa <li...@li...> wrote: > Yes, it works for a bit and then stops working and then starts again > and stops and so on... > All the commands posted are executed in less then a minute. > > What can it be? I'm not sure. Is the robostix running? Are the LEDs flashing? What's the flashing pattern? -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Linus C. <li...@li...> - 2008-12-05 08:22:31
|
Thanks Dave. I should try i2c-test to have more information. But I can't find i2c-test for the gumstix on my build. The hex for the robostix is there but the i2c-test for the gumstix isn't. I made a bitbake gumstix-basic-image and a bitbake robostix and installed the ipk robostix*. I have the source files: linus@linus:~/gumstix/gumstix-oe/tmp/work/gumstix-custom-verdex-angstrom-linux-gnueabi/robostix-1.0-r0/robostix/gumstix/i2c-test$ ls Config.h i2c-test.c Makefile svn-version.h But I can't find the exec file. How can I compile it? 2008/12/5 Dave Hylands <dhy...@gm...>: > Hi Linus, > > On Thu, Dec 4, 2008 at 11:39 PM, Linus Casassa <li...@li...> wrote: >> Yes, it works for a bit and then stops working and then starts again >> and stops and so on... >> All the commands posted are executed in less then a minute. >> >> What can it be? > > I'm not sure. > > Is the robostix running? Are the LEDs flashing? What's the flashing pattern? > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > 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 |
From: Steve M. <smc...@sp...> - 2008-12-05 18:00:53
|
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. |
From: David W. <dw...@da...> - 2008-12-06 02:20:32
|
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 |
From: Linus C. <li...@li...> - 2008-12-06 17:49:00
|
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 |
From: Linus C. <li...@li...> - 2008-12-06 18:04:31
|
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 |
From: David W. <dw...@da...> - 2008-12-06 19:06:33
|
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 |
From: Linus C. <li...@li...> - 2008-12-06 19:21:57
|
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 |
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 |
From: Linus C. <li...@li...> - 2008-12-06 20:14:26
|
"One of the 4 voltage regulators provides 500mA to the gumstix and any other connected boards. Some CF cards, combined with the gumstix, require more than 500mA of current. In this situation, both the CF board and the robostix must be powered. The CF board should be powered with a regulated 5v source in this situation." If the net-vx and the gumstix needs more than 500 mA the gumstix will boot or it will reboot or the net-vx will not work but both of them work fine. I will try to power both but I don't think this is the problem. 2008/12/6 David Warman <dw...@da...>: > 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 > > ------------------------------------------------------------------------------ > 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 |
From: David W. <dw...@da...> - 2008-12-06 21:29:32
|
Good luck, let us know. I admittedly was having a different problem and this note fixed mine. I would guess it is a marginal problem, not all systems respond the same way. Power problems are like that - unpredictable when marginal. 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 12:14 PM, Linus Casassa wrote: > "One of the 4 voltage regulators provides 500mA to the gumstix and any > other connected boards. Some CF cards, combined with the gumstix, > require more than 500mA of current. In this situation, both the CF > board and the robostix must be powered. The CF board should be powered > with a regulated 5v source in this situation." > > If the net-vx and the gumstix needs more than 500 mA the gumstix will > boot or it will reboot or the net-vx will not work but both of them > work fine. > > I will try to power both but I don't think this is the problem. > > > 2008/12/6 David Warman <dw...@da...>: >> 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 >> >> --------------------------------------------------------------------- >> --------- >> 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 |
From: Linus C. <li...@li...> - 2008-12-07 00:45:49
|
Powering netpro-vx and robostix at the same time does not solve the i2c problem. This is very frustrating. 2008/12/6 David Warman <dw...@da...>: > Good luck, let us know. I admittedly was having a different problem and this > note fixed mine. I would guess it is a marginal problem, not all systems > respond the same way. Power problems are like that - unpredictable when > marginal. > 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 12:14 PM, Linus Casassa wrote: > > "One of the 4 voltage regulators provides 500mA to the gumstix and any > other connected boards. Some CF cards, combined with the gumstix, > require more than 500mA of current. In this situation, both the CF > board and the robostix must be powered. The CF board should be powered > with a regulated 5v source in this situation." > If the net-vx and the gumstix needs more than 500 mA the gumstix will > boot or it will reboot or the net-vx will not work but both of them > work fine. > I will try to power both but I don't think this is the problem. > > 2008/12/6 David Warman <dw...@da...>: > > 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 > ------------------------------------------------------------------------------ > 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 > > ------------------------------------------------------------------------------ > 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 |
From: David W. <dw...@da...> - 2008-12-07 01:12:20
|
Useful info. Even if negative. Steve, can you tell us how your work-around works? 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 6, 2008, at 4:45 PM, Linus Casassa wrote: > Powering netpro-vx and robostix at the same time does not solve the > i2c problem. > > This is very frustrating. > > 2008/12/6 David Warman <dw...@da...>: >> Good luck, let us know. I admittedly was having a different >> problem and this >> note fixed mine. I would guess it is a marginal problem, not all >> systems >> respond the same way. Power problems are like that - unpredictable >> when >> marginal. >> 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 12:14 PM, Linus Casassa wrote: >> >> "One of the 4 voltage regulators provides 500mA to the gumstix and >> any >> other connected boards. Some CF cards, combined with the gumstix, >> require more than 500mA of current. In this situation, both the CF >> board and the robostix must be powered. The CF board should be >> powered >> with a regulated 5v source in this situation." >> If the net-vx and the gumstix needs more than 500 mA the gumstix will >> boot or it will reboot or the net-vx will not work but both of them >> work fine. >> I will try to power both but I don't think this is the problem. >> >> 2008/12/6 David Warman <dw...@da...>: >> >> 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 >> --------------------------------------------------------------------- >> --------- >> 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 >> >> --------------------------------------------------------------------- >> --------- >> 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 |
From: Linus C. <li...@li...> - 2008-12-07 16:41:54
Attachments:
rayabot_avr-1.0.tar.gz
|
I just made some code communicating the gumstix and the robostix by uart. It only turns on and off the leds. I attached the code. when doing sertest I typed: LED R ON LED R OFF LED B ON LED B OFF LED Y ON LED Y OFF ------ linus@linus:~/rayabot$ tar zxvf rayabot_avr-1.0.tar.gz rayabot_avr-1.0/ rayabot_avr-1.0/Rules.mk rayabot_avr-1.0/rayabot.c rayabot_avr-1.0/Hardware.h rayabot_avr-1.0/Delay.c rayabot_avr-1.0/avr-mem.sh rayabot_avr-1.0/.dep/ rayabot_avr-1.0/.dep/uart.o.d rayabot_avr-1.0/Config.h rayabot_avr-1.0/UART.h rayabot_avr-1.0/CBUF.h rayabot_avr-1.0/Timer.c rayabot_avr-1.0/Makefile rayabot_avr-1.0/Delay.h rayabot_avr-1.0/Hardware.c rayabot_avr-1.0/Timer.h rayabot_avr-1.0/UART.c linus@linus:~/rayabot$ cd rayabot_avr-1.0 linus@linus:~/rayabot/rayabot_avr-1.0$ make Compiling rayabot.c ... Compiling Delay.c ... Compiling Timer.c ... Compiling UART.c ... Compiling Hardware.c ... Linking rayabot.elf ... AVR Memory Usage: ----------------- Device: atmega128 Program: 4562 bytes (3.5% Full) (.text + .data + .bootloader) Data: 771 bytes (18.8% Full) (.data + .bss + .noinit) Creating rayabot.hex ... linus@linus:~/rayabot/rayabot_avr-1.0$ linus@linus:~/rayabot/rayabot_avr-1.0$ scp rayabot.hex root@192.168.10.1: root@192.168.10.1's password: rayabot.hex 100% 13KB 12.6KB/s 00:00 linus@linus:~/rayabot/rayabot_avr-1.0$ ssh root@192.168.10.1 root@192.168.10.1's password: Welcome to gumstix! For information on how to customize or update this software please visit: http://www.gumstix.net root@gumstix-custom-verdex:~$ uisp --erase --upload if=rayabot.hex root@gumstix-custom-verdex:~$ uisp --erase --upload if=rayabot.hex Atmel AVR ATmega128 is found. Erasing device ... Reinitializing device Atmel AVR ATmega128 is found. Uploading: flash root@gumstix-custom-verdex:~$ sertest -p ttyS2 -b 38400 LED_ON( RED ) LED_OFF( RED ) LED_ON( BLUE ) LED_OFF( BLUE ) LED_ON( YELLOW ) LED_OFF( YELLOW ) root@gumstix-custom-verdex:~$ On Sat, Dec 6, 2008 at 10:12 PM, David Warman <dw...@da...> wrote: > Useful info. Even if negative. > Steve, can you tell us how your work-around works? > 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 6, 2008, at 4:45 PM, Linus Casassa wrote: > > Powering netpro-vx and robostix at the same time does not solve the i2c > problem. > This is very frustrating. > 2008/12/6 David Warman <dw...@da...>: > > Good luck, let us know. I admittedly was having a different problem and this > note fixed mine. I would guess it is a marginal problem, not all systems > respond the same way. Power problems are like that - unpredictable when > marginal. > 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 12:14 PM, Linus Casassa wrote: > "One of the 4 voltage regulators provides 500mA to the gumstix and any > other connected boards. Some CF cards, combined with the gumstix, > require more than 500mA of current. In this situation, both the CF > board and the robostix must be powered. The CF board should be powered > with a regulated 5v source in this situation." > If the net-vx and the gumstix needs more than 500 mA the gumstix will > boot or it will reboot or the net-vx will not work but both of them > work fine. > I will try to power both but I don't think this is the problem. > 2008/12/6 David Warman <dw...@da...>: > 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 > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ > 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 > > ------------------------------------------------------------------------------ > 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 |
From: Steve M. <smc...@sp...> - 2008-12-08 17:46:05
|
My work-around is to not use I2C between the verdex and robostix. I transmit data between the them using the serial port (ttyS2 on gumstix). I use uisp to upload new firmware to the robostix, which also uses ttyS2 so you know it is working. Also, for the serial comm, I initially had trouble 115200 baud (and 57600). I got that working by using the atmega128 2x UART mode. This causes the timing to be more correct. To get that working you have to do this when setting up the UART. // enable UART0 UCSR0A |= (1 << U2X0); // Use 2x baud rate UBRR0H = 0 ; UBRR0L = 16 ; // Force 115200 baud rate UCSR0B = (( 1 << RXCIE ) | ( 1 << RXEN ) | ( 1 << TXEN )) ; I do use I2C between the robostix and various sensors with no problems (100khz). This makes me suspect the verdex hardware or its configuration. Steve ________________________________ From: David Warman [mailto:dw...@da...] Sent: Saturday, December 06, 2008 5:12 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] i2c problem Useful info. Even if negative. Steve, can you tell us how your work-around works? Thanks, David Warman Computer Systems Architect dw...@da...<mailto: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 4:45 PM, Linus Casassa wrote: Powering netpro-vx and robostix at the same time does not solve the i2c problem. This is very frustrating. 2008/12/6 David Warman <dw...@da...<mailto:dw...@da...>>: Good luck, let us know. I admittedly was having a different problem and this note fixed mine. I would guess it is a marginal problem, not all systems respond the same way. Power problems are like that - unpredictable when marginal. David Warman Computer Systems Architect dw...@da...<mailto: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 12:14 PM, Linus Casassa wrote: "One of the 4 voltage regulators provides 500mA to the gumstix and any other connected boards. Some CF cards, combined with the gumstix, require more than 500mA of current. In this situation, both the CF board and the robostix must be powered. The CF board should be powered with a regulated 5v source in this situation." If the net-vx and the gumstix needs more than 500 mA the gumstix will boot or it will reboot or the net-vx will not work but both of them work fine. I will try to power both but I don't think this is the problem. 2008/12/6 David Warman <dw...@da...<mailto:dw...@da...>>: 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...<mailto: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...<mailto:dw...@da...>>: Do you have power applied to both the Robostix and the Netpro, 5v each? David Warman Computer Systems Architect dw...@da...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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. |
From: Dave H. <dhy...@gm...> - 2008-12-07 05:29:45
|
Hi Linus, > gumstix: SCL: 1 SDA: 1 > robostix: SCLw: 0 SCLr: 0 SDAw: Z SDAr: 1 DDRD: 1 PIND: 2, PORTD: 0 In this case, SCLw = 0, so the robostix is driving the line low, but the gumstix is reading a 1. > 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 And here the robostix isn't driving the line, and is reading it as a 1 (which is expected), but the gumstix is reading it as a zero, which is incorrect. > 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 Here, the robostix isn't driving SDA, and so it's reading it as 1, which is correct, but the gumstix is reading it as a 0, which is incorrect. > 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. :) It doesn't looks so good. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Linus C. <li...@li...> - 2008-12-07 14:45:25
|
Hi Dave This is how I think it works: When I press the c key the gumstix reads the i2c lines and tells the robostix through uart to change the i2c line status. The robostix changes the line status and returns through uart the new status on the i2c line. So because gumstix reads the old status and robosix returns the new one I have to match the next gumstix line instead of the previous one and that match's fine. 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 Am I wrong? 2008/12/7 Dave Hylands <dhy...@gm...>: > Hi Linus, > >> gumstix: SCL: 1 SDA: 1 >> robostix: SCLw: 0 SCLr: 0 SDAw: Z SDAr: 1 DDRD: 1 PIND: 2, PORTD: 0 > > In this case, SCLw = 0, so the robostix is driving the line low, but > the gumstix is reading a 1. > >> 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 > > And here the robostix isn't driving the line, and is reading it as a 1 > (which is expected), but the gumstix is reading it as a zero, which is > incorrect. > >> 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 > > Here, the robostix isn't driving SDA, and so it's reading it as 1, > which is correct, but the gumstix is reading it as a 0, which is > incorrect. > >> 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. :) > > It doesn't looks so good. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > 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 |
From: Dave H. <dhy...@gm...> - 2008-12-07 18:39:58
|
Hi Linus, > This is how I think it works: > > When I press the c key the gumstix reads the i2c lines and tells the > robostix through uart to change the i2c line status. The robostix > changes the line status and returns through uart the new status on the > i2c line. Yeah - you're right - It's been a while since I used it last. So I re looked at your data and you're right - everything looks good. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Dave H. <dhy...@gm...> - 2008-12-27 16:41:24
|
Hi Sarain, > Anyway I read some comments elsewhere that suggested i2c stability had been > compromised with the switch to OE. It seems that many people using OE are > having robostix/gumstix i2c trouble which lends support to this claim. I > would be willing to start digging into this problem more as both a learning > exercise and a chance to contribute but before I do I want to confirm that > no one has found a solution or even a cause to this/these problems. Also, > are there people out there who can use i2c-io without any trouble. If so > what build system are you using (buildroot or OE) and can you provide any > comments about your setup that might help narrow down the problem we are > facing. I've never experienced any problems under buildroot, but I also haven't used the i2c a huge amount. I'm in the process of trying to get an OE build building. > If anyone has any other recommendations for where in the code/build-system > to start digging I would also appreciate that. The i2c-pxa driver is found on the linux tree under drivers/i2c/i2c-core.c and drivers/i2c/busses/i2c-pxa.c The i2c-dev driver is in drivers/i2c/i2c-dev.c -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: sarain <rai...@co...> - 2008-12-29 13:03:39
|
Hi Dave and everyone else, Thanks for your response. I have done some further troubleshooting on this and have found clues that support both the gumstix and the robostix as the culprit. I doubt they are both at fault and I want to narrow it down even further before I get much deeper in the code. In order to try and rule out the robostix code as the cause could you, or anyone else who is not experiencing this issue, please try my robostix hex files on their unit. http://tinyurl.com/sarain-robostix-i2c-testing These hex files were compiled along with the robostix packages in OE and the code came strait from the repositories. If you try these use uisp, or whatever other programmer you use, to load the i2c-bootloader hex file onto the robostix. Then use the i2c-load program on the gumstix to load the i2c-io.hex file. Once this is loaded run the following a couple times: $ i2c-io 0x0b info See if it ever fails. I have also included my i2c-load and i2c-io ipkg packages compiled for verdex in OE in case anyone is willing to also try these with their system. Please first try loading my hex files with your versions of these. If things work fine then please try it again with my i2c packages one at a time. If it still works fine then that tells me that I need to look at i2c-core, i2c-pxa, or i2c-dev modules. If any of these tests reproduce what myself and others are seeing then we have hopefully narrowed down the offending program. Alternatively, if anyone would be willing to provide me with their known working versions of these hex files and programs I will test them on my system and see if I can still reproduce the errors. I will explain more about my troubleshooting and what I have found so far in the morning/afternoon once I have had some sleep. I just wanted to get this out before I went to bed. Dave Hylands wrote: > > The i2c-pxa driver is found on the linux tree under > drivers/i2c/i2c-core.c and drivers/i2c/busses/i2c-pxa.c > > The i2c-dev driver is in drivers/i2c/i2c-dev.c > Thanks for the paths but they are less meaningfull for OE. I found some directories that followed this structure in an older kernel version folder somewhere in tmp but I don't know if they are the ones being used. Thanks, sarain -- View this message in context: http://www.nabble.com/i2c-problem-tp20848539p21202977.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: sarain <rai...@co...> - 2009-01-03 22:20:00
|
I am finally getting around to documenting the troubleshooting steps I have taken in trying to identify the source of this problem. I became distracted with another project and am just now getting back to this. I have the I2C bootloader installed and the the i2c-io.hex file loaded using it. The first time the "i2c-io 0x0b info" command, or any other i2c-io operation, is run an error is returned. The second i2c-io operation run will be successful. The next will fail, and the one after that will be successful. If at any time you run "robostix reset pulse" to reset the robostix, wait for it to start the i2c-io program (watch the LEDs,) and then run "i2c-io 0x0b info" again it will always fail this first time. Below is the terminal listing of this to help clarify. gumstix-custom-verdex login: root Password: root@gumstix-custom-verdex:~$ i2c-io 0x0b info ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: I2cReadBlock failed ERROR: Unable to retrieve information from i2c address 0x0b root@gumstix-custom-verdex:~$ i2c-io 0x0b info version: 2 minVersion: 1 SVN Revision: 1134 root@gumstix-custom-verdex:~$ i2c-io 0x0b info ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: I2cReadBlock failed ERROR: Unable to retrieve information from i2c address 0x0b root@gumstix-custom-verdex:~$ i2c-io 0x0b info version: 2 minVersion: 1 SVN Revision: 1134 root@gumstix-custom-verdex:~$ i2c-io 0x0b info ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: I2cReadBlock failed ERROR: Unable to retrieve information from i2c address 0x0b root@gumstix-custom-verdex:~$ robostix reset pulse root@gumstix-custom-verdex:~$ i2c-io 0x0b info ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: I2cReadBlock failed ERROR: Unable to retrieve information from i2c address 0x0b root@gumstix-custom-verdex:~$ i2c-io 0x0b info version: 2 minVersion: 1 SVN Revision: 1134 root@gumstix-custom-verdex:~$ i2c-io 0x0b info ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: I2cReadBlock failed ERROR: Unable to retrieve information from i2c address 0x0b root@gumstix-custom-verdex:~$ i2c-io 0x0b info version: 2 minVersion: 1 SVN Revision: 1134 This would seem to imply that the robostix has something to do with the problem since it can reset the cycle of failed and successful operations. I have also tried using the pre-compiled hex files available from: http://docswiki.gumstix.com/Robostix_i2c_bootloader http://docwiki.gumstix.org/Robostix_i2c-io The results are the same. I have run i2c test and both SDA and SCL indicate that the electrical connection is good. I also connected a logic analyzer to the SDA and SCL lines and recorded the traffic. The following is a decoded listing of the i2c traffic for a failed and a successfully executed "i2c-io 0x0b info" command. Failed attempt: 604.01ms START 16 Control Byte: Slave Address B Write ACK 604.14ms START 3 Control Byte: Slave Address 1 Read STOP Successful attempt: 1.73s START 16 Control Byte: Slave Address B Write NACK STOP 1.73s START 16 Control Byte: Slave Address B Write ACK 1 ACK 1.73s START 17 Control Byte: Slave Address B Read ACK 4 ACK 2 ACK 1 ACK 34 ACK 6 ACK B4 NACK STOP The key thing to note is the transaction at 604.14ms. The I2C master (the gumstix) sends another Start condition and the following transaction is interpreted as an attempt to address a device at 0x01. Even though this is interpreted as an attempt to address a different device, the actual digital signals leave out the final clock pulse used to clock in a possible ACK response from the slave device (See the links below for pictures of this.) It obviously wouldn't have gotten a response either way since no device exists on the bus with that address but this violation of the standard is a little strange. This transaction should have been a value of 0x01 sent by the gumstix to the device addressed at 0x0b (the robostix.) This value would have told the robostix to prepare to send back information about the i2c-io program version. Something on the successful attempt that is odd is the failed attempt to address the device at 0x0b (the robostix) on the first try. It takes a second automatic retry to get an ACK response and then works fine for the rest of the transfer. Here are screenshots of the logic analyzer waveforms. The successful attempt is cropped because I wanted to focus on comparing it with the failed attempt. If anyone wants to see the full successful transfer let me know and I will post that as well. Successfull attempt: http://s487.photobucket.com/albums/rr237/sarain_media/?action=view¤t=I2Ctroubleshootingsuccess.jpg http://i487.photobucket.com/albums/rr237/sarain_media/I2Ctroubleshootingsuccess.jpg Failed attempt: http://s487.photobucket.com/albums/rr237/sarain_media/?action=view¤t=I2Ctroubleshootingfailed.jpg http://i487.photobucket.com/albums/rr237/sarain_media/I2Ctroubleshootingfailed.jpg Click on this image to see my annotations. I have been digging into the i2c-io gumstix program's code looking for any common i2c functions that might be a cause of the problem but haven't found any smoking guns yet. I hope the problem is not in the i2c kernel modules since i2c-load usually works fine. If anyone experienced with the i2c driver code would be willing to help direct our efforts I would much appreciate it, and if anyone else has thoughts or suggestions I would love to hear them. Hopefully we can get this problem ironed out without much additional hair pulling. -sarain Linus Casassa-2 wrote: > > 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 > > 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 > ... > -- View this message in context: http://www.nabble.com/i2c-problem-tp20848539p21270138.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Scott H. <sco...@gm...> - 2009-02-10 23:01:04
|
Has anyone gotten the DS1307 drivers working with buildroot 1641? If not, what version of the buildroot should I go back to to make the wiki DS1307 instructions work? Thanks, -Scott |