Changes between Version 22 and Version 23 of Stuff/FirmwareUpdate

Timestamp:

11/16/10 22:02:33 (13 years ago)

Author:

art

Comment:

--

Stuff/FirmwareUpdate

@@ -25 +25 @@
 
 '''Programming'''
- * Host application must send an Init-Chunk-Message: FF 0B F0 FA FF 00 vh vl nch s2 s1 ncl chk, where:
+ * Host application must send an Init-Chunk-Message: FF 0A F0 FA FF vh vl nch ncl s2 s1 chk, where:
    * vh:vl - major and minor version numbers of the new firmware
    * nch:ncl - is a 16 bit number indicating number of the firmware chunks
@@ -32 +32 @@
  * OpenBM acknowledge each chunk (incl. init chunk) with a message: F0 07 FF FB cnh cnl s2 s1 chk, where:
    * cnh:chl - last received chunk number.
-   * s2:sl - seed number received in the init chunk "xor"ed with the 16bit sum of the chunk written to the flash
+   * s2:sl - seed number received in the init chunk "xor"ed with the 16bit sum of the chunk data written to the flash
+   * "Init"-chunk is acknowledged by 0 chunk number and the same seed received in the init chunk
 
- * Host application send now firmware chunks. The chunk size should be either 32, 64 or 128 bytes, FF len F0 FA FF cnh cnl c1 c2 .. cn chk, where:
+ * Host application send now data chunks. The chunk size should be either 32, 64 or 128 bytes, FF len F0 FA FF cnh cnl c1 c2 .. cn chk, where:
    * cnh:cnl - number of the chunk, this number should be increasing with every chunk (so no random access here is possible!)
    * c1:cn - chunk of firmware data
@@ -41 +42 @@
 
  * Transmission is stopped when either last chunk was received (bootloader will jump to application) or when a "Stop"-chunk received: FF 06 F0 FA FF FF FF chk
+
+ * OpenBM bootloader indicate that it does not accept any data anymore by sending: F0 04 FF FB eeh eel chk, where:
+   * eeh:eel - 16bit error code: when everything went right, we receive 0=OK, otherwise we receive an error code. Check bootloader documentation for error code definitions
+