Thanks - I've attached the device a dozen times, it always shows up as a disabled HID device. The problem is that unless it shows up as a COM port, there is no way to communicate with it from Windows, therefore it cannot be updated.
When the IrToy was new, it showed up as COM3. I could connect to it from a terminal app. But now it's stuck as a disabled HID device and cannot be updated.
I have blown tons of money on Ir Toys in the past month and every single one A) has shipped with old firmware, B) gets stuck in bootloader during an attempted firmware upgrade, C) is now a brick. Search the forums for "stuck in bootloader" or "U2IO flash erasing: FAILED." and you will see this issue has existed for over THREE YEARS and there is no solution. Many people have reported this problem, yet this is no fix, and the assholes at Seeed are still selling this garbage.
So this problem has existed for over three years and there's no damn solution? How nice. I blow $$$ on Ir Toys that SHIP WITH OLD FIRMWARES and then I run into this stupid bootloader hell and can't connect to the hardware to update it. Wonderful ripoff.
I have had the same problem and bricked two brand new IR Toys. Once they go into bootloader, Windows no longer sees them as COM3, so there is no way to connect to them to actually update the firmware. There is no help for this total shit product. Buyer beware. I am so pissed off about this horseshit.
If anyone else has this problem, don't expect a reply. I have had this problem for the past six months and the OP has for over two years. There is no help. I have bricked two brand new Ir Toys because they get stuck in bootloader and once that happens, Windows does not see them as COM3 anymore, so you cannot connect to them to upgrade them. TOTAL SHIT PRODUCT.
Thanks but this does not work. I have shorted PGD and PGC, plugged the USB cable in, ran the fw_update.exe with the args supplied, but all I get is:
U2IO flash erasing: FAILED. Device is not found. Operation aborted.
I have now bricked two IR Toys in a row with this particular issue. It's unbelievable. Are they just going to continue selling flaky hardware or actually fix this issue?
I have two IR Toys that I've attempted to update to v22. Both are stuck in bootloader and will not exit. I've shorted the PGC and PGD over and over again, before plugging the USB in, after plugging the USB in, nothing works. Have I just wasted a chunk of money on bricks?
Thanks, I just gave that a try. But fw_update.exe returns:
U2IO flash erasing: FAILED. Device is not found. Operation aborted.
Correct, I'm on Windows 8.1 - the device appears in Device Manager as a HID that fails to start. I've tried removing/uninstalling/upgrading drivers for about 3 hours last night with no luck.
My orange light is always on. I've shorted the pins but it doesn't make a difference. The device used to show up as COM3 but now it just shows up as a broken HID device. Without a COM port the firmware update doesn't work. The first thing it asks you is "what com port?" so now what?
I have the same exact problem. The orange LED is on, I assume that's the boot loader indicator? Well, the device used to appear as COM2, but now it does not. The docs say "it won't show up as a COM port", well it used to, and the upgrade .bat file asks for the COM port, so what gives? The upgrade reports: U2IO flash erasing: FAILED. Device is not found. Operation aborted. So I guess this is bricked then?
