Changes for page Updating Firmware

Last modified by Alexander Mott on 2024/10/15 14:55
From version 21.1
edited by Alexander Mott
on 2023/12/11 21:08
Change comment: Uploaded new attachment "1702328931005-123.png", version {1}
To version 7.1
edited by Alexander Mott
on 2023/12/11 20:57
Change comment: Uploaded new attachment "put1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -17,30 +17,19 @@
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 +[[image:1702319634460-252.png||height="309" width="437"]]
21 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##
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
22 +[[image:1702326885738-296.png||height="308" width="437"]]
23 +* asdf
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**.
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
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 -[[image:put2.png||height="383" width="412"]]
36 -* Verify that the correct .puf file is selected by checking the fields under "Package Info", and re-select the .puf using the "Select..." button if the information is incorrect
37 -* asdf
38 -* asdf
29 +== Sub 2 ==
39 39  
40 -== Quick Function Firmware Updates ==
31 +Lorem
41 41  
42 -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
43 -
44 44  = Controlled Hardware =
45 45  
46 46  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.
1702328931005-123.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 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
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
1702327987072-395.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +9.5 KB
Content