Hmmm.... by "map file" do you mean the .LST file? Taking one of my apps/code as an example, the .LST file shows: Program memory words used: 599 Program memory words free: 1449 Neat. These even add up to 2048, so it sounds plausible, but how come the .HEX file size is 3418 bytes? From archive posts, I gathered that the .HEX file is a little over twice the actual code size, so I'd expect the .HEX file to be about 1200-1300, maybe even 1400-1500 bytes. Why does it come up with 3418 ('ls -al'). There's gotta be a logical answer here somewhere. If the real answer is that the .HEX file is many times the size of the code, and the .LST file shows the correct code size, I would be most ecstatic to save the utility coding time. Cheers, -Neil. ----- Original Message ----- From: "Olin Lathrop" To: Sent: Thursday, March 14, 2002 2:29 PM Subject: Re: [PIC]: Weekend project (Linux Hex-file utility)? > >> > Just figured out my weekend project (if weather is bad)... a .hex > file size-check utility. My intention is to create a Linux command- > line utility that will be given a .hex file, and would spit out the # of > bytes being used on the chip. Should be fairly simple from what > I see of the INHX8M file format. > > However, does a similar util exist yet? I'd hate to reinvent this > wheel, especially since it's been years since I touched C code. > << > > Such a utility would be very easy to write, but you could just look into the > map file for the answer. > > > ******************************************************************** > Olin Lathrop, embedded systems consultant in Littleton Massachusetts > (978) 742-9014, olin@embedinc.com, http://www.embedinc.com > > -- > http://www.piclist.com hint: The list server can filter out subtopics > (like ads or off topics) for you. See http://www.piclist.com/#topics > > > -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics