summaryrefslogtreecommitdiff
path: root/downloader
diff options
context:
space:
mode:
authorChristian Pointner <equinox@spreadspace.org>2013-07-07 00:18:05 +0000
committerChristian Pointner <equinox@spreadspace.org>2013-07-07 00:18:05 +0000
commitff94ea93e254f7ee8c91e42a3a783f5b2262a391 (patch)
tree5279f6e7d3301bc8ac8d4e747acaae7e3fd097b0 /downloader
parentwriting to flash works now (diff)
skipping 'invalid' code doesn't work on some hardware
droping this feature git-svn-id: https://svn.spreadspace.org/pic/trunk@45 a09c6847-51d9-44de-8ef2-e725cf50f3c7
Diffstat (limited to 'downloader')
-rw-r--r--downloader/proto.txt8
1 files changed, 5 insertions, 3 deletions
diff --git a/downloader/proto.txt b/downloader/proto.txt
index f4f32c8..e85368e 100644
--- a/downloader/proto.txt
+++ b/downloader/proto.txt
@@ -60,8 +60,8 @@ identify:
fss:
1byte, flash segment size
The number of words of one flash segment which has to be written at once.
- The downloader can fill up holes by supplying the illegal code word 0xFFFF
- for some addresses. The bootloader will skip those areas.
+ If less than <fss> should be updated the downloader has to perform a read
+ operation first.
mess:
2bytes, maximum eeprom segment size
@@ -133,7 +133,9 @@ write flash:
5 | <ret> | <csum>
The bootloader writes <data> (which has to contain exactly <fss> words) to address
- <addr> inside the flash.
+ <addr> inside the flash. The start address has to be aligned to <fss> boundaries.
+ Before writing the memory region will be erased. If there are words which shouldn't
+ be altered the downloader has to read these words first and reprogram the whole segment.
read eeprom: