Proper procedure to flash Electron core firmware to 0.5.0-rc1?

Eventually got there with all electrons within reach of a USB cable - one took 4 or 5 tries though - the ide kept being convinced it was in safe mode and refused to pick up the new on-device firmware revision. Got there eventually, but it concerns me that it was such a rough ride.

If you want to take the data hit, you could flash each system part OTA as you would for the photon, so a USB cable isn’t mandatory, just the way we suggest as the preferred way if suitable.

There are some bumps in the road which we’ll iron out before this moves from beta to final release.

Thanks to everyone for testing and reporting back - this will help us make the final release the best it can be!

I have a problem with the identification of firmware version Web IDE.
I made an update to 0.5.0-rc.2 but the Web IDE displays On the device: 0.4.8.
Through the command particle serial identify is displayed 0.5.0.
For now, I flash locally, but I want to know why this problem occurs
.
I should also like to ask whether in the case of an official version of the new firmware OTA works directly without a local update?

To fix the web ide firmware issue, flash a 0.4.8 code using build ide and it will update to the 5.0

You might also need to perform CLEAR CHACHE if just flashing 0.4.8 code doesn’t update the status.

I tried both ways but without success.
I tried with another browser. Do you have another solution?

I had to flash the device from the Web Build IDE with a new piece of code using the 0.4.8 firmware after doing the firmware update.

Then go back to the WEB Build IDE and refresh the webpage and then go check which firmware it shows is on your device.

Unfortunately, these procedures do not solve the problem.
I will try another browser for example mozila, opera.

This definetly works. I’ve done it that exact way with both my devices and both times (0.4.8 -> 0.5.0-rc.1 -> rc.2)

Just to be sure.

  1. you had 0.5.0-rc.2 already installed on the device?
  2. you built and OTA flashed a 0.4.8 targeted dummy sketch to that device?
  3. your device came back online after the flashing and reported a good flash in the dashboard? (including an app-hash event)
  4. you pressed CLEAR CACHE in the properties drawer of Build?

And you still don’t see ā€œOn the device: 0.5.0-rc.2ā€*

Yes exactly as described. But without success.

That’s very odd :confused:

@suda, any other suggestions?

I upgraded my firmware using the Windows update EXE program.

1 Like

Now I noticed that I did not get event app-hash event.
Only two event started and success.

I guess the 0.4.8 flash didn’t stick

Otherwise it should look like this

OTA flash something like

void setup() { }
void loop() { }

Perform a CLEAR CACHE

Thanks @ScruffR
The problem is probably I did not get app-hash event.
Is there a solution? :confused:

Not getting the app-hash is not a cause but a symptom.
Could you try to flash a blinky sketch or something that makes it possible to tell if your OTA did stick?
Try putting the device in Safe Mode before flashing.
I had issues getting an OTA to stick when using SYSTEM_THREAD(ENABLED) or Blynk on the previous application - there are probably other things causing the same sort of thing.

Hello @ScruffR, @RWB, @x1800MODMY360x.
I managed to solve the problem :smile:
Now explain how.
First I tried installing the old 0.4.8 firmware and then flash 0.5.0-rc.2. The problem in this way exists again.
Then I tried to flash first 0.5.0-rc.1, and then 0.5.0-rc.2 and then the problem is solved.
I too noticed that when using the SYSTEM_THREAD (ENABLED) has a problem with getting the app-hash.

2 Likes

Again I have the same problem with the new firmware 0.5.1.
In Web IDE is shown as 0.5.0 :frowning:
Otherwise by sending ā€œvā€ via serial terminal I get version 0.5.1.
Alternatively I switched to using Particle Dev.
Just as I can see I have no information with which version of firmware Electron works. Whether it is the latest version?

I’ve already pinged Particle about this yesterday and they will look into it next week.
The previous workarounds to update Build to recognize the correct version are confirmed to not work.

particle serial inspect gives you a better picture of what version each module on your device is.
You can flash 0.5.1-rc.2 devices with 0.5.1 firmware since this is basically the same version (#15 via inspect), but only via CLI since Build refuses to OTA ā€œincompatibleā€ versions (not knowing that they in fact are the same).

2 Likes

@MDMA @BDub Do you guys plan on updating the Windows Firmware updater app so we can easily update the firmware to 0.5.2 on the Electron without needing the CLI?

https://github.com/spark/device-updater/releases/tag/v0.0.7