I messed up with system firmware update

Troubleshooting
1

I apologize for being in a rush to get some work done and I messed up. I have a new Electron that came with 0.5.4. I updated it to 0.6.0 with the Updater app and then tried a particle update to get it up to 0.7.0. As I understand it, I should have gone to 0.6.4 first and then on to 0.7.0. I then tried to downgrade to 0.6.4, but I’m pretty sure I’ve totally messed things up. Can someone please point me in the direction of how to reset the device to an earlier release and then I’ll upgrade to 0.6.4 and on to 0.7.0. I have another Electron that’s likely 0.5.4 as well and I’ll be a bit more careful with it!

Here’s the output from particle serial inspect:

Platform: 10 - Electron
Modules
  Bootloader module #0 - version 11, main location, 16384 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
  System module #1 - version 110, main location, 131072 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      System module #3 - version 110
  System module #2 - version 110, main location, 131072 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      System module #1 - version 110
  System module #3 - version 110, main location, 131072 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
  User module #1 - version 5, main location, 131072 bytes max size
    UUID: 261665F73DC39A9F48865C14ACBFFBACE50C90A571C405CAFC9092CADAFF5D9A
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: FAIL
      System module #2 - version 207
  empty - factory location, 131072 bytes max size

Again, I apologize for rushing and wasting your time. This is embarrassing as I have dozens of devices in the field and usually don’t make this kind of mistake.

2

Never mind. I’m out of trouble. I ran the Particle Firmware Manager for 0.6.0 several times and refreshed Tinker via the iOS app and I appear to be good to go.

I’ll now try to update to 0.6.4 prior to going to 0.7.0

3 Likes