Differences

This shows you the differences between two versions of the page.

--- ccgx:firmware_upgrade_to_v2 [2018-02-12 02:35] – [Troubleshooting] guystewart
+++ ccgx:firmware_upgrade_to_v2 [2021-02-08 22:30] (current) – latest upgrade is 2.18 not 2.11 doc_nl
@@ Line 1: / Line 1: @@
 ====== CCGX: Upgrading to v2 ======
-Updating a CCGX from v1.74 to a newer version requires a one time manual upgrade.
+===== Introduction =====
+Updating a CCGX from v1.74 to a newer version requires a one time manual upgrade. It can’t be done automatically.
-At this moment, the latest available version is v2.11.
+This document explains how to do the manual upgrade.
-This document explains the one time manual upgrade procedure.
+Once upgraded, updates can be installed normally again. Procedure for normal firmware updates is in [[https://www.victronenergy.com/media/pg/2556-GX_Device_Manual_CCGX/en/updating-gx-firmware.html|the Color Control GX Manual]].
-Once upgraded, updates can be installed automatically from the internet again. See [[https://www.victronenergy.com/live/ccgx:firmware_updating|here]] for details.
+===== Upgrade procedure =====
-.
 {{youtube>T-qK9f6FlmU?medium}}
@@ Line 19: / Line 18: @@
 {{ :ccgx:card.png?nolink&200|}}
+  - Get a microSD card. The card needs to be formatted with either a FAT or FAT32 file system. Preferably use a card of 32GB or smaller, as larger cards are often hard to format with mentioned FAT file systems. The upgrade requires less than 150MB on the card.
   - Download [[https://updates.victronenergy.com/feeds/venus/release/images/ccgx/venus-upgrade-image-ccgx.zip|venus-upgrade-image-ccgx.zip]]
   - Above link always points to the latest available version.
-  - Unzip it, and put its contents on a microSD card. The card needs to be formatted with either a FAT or FAT32 file system.
+  - Unzip it, and put its contents on the card.
   - Click ‘Safely remove hardware’ or another eject function on your computer.
   - Take the card out
@@ Line 33: / Line 33: @@
   - So, remove the card, and press buttons A and B again to reboot.
-Upgrade complete already! But make sure to double check a few things:
+Upgrade from 1.x to 2.18 is now complete! But make sure to double check a few things:
   * All settings in the connected devices (Multis, BMV, Solar Charger etcetera) won’t be affected.
   * Also all settings in the ccgx won’t be affected. But still it is good to double check that.
   * Especially double check wifi and/or ethernet passwords and IP configuration.
+  * There are additional versions of VenusOS that have been released since this update image. To finish updating to the latest version, you can now follow the normal [[ccgx:firmware_updating|version 2.x firmware update instructions here. ]]
-For developers and people that customize the ccgx, make sure to [[:ccgx:swupdate-developer-notes|read these developer notes v2.00 and later]].
 ===== Troubleshooting =====
-=== It restart normally and doesn't start the upgrade ===
+=== It reboots but doesn't start the upgrade; instead it does a normal boot ===
-Make sure to hold (!) button E till the upgrade starts
+Solution: Make sure to hold (!) button E till the upgrade starts
 === A blue screen is shown while booting and after ~1 minute, "Starting" is displayed ===
@@ Line 63: / Line 63: @@
 This means that the button pressing procedure was done OK. And the sdcard is properly formatted.
-Possible causes
+Possible causes:
-  - the .swu file is missing on the sdcard. Make sure to unzip all files on the sdcard
-  - there is an another issue with sdcard, try another card, or [[https://updates.victronenergy.com/feeds/venus/release/images/ccgx/|another version]]. Make sure that all files on the card are from the same version, not just the .swu.
-  - the sdcard slot in the CCGX is broken: contact your dealer for a replacement
-===== DISQUS =====
-~~DISQUS~~
+  - the .swu file is missing on the sdcard. Make sure to unzip all files on the sdcard;
+  - the sdcard slot in the CCGX is broken: contact your dealer for a replacement;
+  - A device, mostly a BMV or MPPT, is connected to VE.Direct port 1. Try disconnecting that, and retry. Did that help? Please let us know by posting what happened here below in Disqus.