Right, but when making many hundred boards you really want to find a fully automated way to do this? Using this I can only figure out a way that requires that you put the device in DFU mode 3 times?
I manually place the device in DFU, update it via USB with “particle update” via CLI.
I could then use Bash scripting to flash it via USB. This officially requires that you put the device in DFU mode, but you can make it “jump” straight into programming by issuing a “particle serial flash xxx.bin” command. This will however not successful all the time (maybe 90% of the time?). Here I could supply the wifi credentials and then the software would nee to run a while to do it’s thing (connecting to AWS to register the device and such).
Then I’d need to put it back into DFU mode again to Flash it with it’s final software.
If I had a guarantee that “particle serial flash xxx.bin” would always put it into DFU mode, this could work well, but ever so often it’ll just crash the CLI though, requiring you to kill that window and start up a new session and do it all again. If I manually place the device in DFU mode, it’ll work every time.
Maybe there’s some clever way for my test jig to put the device in DFU mode?