Can I ask where you saw that other URL? In the docs? I’ll check as well as we changed this around 2 months ago!
An example of the right file name is taken from the JSON file:
formfactor_dvt - this is fixed, but there other options in there - just ignore them!
select region as RoW or NA (North America)
select the variant of headless or desktop (depending on what you want)
Can you try with the version of software that matches your requirements from that list?
When flashing, I have seen that error before when my USB connection was a little dodgy (specifically when using a USB cable that said it was USB 3 but actually didn’t manage the high speed burst) - the error handling protocol doesn’t like bad cables. I didn’t see the message “use USB 3 for faster flashing” which is why I mention this, but it could be something else.
PS: Thanks again, I was able to reflash the board with this image: particle flash --tachyon ./tachyon-ubuntu-20.04-NA-headless-formfactor_dvt-1.0.162.zip
Subsequently went back to using particle tachyon setup which also completed successfully
However it appears the manufacturing data for this board has now been erased?
After programming OS and config, then cycling power -off/-on, the RGB LED never progresses from flashing green to the expected slow green breathing pattern to show Linux is running.
The cloud console shows no connection with the device.
Could this be due to missing manufacturing info?
I think it might be because the device was flashed with the wrong partition image and it caused some issue. The good news is that its easy to fix this (and restore the provisioning information) - we need to add this information to the developer docs which I’ll get done today, but essentially it requires to flash a manufacturing image that ‘resets’ everything and then we restore the backup Particle made of the provisioning information.
