Changes for page Updating Firmware

Last modified by Alexander Mott on 2024/10/15 14:55
From version 35.1
edited by Alexander Mott
on 2024/10/15 14:51
Change comment: There is no comment for this version
To version 5.2
edited by Alexander Mott
on 2023/12/11 20:48
Change comment: (Autosaved)

Summary

Details

Page properties
Hidden
... ... @@ -1,1 +1,1 @@
1 -false
1 +true
Content
... ... @@ -4,9 +4,8 @@
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" using your Crestron credentials. Firmware are sorted by device model in the "firmware" folder of Crestron's FTP server:
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 8  
9 -
10 10  = Network Devices =
11 11  
12 12  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.
... ... @@ -18,82 +18,31 @@
18 18  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.
19 19  
20 20  * Open an SFTP client such as FileZilla or WinSCP (pictured) and connect to the processor at port 22
21 -[[image:sftp1.png||height="309" width="507"]]
20 +[[image:1702319634460-252.png||height="309" width="437"]]
22 22  * Transfer the firmware file to the "firmware" folder on the processor
23 -[[image:sftp2.png||height="307" width="505"]]
24 -* Connect to the processor using Text Console or an SSH client such as PuTTY and run the command ##puf## or ##puf -d##
25 -[[image:sftp3.png||height="307" width="502"]]
26 -* Once the ##puf## command is run, you should see messages appear in the console indicating the status of the firmware update
22 +[[image:1702326885738-296.png||height="308" width="437"]]
23 +* asdf
27 27  
28 28  == Package Update Tool (.puf) ==
29 29  
30 -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.**
27 +Crestron's Package Update Tool is the most convenient way of performing firmware updates for devices that use .puf files for firmware. While the Package Update Tool can be opened from within Crestron Toolbox, we recommend just double-clicking the .puf file to open the tool directly. When updating firmware with the Package Update Tool in Toolbox, the tool will lock Toolbox and only allow updating one device at a time
31 31  
32 -* Locate the firmware .puf file in Windows Explorer
33 -* Double-click the .puf file to open the Package Update Tool
34 -[[image:put1.png||height="386" width="416"]]
35 -* Use the Address Book or the Pencil icon to connect to your processor and wait for it to connect
36 -* Verify that the correct .puf and target device are selected
37 -** 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
38 -** 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
39 -[[image:put2.png||height="365" width="393"]]
40 -* 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
41 -[[image:put3.png||height="340" width="366"]]
42 -* 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
43 -[[image:put4.png||height="336" width="362"]]
29 +== Sub 2 ==
44 44  
45 -== Firmware Update Function ==
31 +Lorem
46 46  
47 -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.
48 -
49 -* 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: 
50 -** Click the Quick Functions lighting bolt icon and select "Firmware..." from the dropdown menu
51 -** At the top of the Toolbox window, navigate to Functions > Firmware... > Firmware...
52 -* Click the "Browse..." button and select the firmware .zip file
53 -[[image:fuf1.png||height="222" width="547"]]
54 -* Click the "Send" button to begin the firmware update
55 -[[image:fuf2.png||height="218" width="540"]]
56 -* The firmware update should be mostly complete once you see the "Please Wait... Rebooting" message disappear
57 -* Click the "Close" button to close the firmware button and run the ##ver## console command to verify the update was successful
58 -
59 59  = Controlled Hardware =
60 60  
61 61  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.
62 62  
63 -== Network Device Tree View ==
37 +== Sub 1 ==
64 64  
65 -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:
39 +Lorem
66 66  
67 -* 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
68 -[[image:ndtv1.png||height="299" width="416"]]
69 -* Locate the device you want to update and ensure that it is addressed uniquely
70 -** The device should have a yellow "OK" circle icon
71 -** If there is a red "Duplicate Network ID" icon, resolve the duplicate network ID by changing the device address
72 -** 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
73 -* Right-click the device to be updated to open the Firmware Update window
74 -[[image:ndtv2.png||height="463" width="415"]]
75 -* 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
76 -[[image:ndtv3.png||height="257" width="513"]]
77 -* Once the correct firmware file is selected and the "Verified" checkbox has a checkmark in it, click the "Update" button on the lower right
78 -[[image:ndtv4.png||height="257" width="513"]]
79 -* The progress bar in the "Progress" column should slowly fill up as the firmware update is executed
80 -** The progress bar should read 100% if the firmware update is completed successfully
81 -** If the progress bar does not get to 100% completion and reports failed, you can try again
82 -** 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
41 +== Sub 2 ==
83 83  
84 -= Zūm Wired Specific Notes =
43 +Lorem
85 85  
86 -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.
45 +== Sub 2 ==
87 87  
88 -Caveats for updating Zūm Wired devices:
89 -
90 -* **All Zūm Link devices must be uniquely addressed**
91 -** 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
92 -** 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
93 -* **All Zūm Link devices should be online before performing firmware updates**
94 -** 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
95 -** Any Zūm Link wiring issues on a given Zūm Net device must be resolved prior to updating the Zūm Wired firmware
96 -* 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
97 -** 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
98 -* 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
99 -** 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
47 +Lorem
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
ndtv2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
ndtv3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -16.3 KB
Content
ndtv4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -15.4 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
1702326885738-296.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +24.9 KB
Content
1702327000173-930.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +24.9 KB
Content
1702327576910-567.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +9.5 KB
Content