I’m currently experimenting with the Essentials kit, which includes seven modules that require updates whenever the firmware or drivers are modified.
I’ve been using the DUELink programmer to perform these updates.
However, the programmer has specific requirements: the target module must be positioned adjacent to the tethering adapter, and another module must be connected downstream of the target module.
I have all seven modules connected in a chain and mounted on a holeyboard.
Updating the entire chain involves a lengthy sequence of unscrewing, screwing, unplugging, and plugging actions, which can take anywhere from twenty to thirty minutes.
Apart from the time-consuming nature of the process, the repeated plugging and unplugging must be detrimental to the connectors and cables.
I understand that we are currently in the pre-release phase of DUELink development, and post-release, the release cycles will likely be significantly longer. Nevertheless, it would be beneficial to develop a more efficient and automated method for updating a chain of modules.
Have I missed something? Has anyone got a better workflow for updating?
You are 100% right. There are 2 sides to this, driver update and firmware update:
For driver update, this is already supported in the firmware today. We only need to add a drop down list option to the console so you can select what device in the chain you want to update the firmware for. This window will have the option to set the device number. We should have this in a few days after the holidays.
What I would like to see however is “update all” feature that goes through all modules in the chain and update all drivers. This will come next.
Now, for firmware update, we have had this on the to do list for a year! Originally DUELink modules had boot loaders and almost has “chain update” done but then we changed the system to use the ST loader, for many reasons that I won’t get into now. The loader is mostly used via DFU (over USB) but it also supports other busses. In short, yes it can be done and we need it but this is not an easy one. I opened a public issue about this on github just now Firmware update for chains · Issue #99 · ghi-electronics/duelink-console · GitHub The good news is that we are done with all major work and this is on the top of the list now.
Actually, the requirement today is you can have only one module connected to USB. If your module does not have USB connectors (all modules in essential kit don’t) you will need a USB adapter, which is USB Hook in your kit.
