Note: This is a Release and may be used for production. Any known issues are likely slated for 0.5.3-rc.1 and 0.6.0-rc.1 releases (check Github issues). It is available by default for all devices. To use, select the 0.5.2 version dropdown from the devices drawer. Please read the note below about downgrading.
Note: Some users previously had last used 0.5.2-rc.1 on Core/Photon/P1 devices. Since this target is no longer available for those devices, please re-flash them with 0.5.2. Pre-release 0.5.2-rc.1 is still available for the Electron since it may be more difficult or costly to upgrade these remote devices. Please do upgrade when you can to 0.5.2, however this is technically the same firmware as 0.5.2-rc.1. As usual, you will have to locally upgrade the Electron system firmware to 0.5.2 first. Electron system version identification has been improved. You should only need to refresh/reload the Build IDE to see the new version.
v0.5.2 Changelog
ENHANCEMENTS
- [Photon/P1] Restores the default WICED country to Japan #1014
Upgrading to this version will now allow you to downgrade remotely OTA to v0.5.0 or earlier without erasing Wi-Fi credentials. There are still some cases where a downgrade will erase credentials, but only if you have explicitly set the country code to something other than the
default
orJP2
. For example, if you set the country code toGB0
orUS4
, if you downgrade to v0.5.0 your Wi-Fi credentials will be erased. Leaving the country code atdefault
or set toJP2
will not erase credentials when downgrading to v0.5.0. Do not downgrade to v0.5.1 first, and then v0.5.0... this will erase credentials in all cases.
BUGFIXES
- .syncTime() and .unsubscribe() called on the system thread. Prevents issues when multiple threads try to send messages through the cloud connection or manage the network state shared memory. #1041
System Binaries (all devices) & Device Upgrader (Photon & Electron)
located below
Particle CLI (easy method)
The easiest way to upgrade to 0.5.2 system firmware, is to use the CLI and run these commands. First upgrade the System firmware, then optionally put Tinker on the device. This requires CLI version 1.15.0 or newer. You can check with particle --version
.
If you have the Particle CLI installed already, you can update it with the following command. Make sure the device is in DFU mode (flashing yellow LED) and run:
sudo npm update -g particle-cli
// Note: you can try without sudo first if you wish
- Make sure the device is in DFU mode and run:
particle update
- Optionally add Tinker as the user firmware instead of an app that you may currently have running on your device. Have the device in DFU mode and run:
particle flash --usb tinker
The OTA method using Particle CLI
For devices already online and connected to the cloud, the system firmware can be updated OTA using these commands:
If your device is online, you can attempt to OTA (Over The Air) update these system parts as well with the particle-cli:
Note: You must download system binaries to a local directory on your machine for this to work. Binaries are attached to the bottom of this release.
Core:
particle flash YOUR_DEVICE_NAME tinker-0.5.2-core.bin
Photon:
particle flash YOUR_DEVICE_NAME system-part1-0.5.2-photon.bin
particle flash YOUR_DEVICE_NAME system-part2-0.5.2-photon.bin
particle flash YOUR_DEVICE_NAME tinker (optional)
P1:
particle flash YOUR_DEVICE_NAME system-part1-0.5.2-p1.bin
particle flash YOUR_DEVICE_NAME system-part2-0.5.2-p1.bin
particle flash YOUR_DEVICE_NAME tinker (optional)
Electron:
particle flash YOUR_DEVICE_NAME system-part1-0.5.2-electron.bin
particle flash YOUR_DEVICE_NAME system-part2-0.5.2-electron.bin
particle flash YOUR_DEVICE_NAME tinker (optional)
The local method over USB using Particle CLI
This requires CLI version 1.15.0 or newer. You can check with particle --version
.
If you have the Particle CLI installed already, make sure it is updated with the following command. Make sure the device is in DFU mode and run:
sudo npm update -g particle-cli
(note: you can try without sudo first if you wish)
Core:
particle flash --usb tinker-0.5.2-core.bin
Photon:
particle flash --usb system-part1-0.5.2-photon.bin
particle flash --usb system-part2-0.5.2-photon.bin
particle flash --usb tinker (optional)
P1:
particle flash --usb system-part1-0.5.2-p1.bin
particle flash --usb system-part2-0.5.2-p1.bin
particle flash --usb tinker (optional)
Electron:
particle flash --usb system-part1-0.5.2-electron.bin
particle flash --usb system-part2-0.5.2-electron.bin
particle flash --usb tinker (optional)
The local DFU-UTIL method
can be applied to offline devices locally over USB using dfu-util
- Put the device in DFU mode (flashing yellow LED)
- open a terminal window, change to the directory where you downloaded the files above, and run these commands:
Core:
dfu-util -d 1d50:607f -a 0 -s 0x8005000:leave -D tinker-0.5.2-core.bin
Photon:
dfu-util -d 2b04:d006 -a 0 -s 0x8020000 -D system-part1-0.5.2-photon.bin
dfu-util -d 2b04:d006 -a 0 -s 0x8060000:leave -D system-part2-0.5.2-photon.bin
P1:
dfu-util -d 2b04:d008 -a 0 -s 0x8020000 -D system-part1-0.5.2-p1.bin
dfu-util -d 2b04:d008 -a 0 -s 0x8060000:leave -D system-part2-0.5.2-p1.bin
Electron:
dfu-util -d 2b04:d00a -a 0 -s 0x8020000 -D system-part1-0.5.2-electron.bin
dfu-util -d 2b04:d00a -a 0 -s 0x8040000 -D system-part2-0.5.2-electron.bin
Debugging for Electron
Instructions on using the Tinker USB Debugging app are here
This is useful for simply capturing the Electron's connection process.
Instructions on using the Electron Troubleshooting app are here
This is useful for interacting with the Electron's connection process.