I am still not convicted whether this upgrade process really works. I connect the board to PC with bootloader pin connected. When it is disconnected the PC (Win7) immediately detects the device. I can check the bootloader version (IOIO0400) using IOIODude. So the bootloader works and is not damaged. I then write the firmware using IOIODude --port=COM20 --force write App-IOIO0500.ioioapp this seems to work ok. I then disconnect and reconnect the IOIO without bootloader pin connected (to find out what version of firmware I have), but the PC cannot connect to device anymore ! (to test HelloIOIOConsole). And of course Android cannot connect to the IOIO. The same is true, if I write the original V3 firmware back. PC and Android cannot connect to it. Are those *.ioioapp files damaged ? They are downloaded from IOIO download site.
I have two new IOIO V3 boards (I wish that they would have come V5 installed !) that are working with Android, I cannot take the risk of upgrading them, before being absolutely sure that the new firmware works. It takes two weeks (and costs money) to get new IOIO boards from China. tiistai, 9. syyskuuta 2014 22.48.11 UTC+3 Ytai kirjoitti: > > The firmware upgrade process cannot cause any electrical damage, nor can > it cause the bootloader to go bad. > I would start by upgrading the IOIO firmware to the latest version and > convince yourself that it works OK by running it against HelloIOIOConsole > running on a PC. > If your VREG is indeed fried, your 5V bypass should solve the problem. > Please use a voltmeter to verify that you indeed have 5V on the 5V rail > with / without the Android connected. > > > -- 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.
