Searching \ for 'Device-specifics in HEX files?' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/index.htm?key=device+specifics
Search entire site for: 'Device-specifics in HEX files?'.

Truncated match.
PICList Thread
'Device-specifics in HEX files?'
1995\11\09@142549 by Rick Miller

flavicon
face
-----BEGIN PGP SIGNED MESSAGE-----

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

I think Parallax's docs refer to "IHEX8M"...
Where do I get details on this file format?

Rick Miller, Design Engineer  (and local "Internet Guy")
Digalog Systems, Inc.         <spam_OUTrickTakeThisOuTspamdigalogsys.com>
3180 S. 166th St.             <.....Rick.MillerKILLspamspam@spam@Linux.org>
New Berlin, WI  53151  USA    +1 414 797 8000 x-228


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMKJVHmJrU1sdj28/AQHqWgP6AmmepF4rO48WCcUkHu/gtreKCAP+vaCv
v7EsHtL6duRY6wU9jzb3/NIyQ5tHSzdHPyVZgvK//ntHx+lUTxq6SJm3ZsQM6C08
kV72BFqhM0mpLY6OJuevzisPRFK/d4w8xHY+LB8z8XH9JJW+n9NqrG1qoA9U28bO
vb3RUXmURqs=
=Ld1z
-----END PGP SIGNATURE-----

1995\11\09@153212 by Scott Stephens

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

I use MPASM assembly directive, such as "__CONFIG       _CP_OFF & _PWRTE_ON &
_WDT_OFF & _XT_OSC"

>I think Parallax's docs refer to "IHEX8M"...
>Where do I get details on this file format?

The MPASM User's Guide has it in Appendix A. Probably available from Web site.

1995\11\09@162932 by Conny Andersson

flavicon
face
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

1995\11\10@033317 by Newfound Electronics

flavicon
face
Rick Miller wrote:

>Is there a "standard" way to embed PIC16C84-specific info
>(fuses, ID, data-EEPROM) into a "HEX" (or any other) file?
>
>I think Parallax's docs refer to "IHEX8M"...
>Where do I get details on this file format?

signature cut..................

Rick, here is the gospel on this matter.  (sorry for the long response folks
but this is detailed and of interest to (a few?) others.)

There is a microchip standard  defined to embeded fuse, ID data EEPROM. The
details are in the programming specs section of the last two data books. I
admit is a bit terse but all the details are there if you can dig them out.

First,  see the 16C5x programming specs for the general format of the INHX8M
format.  then look at the 16C84 specs for other details.

Regarding defining the fuse ID and data eeprom in you source code, yes this
can be done with the later assemblers BUT, understand the instructions and
syntax are partly defined in a "header file" and not native to the
assembler. So if someone shows you how he has done it, make sure you get his
header file! I have seen at least 3 different syntax forms and I'm sure
there are others. There are standard headers from microchip and perhaps it
best the stick with them.

Now parallax. The parallax assamblers DO NOT ALWAYS produce a standard
microchip INHX8M file format. If you use the fuse and ID instructions native
to PASM and PASMX the resulting hex file IS NOT compatable with picstart or
many other programmers. Oops, Almost forgot, don't use the embedded device
statement either. Sorry, I don't know how you define the device for assembly
purposes with out it being embedded.  - Someone? anyone?....

Maybe you don't as the 16C5x and 16Cxx use different assemblers

However, if you do not use these instructions then the parallax hex format
is compatible with the standard. The parallax data EEPROM is ok to use as it
is compatible. The TRUELY FANTASIC ADVANTAGE of the parallax format is that
you can also define the DEVICE! in the hex file. Now that has to worth a
beer or two!

If there is interest, I shall release as a general utility the "DEMO"
version of my programmer software. This allows exchange from microchip to
parallax hex formats and vise-versa. You can easily  edit everything along
the way. It also handles the data eeprom  as being "ON" "OFF" or "ONLY"  (no
program fuse or ID) If you want to see how it all goes together this is what
you want.

Hope this provides the info you were looking for.  Now I will kill the first
person who asks about checksums!  :-)

Finally, regarding your other message re "cheap programmer doesn't work" How
cheap is something that doesn't work or requires hours to fix??

Every man and his dog is producing programmer designs these days. (mostly
with someone elses work.)

I wish someone independant of all other interests (unlike myself) would do a
review of programmer types, hidden problems, advantages  and their REAL
value for money.  The thread of a logic analyzer will have most of these
programmers hiding under the bed! Well enough of my self serving
rantings...........


Regards,

Jim Robertson


-----------------------------------------------------------------
NEWFOUND ELECTRONICS,  Makers of low cost,
mega featured PIC programming tools.
newfoundspamKILLspamne.com.au
------------------------------------------------------------------

More... (looser matching)
- Last day of these posts
- In 1995 , 1996 only
- Today
- New search...