Changes between Version 33 and Version 34 of Software/Gateway

Timestamp:

11/26/10 12:04:18 (13 years ago)

Author:

art

Comment:

--

Software/Gateway

@@ -169 +169 @@
 Afterwards an update of the firmware can be initiated by the following protocol:
 
-  * send '''InitFirmwareUpdate''': ''src='f' '', ''dst='i' '' - which will cause server to initiate firmware update. The message must contain in the priority field and both last reserved bytes the 32bit password which is specific to the flashed unit and the firmware. 
-  * receive '''InitFirmwareUpdate''' - wait for max 3sec. until server response with this message indicating that firmware can be now uploaded. 
-  * send '''UploadFirmware''': ''src='f' '', ''dst='u' '':
+  * send '''!InitFirmwareUpdate''': ''src='f' '', ''dst='i' '' - which will cause server to initiate firmware update. The message must contain in the priority field and both last reserved bytes the 32bit password which is specific to the flashed unit and the firmware. 
+  * receive '''!InitFirmwareUpdate''' - wait for max 3sec. until server response with this message indicating that firmware can be now uploaded. 
+  * send '''!UploadFirmware''': ''src='f' '', ''dst='u' '':
      * the len:lenx is a 16bit number indicating the length in bytes of the data (i.e. firmware) following in the data part of the message. 
      * priority field must contain the checksum (16 bit) delivered with the firmware data. 
      * both last reserved bytes in the header must contain the firmware version we are uploading. 
      * The data field of this message must contain the full firmware data which will be directly uploaded to the unit. (will be buffered by the Gateway server)
-  * receive '''UploadFirmware''' - server responses with this message every time when next chunk of bytes has been uploaded to the device. 
+  * receive '''!UploadFirmware''' - server responses with this message every time when next chunk of bytes has been uploaded to the device. 
      * Client application can use the response in order to indicate how much of the data has been already uploaded. 
      * The len:lenx field contains number of bytes already uploaded to the device.