Yep, I also fail to update firmware on Win11, it just hangs with blue lights, not being able to upload temari.1.2.3 whatever file.
Luckily i had a second laptop with Win10, and it worked there.
[0000079857]+24831 [t:MessageManager] (ViewController.cpp) -> navigating to Progress Dialog
[0000080228]+0371 [t:FW Update Thread] (FirmwareUpdaterService) -> Starting Firmware Update at 17 Apr 2024 1:58:52pm
[0000089321]+9093 [t:FW Update Thread] (NxpRecoveryUtility) -> attempting to open a FileInputStream with temari_XiP_BEE_1_2_3_b50147c.bin
[0000089321]+0000 [t:FW Update Thread] (NxpRecoveryUtility) -> attempting to open a FileOutputStream with temari_XiP_BEE_1_2_3_b50147c_8ffa78352a1f4b2a95b23fd817a79959.bin
[0000079857]+24831 [t:MessageManager] (ViewController.cpp) -> navigating to Progress Dialog
[0000080228]+0371 [t:FW Update Thread] (FirmwareUpdaterService) -> Starting Firmware Update at 17 Apr 2024 1:58:52pm
[0000089321]+9093 [t:FW Update Thread] (NxpRecoveryUtility) -> attempting to open a FileInputStream with temari_XiP_BEE_1_2_3_b50147c.bin
[0000089321]+0000 [t:FW Update Thread] (NxpRecoveryUtility) -> attempting to open a FileOutputStream with temari_XiP_BEE_1_2_3_b50147c_8ffa78352a1f4b2a95b23fd817a79959.bin
[0000108762]+19441 [t:commsEventThread] (Comm.cpp) -> Comm::packetTimedOut with sequence number: 248
Even with latest .608 software, Windows 11 flashing fails.
yep. Yet again had to fallback to Win10 laptop for firmare flashing yesterday.
I'm on Windows 11 and had no problems updating Chordas and Orba (two of each). It took two attempts on one of the Chordas but than one has always been flaky - it usually takes a number of tries just to get it to boot up.
Updating the firmware? It used to work, but since the change in the software it hasn't worked on Win11. The device connects, but something in the firmware process you can see the device disconnects and it never actually flashes. So at least no worries of bricking your device, but no update happens. On Win10, it works perfectly fine, no issues.
This seems like connection or cable issues to me (not saying it is - just that it sounds like it). On my main use laptop the USB C ports have taken a bit of mis-handling and I do get some disconnections due to it. I mostly deal with it by being careful what cables I use and generally being careful. It does seem to me USB C connections are not very robust - especially when they are being used for powering laptops. (And yes - updating the firmware - that's one time when I would be especially careful.)
No isn't a cable issue, it's strictly to do with the update. The software and everything else is working fine with the connection. It sees the device, and gets into firmware mode with all lights, and then it's disconnecting from the computer, you can even hear the windows disconnecting sound.
>>This seems like connection or cable issues to me (not saying it is - just that it sounds like it)
Unfortunately not as easy as that.
Also i tried multiple cables, and one of them works fine for type-c monitor.
Tried all the usb ports, no usb hubs in the middle, and same port are just working fine with all other periphery.
Another one i used for flashing firmwares to Flipper Zero, ESP32 controller and STM32 controller. These guys are really sensitive to the cable quality. And the same cable works on win10.
I might guess that my win11 laptop is much newer usb port standard, something like 3.1 vs 2.0.
Anyway - orba just stays as mounted storage with a firmware file and nothing happens further on win 10.
@Ignis32 Just a thought - could this be to do with the COM ports used? (I don't deal with the sort of other devices you do - perhaps that could be difference?)
Mark Lobo
Anyone on Windows 11 able to flash their Orba 2 firmware? Seems to always disconnect just before.
Able to on Windows 10.