Changes for page Updating Firmware

Last modified by Alexander Mott on 2024/10/15 14:55
From version 29.1
edited by Alexander Mott
on 2023/12/11 23:52
Change comment: Uploaded new attachment "ndtv1.png", version {1}
To version 2.10
edited by Alexander Mott
on 2023/12/11 19:14
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -2,62 +2,27 @@
2 2  {{toc/}}
3 3  {{/box}}
4 4  
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.
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 typically recommended to update network devices after their network settings have been configured (to take advantage of increased file transfer speed over Ethernet compared to USB), but before loading the ShowRunnerCLC™ program and starting up the job (to avoid any potential bugs that may result from using outdated 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"
8 -
9 9  = Network Devices =
10 10  
11 -Networked devices (i.e. devices connected via Ethernet to the LAN or Control Subnet) should always be updated when starting up a job. You can check the current firmware version of most network devices by running the ##ver## command in Text Console or by exporting a Device Summary using the Device Discovery Tool.
9 +Networked devices (i.e. devices connected to the LAN or Control Subnet)
12 12  
13 -While these devices can be updated over USB, it is recommended to update these devices over Ethernet whenever possible in order to take advantage of increased file transfer speed of Ethernet and to enable updating multiple devices at once. Since most network devices will reboot as a part of the firmware update process, **it is important to be mindful of the order in which devices are updated to avoid losing connection to a device while in the middle of a file transfer**. For example, if you have several CEN-GWEXERs that are connected to a CEN-SWPOE-16, it is important to either update the CEN-SWPOE-16 //before// starting the update for any of the CEN-GWEXERs, **or** wait to update the CEN-SWPOE-16 until //after// all of the CEN-GWEXERs are done updating. If you update all devices simultaneously, you risk damage to the CEN-GWEXERs as a result of losing power mid-update due to the CEN-SWPOE-16 rebooting.
11 +== Sub 1 ==
14 14  
15 -== SFTP and SSH (Processors) ==
13 +Lorem
16 16  
17 -Due to the large file size for processor firmware, the most efficient method of updating firmware is to use dedicated third-party SFTP and SSH clients rather than built-in Toolbox functions. This allows for rapidly transferring the large firmware file to the device and then running the update without locking up Toolbox and preventing you from working on other devices while the firmware update is performed.
15 +== Sub 2 ==
18 18  
19 -* Open an SFTP client such as FileZilla or WinSCP (pictured) and connect to the processor at port 22
20 -[[image:sftp1.png||height="309" width="507"]]
21 -* Transfer the firmware file to the "firmware" folder on the processor
22 -[[image:sftp2.png||height="307" width="505"]]
23 -* Connect to the processor using Text Console or an SSH client such as PuTTY and run the command ##puf## or ##puf -d##
24 -[[image:sftp3.png||height="307" width="502"]]
25 -* Once the ##puf## command is run, you should see messages appear in the console indicating the status of the firmware update
17 +Lorem
26 26  
27 -== Package Update Tool (.puf) ==
19 +== Sub 2 ==
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**.
21 +Lorem
30 30  
31 -* Locate the firmware .puf file in Windows Explorer
32 -* Double-click the .puf file to open the Package Update Tool
33 -[[image:put1.png||height="386" width="416"]]
34 -* Use the Address Book or the Pencil icon to connect to your processor and wait for it to connect
35 -* Verify that the correct .puf and target device are selected
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 -** 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="365" width="393"]]
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 -[[image:put3.png||height="340" width="366"]]
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
42 -[[image:put4.png||height="336" width="362"]]
43 -
44 -== Firmware Update Function ==
45 -
46 -While most networked devices will use .puf files for firmware updates, some devices (such as DIN-DALI-2) will use .zip files. In these instances, the Package Update Tool will not work to update the firmware and you must instead use the "Functions..." menu to select and load the firmware.
47 -
48 -* Connect to the device to be updated in Toolbox using a tool such as Text Console and open the Firmware dialog using one of the methods below: 
49 -** Click the Quick Functions lighting bolt icon and select "Firmware..." from the dropdown menu
50 -** At the top of the Toolbox window, navigate to Functions > Firmware... > Firmware...
51 -* Click the "Browse..." button and select the firmware .zip file
52 -[[image:fuf1.png||height="222" width="547"]]
53 -* Click the "Send" button to begin the firmware update
54 -[[image:fuf2.png||height="218" width="540"]]
55 -* The firmware update should be mostly complete once you see the "Please Wait... Rebooting" message disappear
56 -* Click the "Close" button to close the firmware button and run the ##ver## console command to verify the update was successful
57 -
58 58  = Controlled Hardware =
59 59  
60 -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.
25 +Lorem
61 61  
62 62  == Sub 1 ==
63 63  
... ... @@ -70,20 +70,3 @@
70 70  == Sub 2 ==
71 71  
72 72  Lorem
73 -
74 -= Zūm Wired Specific Notes =
75 -
76 -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.
77 -
78 -Caveats for updating Zūm Wired devices:
79 -
80 -* **All Zūm Link devices must be uniquely addressed**
81 -** 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
82 -** 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
83 -* **All Zūm Link devices should be online before performing firmware updates**
84 -** 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
85 -** Any Zūm Link wiring issues on a given Zūm Net device must be resolved prior to updating the Zūm Wired firmware
86 -* 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
87 -** 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
88 -* 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
89 -** 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
1702330126400-306.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
fuf1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -6.7 KB
Content
fuf2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -9.9 KB
Content
ndtv1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -33.1 KB
Content
put1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
put2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -12.4 KB
Content
put3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
put4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
sftp1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -44.9 KB
Content
sftp2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -32.6 KB
Content
sftp3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -23.4 KB
Content
1702319634460-252.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +12.4 KB
Content