I recently installed 2.1 version of PC (Windows) software and tried to upgrade device firmware to version 1.0.9.
During the firmware upgrade, the info log with “bossac…” command showed and stayed like this for over 10 minutes.
When my patience runs out I tried to do firmware upgrade again with no luck…
Now, the Otii software does not see my device. When I try to upgrade firmware I get:
Upgrading Arc connected to: "COM10"
\"C:/......./bossac\" --port COM10 -i -e .... Arc_1.0.9.bin
The firmware upgrade process failed with status code: 1
No devices suitable for upgrade connected
When I plug/unplug USB from Otii device I get:
Device in firmware upgrade mode removed:
Device in firmware upgrade mode added: "COM10"
When I run bossac command manually I get:
> bossac -p COM10 -i -e -w -v -b -R -U true -u Arc_1.0.9.bin
No device found on COM10
Not quite sure what happened there. Could you please try the following:
Unplug USB.
While pressing the reset button in the small hole on the back, insert USB again
Try firmware upgrade again.
If this does not help, I would advise you to reboot your computer. We’ve had a previous instance where a firmware upgrade scenario got sorted after rebooting Windows.
Thanks for the quick reply.
Pressing the reset button on the device while connecting USB didn’t help. Rebooting Windows did help, partially.
Now, I’ve repeated what happened at the beginning, the complete history is:
How long does it take?..
I’m writing this about 35 minutes later and nothing changed.
In the process manager, I can see that the bossac.exe is on.
Process explorer saying that bossac.exe does not use CPU and I/O at all while otii.exe does ~2% of CPU and 5-16KB of I/O.
In the process monitor, I can see that otii.exe all the time (every ~500ms) is checking some registry values + creating/querying oem106.* files in my windows/** directory…
If nothing comes to your mind that I can try I will try again with windows defender disabled, or with Otti started in admin mode.
We are sorry that you experienced this issue.
From FW 1.1.0 and desktop 2.3.0 this should be fixed so you need to perform your workaround one last time.