Probably because the calibration value is encoded as a MOVLW XX instruction
at the address 0x3FF (I have one here that has 0xC50 there, so my
calibration value is 0x50 and the opcode for MOVLW is the 0xC in the 4 high
bits.) Since the instructions are all 12 bits wide and a HEX file deals with
8-bit values, the instruction is spread over two bytes in the HEX file.

/\/\/\/*=Martin

----- Original Message -----
From: "Mark Skeels" <meskeels@EARTHLINK.NET>
To: <PICLIST@MITVMA.MIT.EDU>
Sent: Tuesday, December 11, 2001 10:30 AM
Subject: [PIC]:programming a 12c509A; configuration word


> Hi, List.
>
> I am building a test fixture for a product we make using a 12C509A. One of
> it's functions is integral programming of the PIC using ISP.
>
> I have got to the point where I am parsing the HEX file generated by MPASM
> and was suprised to find that the configuration word information appears
in
> the second-to-last line in the HEX file, but at address 0xFFE, _not_ 0xFFF
> as I expected.
>
> What am I missing, or can someone explain this to me? The ISP app note for
> the 12C5XX from MChip clearly states that the config word is stored at
> location 0xFFF.
>
> Mark Skeels
> Engineer
> Competition Electronics
> meskeels@earthlink.net
>
> Soli Deo Gloria!
>
> --
> http://www.piclist.com#nomail Going offline? Don't AutoReply us!
> email listserv@mitvma.mit.edu with SET PICList DIGEST in the body
>
>

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