> Oh nice, so the _program_slave argument takes a processor number argument=
 which
>  could indicate that there may be multi slave products in the offing.

Yes, I have noticed that too. But the other interesting thing with the curr=
ent chips is that you appear to be able to have multiple pieces of code tha=
t can be loaded (as noted in the write up) so you could have a separate dia=
gnostic module to the normal run module, assuming you can get it all in the=
 master EEPROM, along with its code.

But what I could also see happening is having a large EEPROM chip, either I=
2C or SPI, connected which has the slave code in it and then a tiny bootloa=
der in the master code that gets loaded into the slave to download the code=
 from the external EEPROM. You could then have multiple tiny bootloaders th=
at use different offsets into the external EEPROM to load different modules=
.. Another possibility with having external EEPROM would be doing code overl=
ays, so you could overlay part of the code for a calibration mode, for exam=
ple.



--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.