-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> My design rule of thumb is "Simulate what you can, Emulate what you
> cannot."

By the above maxim, the design that I proposed is more appropriate.
The bootloader proposition takes the design one step beyond
emulation.

The rule should read:  "Simulate what you can, Emulate what you can
but cannot simulate, and Hard program what you cannot emulate."

You've skipped the second part, IMHO.

> That's one of the reasons I absolutely love the current version of
> gpsim. It allows you to load virtual hardware modules (LCD, LED,
> serial) that you can interact with during simulation without having
> any real hardware at all. You can program with the simulator as the
> target. The Designer extends this model into hardware allowing the
> designer to utilize all of the onboard hardware for project
> development. Again it's the target, not a programmer for the
> target. Only once the project is fully realized does an actual
> target chip on an actual target board need to be programmed. And if
> the design is correct this step will have a very small cycle
> interval.

- --Brendan

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>

iQA/AwUBPVQHygVk8xtQuK+BEQLybgCfQKnVlbh18ntTWLEAqrrv0rhPOKIAn3Gc
rC3Jrxi7WZ/jyjF3HuVUVv2N
=9/C1
-----END PGP SIGNATURE-----

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu