I have tried to write the small blink.ioioapp, this does not give IOException, it seems to write it, but then hangs, and the app does not start. I upgraded the windows driver to the latest digitally signed version, but no help, same IOException. I think I have damaged app now, because windows does not recognize the IOIO, when in app-mode, but when the bootloader-mode is entered, IOIO is detected. Connection is ok, because the version query always succeeds. How do I recalibrate the IOIO oscillator ?
torstai 30. kesäkuuta 2016 0.08.44 UTC+3 Ytai kirjoitti: > > There is now a signed Windows driver on the downloads page. This will get > rid of the signing warning, but I don't think this is actually the problem. > I've definitely used Windows 10 for IOIO upgrades many times with the old > driver. Is the connection to the IOIO solid? Have you tried recalibrating > the IOIO oscillator? Have you tried writing a different ioioapp file? > > On Wed, Jun 29, 2016 at 11:37 AM, <[email protected] <javascript:>> > wrote: > >> Hello ! >> I just got my latest IOIO board and have to upgrade the firmware. I have >> entered the bootloader mode, and Windows 10 is detecting the board as COM7. >> So the versions I get the following results: >> D:\IOIODude>ioiodude --port=com7 versions >> IOIO Bootloader detected. >> >> Hardware version: SPRK0020 >> Bootloader version: IOIO0400 >> Platform version: IOIO0030 >> >> In the IOIOdude directory I have >> D:\IOIODude>dir >> Volume in drive D is Data1 >> Volume Serial Number is 7092-F163 >> >> Directory of D:\IOIODude >> >> 23.06.2016 06:47 <DIR> . >> 23.06.2016 06:47 <DIR> .. >> 19.08.2014 08:24 168 236 App-IOIO0330.ioioapp >> 14.08.2014 09:25 185 269 App-IOIO0500.ioioapp >> 23.06.2016 06:46 191 319 App-IOIO0506.ioioapp >> 19.08.2014 08:20 1 981 Blink-IOIO0003.ioioapp >> 14.08.2014 09:40 3 358 ioio.inf >> 23.06.2016 06:43 63 ioiodude >> 23.06.2016 06:43 34 ioiodude.bat >> 23.06.2016 06:43 1 122 923 ioiodude.jar >> 8 File(s) 1 673 183 bytes >> 2 Dir(s) 491 300 593 664 bytes free >> >> However when upgrading I get: >> D:\IOIODude>ioiodude --port=com7 write App-IOIO0506.ioioapp >> Comparing fingerprints... >> Fingerprint mismatch. >> Writing image... >> Caught IOException. Exiting.### ] >> >> If I add the --force option the write process just hangs. So what is the >> problem ? Do I have to upgrade the USB driver in W10 ? If I try to upgrade >> the driver using ioio.inf, >> W10 says, that it is not digitally signed. >> Has anybody managed to do this upgrade process using Windows 10 ? >> Ytai, can you test this upgrade process in W10 and possibly update the >> documentation, if something is missing, because we do not have the previous >> windows-versions anymore. >> Thanks for the great product, If I just could get it working again ! >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://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 https://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
