> Now, before everyone starts to hack at this one and spewing out
> (pseude)code, I'm just wondering what the correct procedure (failsafe and
> dummyproof) is to start such a bootload procedure, which options are a
must
> (CRC validation before running the program, load retry, device type
> verification, etc etc).

I would want to make sure that I could update the network at *any* time, so
- the master devices (PICs etc) that make the connection are *not*
updateable
- the updateable devices have a non-updateable bootstrap loader
- the master devices can activate the bootstrap loaders (for instnace by
resetting the other devices)

Wouter van Ooijen
--
Van Ooijen Technische Informatica: http://www.voti.nl
Jal compiler, Wisp programmer, WLoader bootloader, PICs kopen

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