You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ert78gb Assume I call the flashing script (update-device-firmware.ts) while specifying the pid (say dongle's). Assume that multiple such devices (dongles) are connected.
How difficult would it be to introduce a new argument (say --flashAll) that would make the flashing script flash all the connected devices of that kind, one by one?
The text was updated successfully, but these errors were encountered:
Very difficult in a reliable way. The USB descriptor has path property that the unique identifier of the device. This value is changing under the firmware upgrade process. So not easy to identify the newly appeared device is a newly connected device or reenumerated after the firmware upgrade process. Logically I could use the device serial number but as far as I know it is 0000000000 in case of dongle.
I think the path-based variant is (definitely) not worth the effort.
If serial number implementation is not too laborous, I would appreciate that - you can assume non-zero serials.
(Am I correct that it currently is possible to flash a hardware config (and thus serial number) onto a dongle manually via the agent script?)
(Usecase: I am now messing with switching between multiple dongles and so this would make the build-flash-test development cycle more comfortable. Of course this is a niche usecase/request...)
@ert78gb Assume I call the flashing script (update-device-firmware.ts) while specifying the pid (say dongle's). Assume that multiple such devices (dongles) are connected.
How difficult would it be to introduce a new argument (say --flashAll) that would make the flashing script flash all the connected devices of that kind, one by one?
The text was updated successfully, but these errors were encountered: