CANedge2 Docs, Release FW 01.04.02
•
PATCH
: Backwards-compatible bug fixes (e.g. no changes to the Configuration File)
The firmware files available for download are zipped with naming as follows:
firmware-[MAJOR].[MINOR].[PATCH].zip
Example:
firmware-01.02.03.zip
0.8.3 Firmware upgrade
The device supports in-the-field firmware upgrades.
Note:
The firmware upgrade process is power safe (tolerates power failures). However, it is recom-
mended to ensure that the process completes
0.8.3.1 Upgrade process
Upgrading initiates when the device is powered and has been prepared with a new Firmware File:
1. Power is applied to device
2. The green LED comes on
3. If the firmware is valid, the green LED blinks 5 times, else the red LED blinks 5 times
4. The green LED remains solid while the firmware is upgraded (~20 sec)
5. If the upgrade succeeds, the green LED blinks 5 times, else the red LED blinks 5 times
6. The upgraded firmware is started
Note:
The green LED comes on later than usual when a firmware upgrade is initiated
Note:
The device automatically removes any Firmware Files (
firmware.bin
or
firmware_wifi.bin
)
when the upgrade has completed. Firmware Files should never be manually deleted during the upgrade
process.
Note:
The CANedge2 upgrades the WiFi related features as a second step of the firmware upgrade
process after the main firmware has started. Allow the CANedge2 a few minutes to complete the second
step of the firmware upgrade. If power is lost during the second step, the device will resume next time
it powers on.
0.8.3.2 Configuration update
If a device is updated to a firmware version with a different
MAJOR
or
MINOR
number, then the Configu-
ration File also needs updating (i.e. with an updated name and structure matching the new firmware).
The Configuration File is named as described in the
section. A default Configuration File
and corresponding Rule Schema are contained in the firmware download zip.
To modify an existing Configuration File, it can be useful to load the new Rule Schema in an edi-
tor together with the old Configuration File. After making the necessary updates, save the modified
Configuration File with a name matching the new version.
0.8. Firmware
61