The COM prefix is specific to Windows.
On Apr 26, 2014 11:37 PM, <[email protected]> wrote:

> Problem solved.... COM27 does the trick.... I misread the doc....
>
> ioiodude --port=COM<number> versions
> ioiodude --port=<your_port> --reset write <new_firmware>.ioioapp
>
>
> changing that to the following may be less misleading.... :)
>
> ioiodude --port=COM<number> --reset write <new_firmware>.ioioapp
>
>
> On Saturday, April 26, 2014 11:25:58 PM UTC-7, [email protected] wrote:
>>
>> I tried configuration wipe & the device is into bootloader mode. (yellow
>> LED blinked few time and stop)  I still can't program the firmware because
>> none of the following commands work.
>>
>> c:\fw> ioiodude --port=27 versions
>> c:\fw> ioiodude --port=27 --reset write App-IOIO0500.ioioapp
>>
>> I double checked the port is on 27.  Any other suggestion?
>>
>>
>> On Saturday, April 26, 2014 7:40:49 PM UTC-7, Ytai wrote:
>>>
>>> You shouldn't be able to brick the bootloader even if you install
>>> complete garbage using it. You should try to boot into bootloader mode and
>>> reinstall the firmware. You may need to follow the configuration wipe
>>> procedure. Make sure you use the latest IOIODude.
>>> On Apr 26, 2014 7:26 PM, <[email protected]> wrote:
>>>
>>>> It seems like my problem is fixed when I connected IOIO back to a Win7
>>>> host machine.  My other problem is IOIO got stuck when I execute the
>>>> following command.  Any one else seeing similar problem?  Any suggestion
>>>> would be great because I really want to get the application firmware
>>>> upgrade.
>>>>
>>>> c:\fw> ioiodude --port=27 --reset write App-IOIO0500.ioioapp
>>>>
>>>> thanks,
>>>> -Ken
>>>>
>>>> On Saturday, April 26, 2014 7:01:30 PM UTC-7, [email protected] wrote:
>>>>>
>>>>> I accidentally bricked my IOIO-OTG during the process of upgrading the
>>>>> application firmware.  Everything went well until I used the hex file
>>>>> instead of .ioioapp file.
>>>>>
>>>>> c:\fw> ioiodude --port=27 --reset write SPRK0020.hex
>>>>>
>>>>> My ioio keep blinking since then and won't talk to my android device
>>>>> anymore.  I have another IOIO-OTG, and wondering can the same programmer
>>>>> procedure for IOIO V1 be used on IOIO-OTG?  Or I have to use PICKIT3?  
>>>>> Just
>>>>> want to check before risking my other IOIO-OTG.
>>>>>
>>>>> thanks
>>>>> -Ken
>>>>>
>>>>>
>>>>>
>>>>>  --
>>>> 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.
>

-- 
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.

Reply via email to