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?)
We bought an Orba 2 and we didn't use it much at the time, because the app didn't work very well with our phones or PC. I was trying to update the firmware now, and it was impossible... Luckily I've read about Windows 10 and I have a laptop that I couldn't update to Windows 11. I can confirm that with Windows 10 it updates on the first try. By the way, the PC and mobile apps still have a lot to improve. I expected more progress in these two years, what a shame.
Yeah sadly the aoftware is okay, the only being able to flash on Windows 10 kinda sucks. Luckily it makes an okay MPE Midi controller.
I don't understand why people are saying they can't flash firmware using Windows 11 - two Orba 2s and Two Chordas all running on different laptops running Windows 11, the only problem has been with one of the laptops which has a damaged usb c port, and that works OK as long as I'm careful to make sure the connection is made and I don't disturb it in the process.
I wonder whether there's some setting that people are using (perhaps for security/privacy?) that causes the issues. Or maybe using USB hubs messes it up? The only other thing that comes to mind is that the process can take time and part of that time it looks as if nothing is happening or that it has done and people don't let the process finish.
>>I don't understand why people are saying they can't flash firmware using Windows 11
Because they can't. *wink*
>>Or maybe using USB hubs messes it up?
No, in my case I connected it directly to every port I could
>> wonder whether there's some setting that people are using
I wonder too, and it is Artiphone's job to ask people for logs, to communicate with us, and dig up the answer, but nobody from Artiphone showed up in a half of year, and probably never would. Probably too busy planing for Chorda 2 or anything else not related to fixing issues.
>> people don't let the process finish.
Once I left it for several hours, I think it should be enough. Otherwise it still an issue
Mark Lobo
Anyone on Windows 11 able to flash their Orba 2 firmware? Seems to always disconnect just before.
Able to on Windows 10.