Batch file issue

[ha1vorsen]

I've read every issue on the project created thus far. Making sure that the cable wouldn't become detached during flashing, I ran the flash.bat while a genuine SX Lite was connected to my PC.

This is the output of the batch file.

Spacecraft-NX DFU found!
Flashing bootloader updater.........................................................................................................................................................................
Waiting for the updater to boot...
Backing up the current bootloader.
................................................................................................................................................................................................
Flashing the new bootloader.
...............................................................................................................................................................................
timeout: invalid time interval '/t'
Try 'timeout --help' for more information.
Spacecraft-NX DFU not found!
!!!DONE!!!
Press any key to continue . . .

I've used three fully separate PCs and three fully separate microUSB cables, they all yield the same result with the same output.
As mentioned in the title, the chip now has a permanent white LED, even after booting to Horizon.

[ha1vorsen]

This is an issue with the timeout call in the batch file.
After running the commands manually outside of the batch file, I see that my chip has entered the training mode, and it functions normally.

All of my devices are running Windows 11. Is it possible that they changed the functionality of timeout at all? Since it's only two operations, why not have the user run these commands manually as a troubleshooting step?