Philip Pemberton wrote:
> Just out of curiosity, is there any way you could add an optional
> command to the spec that returns, say, a string that identifies the
> programmer. For instance, an Easyprog might return "Easyprog", a Wisp
> might return "WispE648" - you get the idea. Just a thought :)

I didn't want to burden small implementations with having to cough up an
ASCII string.  The FWINFO2 command is intended to serve that purpose
instead.  This gives each organization that creates firmware its own 8 bit
namespace.  Your organization ID is 2, which means your firmware must return
2 in the ORG byte of the FWINFO command response.  You then get to define
the FWINFO2 value any way you like.

I guess I need to come up with a general means for other oganizations to
supply text names for their FWINFO2 values.  I'll probably do this by
defining a unique environment file for each organization ID.  Right now I'm
trying to make my software support spec version 10.

I definitely appreciate the feedback.  You are the first "outside"
organization creating firmware compatible with the programmer protocol spec,
so some of these issues haven't been woked out completely yet.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com
_______________________________________________
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist