Re: [Gumstix-users] i2c robostix problem

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Ok, but I have only one robostix and no way to try an other :/

Hummm... What can I do?
Steve can you tell us if there is some problem with some robostix version ?

Thank you!

2009/4/22 mike2323 <mmi...@gm...>

>
> Not sure if it's the best solution, but I wound up ordering two new
> robostix
> boards.
>
> We had a set of boards at an installation that were working fine.  So I had
> them send me one, and it also worked with all of my verdex boards.  To be
> sure, I alternated between my old robostix boards and theirs, and all of
> mine still had the 111 error.  Not sure if the old boards are in some weird
> state, and can be fixed, or if they've got a voltage problem or something.
> Anyway, I had to move on with my project, so I opted to go the new board
> route.  Hope this helps.  I would be interested to see if anyone comes up
> with a better solution as I'd like to be able to use my other boards.
>
>
> batoub wrote:
> >
> > Hi!
> >
> > I have the same problem, I can write the i2c-bootloader but I can't use
> > i2c-load:
> > root@gumstix-custom-verdex:~$ i2c-load 0x0b write i2c-io.hex
> > Detected ATMega128
> > Write:  #ERROR: I2cTransfer: ioctl failed: Connection refused (111)
> > ERROR: BootLoaderWrite: I2cWriteBlock failed: Connection refused (111)
> >
> >
> > Well, have you got a solution?
> >
> > Thank!
> >
> >
> >
> >
> > mike2323 wrote:
> >>
> >>
> >>
> >> Dave Hylands wrote:
> >>>
> >>> Hi Mike,
> >>>
> >>>> Tried using robostix reset pulse. but it didnt' help.  Finally wound
> up
> >>>> putting the etc/init.d/S10robostix script back in, which contains the
> >>>> following, and rebooting.
> >>>>
> >>>>    /sbin/modprobe proc_gpio
> >>>>    echo "AF2 in"  > /proc/gpio/GPIO46
> >>>>    echo "AF1 out" > /proc/gpio/GPIO47
> >>>>    echo "GPIO out clear" > /proc/gpio/GPIO72
> >>>>    echo "GPIO out set" > /proc/gpio/GPIO70
> >>>>    echo "GPIO out set" > /proc/gpio/GPIO73
> >>>>
> >>>> After that, the robostix behaved pretty much as the original robostix
> -
> >>>> no
> >>>> 111 errors on i2c-load 0x0b info, and 111 errors every other time on
> >>>> i2c-io
> >>>> 0x0b info.
> >>>
> >>> The S10robostix script basically turns on the power, and takes the
> >>> robostix out of reset so that it can run whatever program is burned
> >>> into flash.
> >>>
> >>> Also, all of my testing was done with the 400 MHz parts. So it's
> >>> possible that this is some type of timing issue with the u2c bus.
> >>>
> >>> Which version of buildroot/OE are you using?
> >>>
> >>> Buildroot 1545M
> >>> OE 318M
> >>>
> >>>> On the second robostix, I had an odd thing happen.  I left the
> >>>> S10robostix
> >>>> in, and on boot I wound up with a blue flashing light on the robostix.
> >>>> I
> >>>> think I had only run modprobe robostix_drv to get uisp to work after
> >>>> booting
> >>>> before I noticed the light.  From there, I was able to run the
> >>>> rs_reboot
> >>>> script, and have everything behave as on the original robostix with
> >>>> respect
> >>>> to the 111 errors.
> >>>
> >>> The robostix_drv.ko file needs to be loaded for uisp to work (one of
> >>> the things that the robostix driver does is to fake out the parallel
> >>> port API, so that uisp thinks its talking to a parallel port).
> >>>
> >>>> One thing to note, I did experiment with some rmmod's and modprobe's
> on
> >>>> the
> >>>> other drivers (i2c-dev, i2c-core, robostix-drv) prior to attaching the
> >>>> 2nd
> >>>> robostix.  I hope that didn't mess up troubleshooting.  If so, I
> >>>> apologize.
> >>>
> >>> The robostix one shouldn't make any difference. Unloading and
> >>> reloading the i2c ones can sometimes clear up the HW if it gets into a
> >>> weird state. Your problem sounds more like timing.
> >>>
> >>> I'm on my windows laptop right now and don't have access to the source
> >>> code, but you might want to try increasing the i2c timeout.
> >>>
> >>> I'd be glad to give it a try.  Where do I make the change?
> >>>
> >>>> Also, I wasn't sure if the following i2c-pxa output was normal:
> >>>>
> >>>> # modprobe i2c-pxa
> >>>>  : Enabling slave mode
> >>>> I2C: i2c-0: PXA I2C adapter, slave address 1
> >>>>  : Enabling slave mode
> >>>> I2C: i2c-1: PXA I2C adapter, slave address 1
> >>>
> >>> Yeah - the verdex has 2 i2c buses, one is connected to the power
> >>> management chip. i2c-0 is still the one connected to the robostix.
> >>>
> >>> --
> >>> Dave Hylands
> >>> Shuswap, BC, Canada
> >>> http://www.DaveHylands.com/
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> Open Source Business Conference (OSBC), March 24-25, 2009, San
> >>> Francisco, CA
> >>> -OSBC tackles the biggest issue in open source: Open Sourcing the
> >>> Enterprise
> >>> -Strategies to boost innovation and cut costs with open source
> >>> participation
> >>> -Receive a $600 discount off the registration fee with the source code:
> >>> SFAD
> >>> http://p.sf.net/sfu/XcvMzF8H
> >>> _______________________________________________
> >>> gumstix-users mailing list
> >>> gum...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
> >>>
> >>>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/i2c-robostix-problem-tp22003358p23175481.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>