Actually, ccs help file says the directive can place comments at the top=20
or bottom of the file.
#HEXCOMMENT text comment for the top of the hex file
#HEXCOMMENT\ text comment for the end of the hex file
The second directive has a backslash in it.

Back to the original issue, how would this be used?  Serializing was=20
mentioned; could it be that a tool reads the address of the serial=20
number address from the comment, generates a number and inserts it at=20
that address?
Curious because I created a software tool to serialize parts, but the=20
address of the serial number was known to the tool, and did not need to=20
be embedded in the hex.
Joe W



On 11/30/2011 12:07 AM, Forrest Christian wrote:
> Yep,
>
> CCS generally puts at least the processor in the file at the end with a
> line like:
>
> ;PIC18F26K20
>
> It also allows you to add additional lines...  they all appear at the
> end, after the EOF mark...
>
>
> On 11/29/2011 9:37 PM, Harold Hallikainen wrote:
>> Interesting concept. Do most hex file readers (including bootloaders)
>> just ignore a line that doesn't start with colon? I typically have a
>> state machine that does not advance until I see the start of line
>> colon in Intel hex. Harold

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