Differences

This shows you the differences between two versions of the page.

--- en:sw:04-unipi-firmware [2020/05/22 11:31]
tomhora
+++ en:sw:04-unipi-firmware [2020/05/26 06:40]
tomhora ↷ Links adapted because of a move operation
@@ Line 8: / Line 8: @@
 <WRAP center round info 90%>
-Currently, the packages are supported only for all controllers except Unipi 1.1 and Unipi 1.1. lite - those should be [[en:sw:02-sdks:01-evok|installed as described here.]]
+Currently, the packages are supported only for all controllers except Unipi 1.1 and Unipi 1.1. lite - those should be [[en:sw:02-apis:01-evok|installed as described here.]]
 </WRAP>
@@ Line 23: / Line 23: @@
 ===== Application interfaces =====
-Available APIs are described in the [[en:sw:02-sdks:01-evok|SDK section]].
+Available APIs are described in the [[en:sw:02-apis:01-evok|SDK section]].
 ===== Firmware =====
@@ Line 66: / Line 66: @@
   * 2.a - Using SCP
       * Copy if from your PC to the unit using SCP (a WinSCP, Filezilla or other software can be used) to the /tmp/ folder
-      * Install the package using dpkg, for example <code>dpkg -i /tmp/unipi-firmware_5.32_all.deb</code>
+      * Install the package using dpkg, for example <code>dpkg -i /tmp/unipi-firmware_5.50_all.deb</code>
   * 2.b - Via USB flash
       * Copy the downloaded file from your PC to the root of the FAT32 formated USB flash and insert the USB flash to any USB port of the unit.
@@ Line 73: / Line 73: @@
       * Create a mount folder for the disk <code>mkdir /media/usbflash</code>
       * Mount the disk to the newly created folder <code>mount /dev/sda /media/usbflash</code>
-      * Install the package using dpkg, for example <code>dpkg -i /media/usbflash/unipi-firmware_5.32_all.deb</code>
+      * Install the package using dpkg, for example <code>dpkg -i /media/usbflash/unipi-firmware_5.50_all.deb</code>
   * 3. Check the current FW version installed in the HW <code>/opt/unipi/tools/fwspi -i 0</code>
   * 4. Update to the latest obtained FW version <code>/opt/unipi/tools/fwspi -i 0 -P</code>
@@ Line 83: / Line 83: @@
 === Upgrading firmware in RS485 Modbus extensions ===
-xS/xG series extensions can be upgraded similarly. Instead of **fwspi** utility, just use the alternative named **fwserial** which is also included in the //unipi-firmware-tools// package (installed automatically with //unipi-firmware//). The command-line arguments are very similar as for the fwspi, except RS485 port specification.
+xS/xG series extensions can be upgraded similarly. Instead of **fwspi** utility, just use the alternative named **fwserial** which is also included in the //unipi-firmware-tools// package (installed automatically with //unipi-firmware//). The command-line arguments are very similar as for the fwspi, except serial port specification.
-<WRAP center round info 60%>
+<WRAP center round alert 80%>
-The -p (path) parameter must be set according to the RS485 used for the extension. See section [[en:hw:01-axon:portmap|]] to resolve the appropriate path for each RS485 available within your unit. For example, if extension is connected to //RS485-1/RS485-1.1//: <code>/opt/unipi/tools/fwserial -p /dev/ttyNS0 -P </code>.
+Make sure that there is no other application using/communicating on the used port and do not disconnect power to the Controller or Extension. Any of this will lead to bricking the extension.
+</WRAP>
+<WRAP center round info 80%>
+The -p (path) parameter must be set according to the used serial for the extension - see the [[en:hw:01-axon:portmap|]] or [[en:hw:02-neuron:portmap|]]to find proper serial port within your unit. For example, if extension is connected to //RS485-1/RS485-1.1//: <code>/opt/unipi/tools/fwserial -p /dev/ttyNS0 -P </code>.
 Note that the fwserial assumes that extension‘s Modbus address, baud rate and parity are in the factory-default state, ie **19200 baud 8N1 with address 15**.
 </WRAP>