Fastboot is really not the recommended way to update devices, and should only be used for development.
Overall I would recommend to do firmware updates (
swiflash …) instead of system updates (
I think this approach is a bit more deterministic as you ‘know’ that the Legato partition that will be on the device is exactly what you’re programming. So if you flash the legato partition and wipe
/mnt/flash, you should have exactly the same thing across devices.
I’m thinking that could potentially use swiflash, on Linux, although I’m not sure that it works well with multiple devices at the moment (I’ve asked if it’s a supported or upcoming feature, stay tuned).
The Windows executable might have an option to select the device id, but I cannot check as I don’t have a Windows host accessible at the moment.
The way I handle the multi-target per host management is quite ‘hardcore’ since I use Xen to make sure that sure that each VM only sees one target, both for USB and networking (so all targets can still have 192.168.2.2 and be connected to the same PC, since they are all connected to one independent VM it’s fine).
However this is the brute-force approach that has the advantage of being compatible with anything, but is not that easy to put in place and manage. I mean, you could try with VirtualBox which also has some USB-passthrough capabilities.