Hey Gino.
Sorry to bother you.
I had the same problem.
when i typed as you did, same ioexception appeared.
D:\IOIOdude>ioiodude --port=COM9 --reset write App-IOIO0400.ioioapp
Caught IOException. Exiting.
I'm wondering where to put the ioioapp file?? in the ioiodude folder?? or 
it will detect automatically??
Thank you.



On Monday, July 15, 2013 9:38:10 PM UTC+9, gino wrote:
>
> Hello,
>
> I have a working IOIO app and a fried IOIO-OTG (just connecting it to 
> power, after about 10 seconds the micricintroller chip is too hot to even 
> touch, not sure how that happened).
> Anyway, I got a new IOIO-OTG that is now not recognized by my app - 
> BaseIOIOLooper.setup() is never called. It is, however, recognized in IOIO 
> hardware app with the following output:
> Android Version: 4.2.1
> IOIO Hardware: SPRK0020
> IOIO Bootloader: IOIO0400
> IOIO Firmware: IOIO0330
>
> Yellow LED can be turned on and off in the app.
>
> If I remember correctly, though the new IOIO does seem to have now the 
> latest bootloader, I had the same problem with the old one and burning a 
> new bootloader solved it.
>
> But I can't burn the bootloader:
> I shortened the boot pin and connected to my PC, disconnected the short, 
> got the flashing LED, installed drivers and then got the following:
>
> D:\IOIOdude>ioiodude --port=COM9 versions
> IOIO Bootloader detected.
>
> Hardware version: SPRK0020
> Bootloader version: IOIO0400
> Platform version: IOIO0030
>
> D:\IOIOdude>ioiodude --port=COM9 --reset write App-IOIO0400.ioioapp
> Caught IOException. Exiting.
>
>
> Why does my app not recognize the phone? Why the IOException?
>
> Thanks,
> Gal
>
>
>
>
>

-- 
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/groups/opt_out.

Reply via email to