1. I stand corrected.
2. Compared to using a 16 bit file format it is. (I think so anyway!)

> -----Original Message-----
> From: pic microcontroller discussion list
> [mailto:PICLIST@mitvma.mit.edu] On Behalf Of Byron A Jeff
> Sent: 06 March 2002 16:30
> To: PICLIST@mitvma.mit.edu
> Subject: Re: [PIC]: Can't locate EEPROM?
>
>
> On Wed, Mar 06, 2002 at 04:11:34PM -0000, Kevin Blain wrote:
> > Generally speaking however, the hex file produced by mplab
> for example
> > located the EEPROM data at org 0x2100, for programming
> purposes. This
> > won't appear in the program memory window, but it will be
> in the hex
> > file. The PIC when in programming mode knows this is
> actually for the
> > EEPROM bit.
>
> Not exactly. The PIC programmer knows that it belongs the the
> data EEPROM and will send 'program data EEPROM' instructions
> instead of 'program program Flash' instructions. The PIC
> itself will not respond to an address of 0x2100 in
> programming mode under any circumstances.
>
> >
> > Because of the obfuscated method which the hex file is stored, this
> > will appear at 4200 (2100 x 2) in the hex file, with every
> other byte
> > being EEPROM data.
>
> Not obfuscated. The hex file stores byte addresses. PIC
> instructions take 2 bytes.  Therefore the addresses in the
> hex file must be double the addresses in the PIC assembly listing.
>
> BAJ
>
> --
> http://www.piclist.com#nomail Going offline? Don't AutoReply
> us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body
>
>
>
>
> *****************************************************************
> This email has been checked by the altohiway e-Sweeper Service
> *****************************************************************
>
>

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