Skip to Content

Changes for page Updating Firmware

Last modified by Alexander Mott on 2026/03/04 22:04
From version 28.19
edited by Alexander Mott
on 2023/12/11 22:56
Change comment: (Autosaved)
To version 39.1
edited by Alexander Mott
on 2026/03/04 22:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Hidden
... ... @@ -1,1 +1,1 @@
1 -true
1 +false
Content
... ... @@ -1,3 +1,11 @@
1 +{{error}}
2 +=== Stepped Firmware Notes ===
3 +
4 +Some devices on older firmware may require "stepping" the firmware by updating to an intermediate firmware before updating to the latest firmware version. Currently installed firmware version can be checked with "**ver**" command, and the PUF version can be checked with "**ver -all**". The below list of devices may not be exhaustive and it is a good idea to check the update notes prior to updating firmware:
5 +//**ZUM-HUB4** //processors must be updated to **PUF version 3.008.054** before being updated to **PUF version 3.009.0039 or newer**.
6 +**//TSW-xx70 //**series touchscreens with** **firmware **below v2.001.0058** must first be updated to firmware **between v2.001.0058 and v2.006.0054** before being upgraded to firmware **v3.000.0110 or newer**
7 +{{/error}}
8 +
1 1  {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 2  {{toc/}}
3 3  {{/box}}
... ... @@ -4,7 +4,7 @@
4 4  
5 5  ShowRunnerCLC™ is tested against the latest Crestron firmware releases, and as such it is recommended to update all device firmware whenever starting up a job. While firmware updates can be performed at any time, it is recommended to update network devices after their network settings have been configured but before loading the ShowRunnerCLC™ program and starting up the job in order to avoid any potential bugs that may result from using outdated firmware. Controlled hardware should be updated once all devices on any given Cresnet/ZUMLINK bus or wireless gateway are online and uniquely addressed. Any communication issues on the bus or gateway should also be resolved prior to updating firmware.
6 6  
7 -Current Crestron firmware can be downloaded from [[Crestron's website>>https://www.crestron.com/Support/Search-Results?c=4]]. Old firmware releases can be downloaded using an SFTP client (such as FileZilla or WinSCP) and connecting to "ftp.crestron.com"
15 +Current Crestron firmware can be downloaded from [[Crestron's website>>https://www.crestron.com/Support/Search-Results?c=4]]. Old firmware releases can be downloaded using an SFTP client (such as FileZilla or WinSCP) and connecting to "ftp.crestron.com" using your Crestron credentials. Current and former firmware releases are sorted by device model in the "firmware" folder of Crestron's FTP server.
8 8  
9 9  = Network Devices =
10 10  
... ... @@ -26,7 +26,7 @@
26 26  
27 27  == Package Update Tool (.puf) ==
28 28  
29 -Crestron's Package Update Tool is the most convenient way of performing firmware updates for devices that use .puf files for firmware. The Package Update Tool can be opened from Toolbox, but doing this will lock Toolbox and only allow updating one device at a time, so we recommend instead that you double-click the .puf file directly. Double-clicking a .puf file will allow you to open multiple instance of the Package Update Tool and enable updating multiple devices simultaneously. Once again, **be careful when updating multiple devices simultaneously not to do anything that would disrupt your connection to a device while transferring the .puf file, nor should you do anything that could result in the device rebooting while it is mid-update**.
37 +Crestron's Package Update Tool is the most convenient way of performing firmware updates for devices that use .puf files for firmware. The Package Update Tool can be opened from Toolbox, but doing this will lock Toolbox and only allow updating one device at a time, so we recommend closing Toolbox (or at least closing any Toolbox connections to devices that you intend to update) and double-clicking the .puf file to open the Package Update Tool in a separate window. Double-clicking a .puf file will allow you to open multiple instance of the Package Update Tool and enable updating multiple devices simultaneously. **Exercise caution when updating firmware for multiple devices simultaneously, as some devices will reboot as part of the update process which may disrupt connection to downstream devices.**
30 30  
31 31  * Locate the firmware .puf file in Windows Explorer
32 32  * Double-click the .puf file to open the Package Update Tool
... ... @@ -35,10 +35,11 @@
35 35  * Verify that the correct .puf and target device are selected
36 36  ** Verify the information under "Package Info" matches what is expected for the desired firmware, and re-select the .puf using the "Select..." button if the information is incorrect
37 37  ** Verify that the information under "Target" matches the device to be updated, and re-select the device using the Address Book or Pencil icon if it is incorrect
38 -[[image:put2.png||height="383" width="412"]]
46 +[[image:put2.png||height="365" width="393"]]
39 39  * Once you have verified all the information is correct and the Package Update Tool has run its check to see that the firmware is compatible with the device, click the "Update" button to begin the update
40 40  [[image:put3.png||height="340" width="366"]]
41 41  * The Package Update Tool will notify you of when it is safe to close, but it is recommended to stay connected if possible in order to verify that the firmware update has been completed successfully
50 +[[image:put4.png||height="336" width="362"]]
42 42  
43 43  == Firmware Update Function ==
44 44  
... ... @@ -58,18 +58,40 @@
58 58  
59 59  Controlled hardware such as Cresnet and infinetEX devices are less frequently updated, but nonetheless will occasionally require firmware updates. ZUMLINK devices should always be updated, but these devices are automatically updated whenever their host ZUMNET device is updated as long as the ZUMLINK device is online and uniquely addressed.
60 60  
61 -== Sub 1 ==
70 +== Network Device Tree View ==
62 62  
63 -Lorem
72 +Updating individual devices can be accomplished in Toolbox using Network Device Tree View, provided that the devices are uniquely addressed and there are no Cresnet wiring or wireless gateway connectivity issues:
64 64  
65 -== Sub 2 ==
74 +* Open Network Device Tree View in Toolbox and connect to the host device (i.e. the processor, DIN-CENCN-2, or gateway) for the devices that need to be updated
75 +[[image:ndtv1.png||height="299" width="416"]]
76 +* Locate the device you want to update and ensure that it is addressed uniquely
77 +** The device should have a yellow "OK" circle icon
78 +** If there is a red "Duplicate Network ID" icon, resolve the duplicate network ID by changing the device address
79 +** If there is a black "Invalid TSID" or "Duplicate TSID" icon, verify that there are no wiring issues on the Cresnet bus and resolve the duplicate/invalid TSID
80 +* Right-click the device to be updated to open the Firmware Update window
81 +[[image:ndtv2.png||height="463" width="415"]]
82 +* Click the "Browse" button on the lower right or the "Verified" checkbox under the "Status" column to open a file selection prompt and select the downloaded firmware .zip file
83 +[[image:ndtv3.png||height="257" width="513"]]
84 +* Once the correct firmware file is selected and the "Verified" checkbox has a checkmark in it, click the "Update" button on the lower right
85 +[[image:ndtv4.png||height="257" width="513"]]
86 +* The progress bar in the "Progress" column should slowly fill up as the firmware update is executed
87 +** The progress bar should read 100% if the firmware update is completed successfully
88 +** If the progress bar does not get to 100% completion and reports failed, you can try again
89 +** If the firmware fails to update multiple times, then it may be necessary to try restarting the host device, isolating the device to be updated, or performing other troubleshooting to ensure that there are no wiring issues or issues with the specific device caused by poor installation, damage during shipping, or factory defects
66 66  
67 -Lorem
91 += Zūm Wired Specific Notes =
68 68  
69 -== Sub 2 ==
93 +Zūm Wired devices are unique among Crestron devices in the fact that the Zūm Link (controlled hardware) device firmware is built into the Zūm Net (networked device) firmware files, and these Zūm Link devices will be updated whenever the host Zūm Net device is updated (with a few caveats mentioned below). While the firmware files for individual Zūm Link devices can be extracted from the "zum-wired_XXX.puf" file using archive tools such as 7-Zip, it is still generally recommended to update Zūm Link firmware using the Package Update Tool whenever possible.
70 70  
71 -Lorem
95 +Caveats for updating Zūm Wired devices:
72 72  
73 -= Zūm Wired Specific Notes =
74 -
75 -Zūm Wired devices are unique among Crestron devices in the fact that the Zūm Link (controlled hardware) device firmware is built into the Zūm Net (networked device) firmware files, and these Zūm Link devices will be updated whenever the host Zūm Net device is updated (with a few caveats mentioned below). While the firmware files for individual Zūm Link devices can be extracted from the "zum-wired_XXX.puf" file using archive tools such as 7-Zip, it is still generally recommended to update Zūm Link firmware using the Package Update Tool
97 +* **All Zūm Link devices must be uniquely addressed**
98 +** Setting the Zūm Net device to primary mode using the command ##zwps primary## will allow it to discover all connected Zūm Link devices
99 +** Setting the Zūm Net device to App/Zūm mode using the command ##zwmode zum## will cause it to reboot and re-address all connected Zūm Link devices
100 +* **All Zūm Link devices should be online before performing firmware updates**
101 +** Ensuring that all devices are online saves time by allowing you to perform the firmware update only once as well as avoids any issues that may be caused by incorrect Zūm Link wiring
102 +** Any Zūm Link wiring issues on a given Zūm Net device must be resolved prior to updating the Zūm Wired firmware
103 +* ZUMNET-JBOX-* devices will reboot as part of the firmware update process; since ZUMNET-JBOX-* devices are typically daisy chained, this means that connectivity with downstream devices will be lost momentarily
104 +** While we have not seen damage to devices as a result of this, it does mean that sometimes the firmware fails to transfer and the firmware update needs to be restarted on the devices where connectivity was lost
105 +* Zūm Link devices can still be updated directly (without updating firmware for the Zūm Net box) using the Network Device Tree View method mentioned above
106 +** Note that the individual Zūm Link firmware will need to be extracted from the "zum-wired_XXX.puf" file in order to load it
ndtv1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +33.1 KB
Content
ndtv2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +56.0 KB
Content
ndtv3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +16.3 KB
Content
ndtv4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +15.4 KB
Content