piclist 1995\11\09\162932a >
Thread: Device-specifics in HEX files?
www.piclist.com/techref/index.htm?key=device+specifics
flavicon
face BY : Conny Andersson email (remove spam text)



At 13.23 1995-11-09 -0600, Rick Miller wrote:

>Is there a "standard" way to embed PIC16C84-specific info
>(fuses, ID, data-EEPROM) into a "HEX" (or any other) file?

It's up to the programmer! ;)

I don't know if there is a standard where to put such info in the hex-file.
You can put whatever you like at whatever position you like but don't expect
the programmer will understand it. The best way to find out is to check the
docs for your programmer.

I know that the DATA I/O programmer likes the configuration bits for 16C54A
at address 204h and the "customer" bits at 205h-208h (is it four bytes? I
don't remember). The configuration bits are of course NOT in the same format
as the usual Microchip defines (_CP_OFF, _WDT_ON etc).

Data-EEPROM should reside at 2100h (64 bytes) but I don't think the
PIC-Start will handle these locations.


-- Conny
<9511092129.AA01502@MIT.EDU>

See also: www.piclist.com/techref/index.htm?key=device+specifics
Reply You must be a member of the piclist mailing list (not only a www.piclist.com member) to post to the piclist. This form requires JavaScript and a browser/email client that can handle form mailto: posts.
Subject (change) Device-specifics in HEX files?

month overview.

new search...