Changes for page Updating Firmware

Last modified by Alexander Mott on 2024/10/15 14:55
From version 12.1
edited by Alexander Mott
on 2023/12/11 20:58
Change comment: Deleted image "1702319634460-252.png"
To version 28.17
edited by Alexander Mott
on 2023/12/11 22:46
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -17,8 +17,11 @@
17 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.
18 18  
19 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"]]
20 20  * Transfer the firmware file to the "firmware" folder on the processor
21 -* Connect to the processor using Text Console or an SSH client such as PuTTY and run the command ##puf##
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"]]
22 22  * Once the ##puf## command is run, you should see messages appear in the console indicating the status of the firmware update
23 23  
24 24  == Package Update Tool (.puf) ==
... ... @@ -27,15 +27,30 @@
27 27  
28 28  * Locate the firmware .puf file in Windows Explorer
29 29  * Double-click the .puf file to open the Package Update Tool
33 +[[image:put1.png||height="386" width="416"]]
30 30  * Use the Address Book or the Pencil icon to connect to your processor and wait for it to connect
31 -* asdf
32 -* asdf
33 -* asdf
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="383" width="412"]]
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
34 34  
35 -== Quick Function Firmware Updates ==
43 +== Firmware Update Function ==
36 36  
37 -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, there is no way to use the
45 +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.
38 38  
47 +* 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: 
48 +** Click the Quick Functions lighting bolt icon and select "Firmware..." from the dropdown menu
49 +** At the top of the Toolbox window, navigate to Functions > Firmware... > Firmware...
50 +* Click the "Browse..." button and select the firmware .zip file
51 +[[image:fuf1.png||height="222" width="547"]]
52 +* Click the "Send" button to begin the firmware update
53 +[[image:fuf2.png||height="218" width="540"]]
54 +* The firmware update should be mostly complete once you see the "Please Wait... Rebooting" message disappear
55 +* Click the "Close" button to close the firmware button and run the ##ver## console command to verify the update was successful
56 +
39 39  = Controlled Hardware =
40 40  
41 41  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.
... ... @@ -51,3 +51,7 @@
51 51  == Sub 2 ==
52 52  
53 53  Lorem
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
1702327000173-930.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -24.9 KB
Content
1702330126400-306.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +11.7 KB
Content
fuf1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +6.7 KB
Content
fuf2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +9.9 KB
Content
put2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +12.4 KB
Content
put3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +11.7 KB
Content
put4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +11.7 KB
Content
sftp1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +44.9 KB
Content
sftp2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +32.6 KB
Content
sftp3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +23.4 KB
Content