This is the second time I hear about a similar problem with OpenSuse. Let's focus on the Windows, since this is a known working config. Is the IOIO enumerating correctly there. Are you using the latest IOIODude? On May 5, 2014 7:45 AM, "Urs Weder" <[email protected]> wrote:
> Hello all, > I want to update my IOIO with the most recent firmware but nothing seems > to work as it should: > > The first problem: > ./ioiodude --port=/dev/IOIO0 versions mostly just hangs and doesn't > return anything. If ioiodude returns something than it can take up to 3 > seconds. > > Output (after several tries): > IOIO Application detected. > Hardware version: SPRK0020 > Bootloader version: IOIO0400 > Application version: IOIO0330 > > The second problem: > When starting in bootloader mode, the IOIO doesn't enumerate, i.e. > lsusbdoesn't list the connected IOIO. > > For these tests i used: > Two different computers (openSuse and Win7 Prof) > Two different IOIO OTG (both have the same versions) > And two different cables, just to make sure. > > > Greetings, Urs > > -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/ioio-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
