added 'mess' value to identify

git-svn-id: https://svn.spreadspace.org/pic/trunk@29 a09c6847-51d9-44de-8ef2-e725cf50f3c7

1 files changed, 10 insertions, 3 deletions

diff --git a/downloader/proto.txt b/downloader/proto.txt
index 826be5f..5afe572 100644
--- a/downloader/proto.txt
+++ b/downloader/proto.txt
@@ -39,7 +39,7 @@ identify:
     'i' | <csum> (in this case <csum> will always be 'i')
 
   answer:
-    'i' | <ret> | version | name | devid | fss | supported | <csum>
+    'i' | <ret> | version | name | devid | fss | mess | supported | <csum>
 
       version:
          2bytes, protocol version
@@ -61,8 +61,15 @@ identify:
          The downloader can fill up holes by supplying the illegal code word 0xFFFF
          for some addresses. The bootloader will skip those areas.
 
+      mess:
+         2bytes, maximum eeprom segment size
+	 This represents the maximum number of eeprom bytes which may be written at
+         once. Unlike <fss> value it is ok to write less than <mess> bytes. Also
+         this only applies to eeprom writes, reading the eeprom is much faster and
+         therefore not subject to this limitation.
+
       supported:
-         1byte, a bitmap showing supported commands
+         2bytes, a bitmap showing supported commands
          The commands 'identify' and 'boot' are always supported by the bootloader,
          others may not (i.e.: not all PICs allow to update the configurtion words)
 
@@ -151,7 +158,7 @@ write eeprom:
     'E' | <ret> | <csum>
 
   The bootloader writes <data> (which has to contain exactly <len> bytes) to address
-  <addr> inside the eeprom. len is 2bytes long.
+  <addr> inside the eeprom. len is 2bytes long and the value must not exceed <mess> bytes.
 
 
 read config: