OK, so I ended up returning the device to supplier (dx.com) And since the RMA proces was extremely lengthy I decided to buy two new devices in the mean time. They arrived yesterday. This time I bought devices with bluetooth dongle included. They still look exactly the same (white PCB with IOIO otg branding).
This time I did not solder on the pin headers on one board to make sure it was 100% vanilla before testing. This did not matter. So on the last board the ioiodude command did not work at all, however on these two devices it works (shows version numbers) for applications mode but NOT for bootloader mode. When I enable bootloader mode the device starts acting up during enumeration (device shows up in /dev once every 10 times I run ls /dev/IOIO*), and ioiodude hangs indefinitely when trying to list versions. This time I have also tried it on a third laptop (Lenovo T61) to no avail. Also clearing the usb timing did not help (work at all)? There is mention in documentation about a quick flashing yellow light when synchronizing but my board seems only to have a green power led and a red stat led. Also the documentation is really fragmented between v1 and otg models. Before using ioiodude i did the whole ioiomanager app thing first before finally reading in the fine print that it would only work for v1 devices. Could this be the reason why my devices are bricked? I am at loss here. The thought of having to go through dx.com RMA process again sends chills down my spine but I guess I have no choice. -- 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.
