At 08:42 AM 3/12/02 +1100, Tony Nixon wrote:

>What about verification??

I suspect there may some confusion regarding this: it may be the same
confusion I initially suffered from.

Wouter said "bootloader", I thought "programmer".  Specifically, ICSP
programmer using only MCLR.  Big difference!  He was accurate in his post,
I was careless in reading it.

Olin's post made it clear to me that this was a bootload technique, not a
general purpose ICSP programmer.  I mean: it can be an ICSP programmer, but
only if the bootload code is loaded first.

As such, I don't think that verification is required.  A CRC or checksum
would be a good idea, as would an error routine that causes the target
system to warn the user that the code transfer did not work correctly.  But
the bootloader itself should be able to take care of verifying that each
location was programmed correctly and to re-try if does not program correctly.

dwayne


Dwayne Reid   <dwayner@planet.eon.net>
Trinity Electronics Systems Ltd    Edmonton, AB, CANADA
(780) 489-3199 voice          (780) 487-6397 fax

Celebrating 18 years of Engineering Innovation (1984 - 2002)
  .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-
     `-'   `-'   `-'   `-'   `-'   `-'   `-'   `-'   `-'
Do NOT send unsolicited commercial email to this email address.
This message neither grants consent to receive unsolicited
commercial email nor is intended to solicit commercial email.

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body