'obj vs. hex file sizes'
I noticed that the same source (.asm) file assemlbed with the older MPASM
from microchip (prior to ByteCraft assembler) that created an .obj file is
different in size than one assembled with the latest version of assembler, that
give .hex files. Both read the same (into MPS16B), and verify the same, just
wondering if the .hex now has some header info, or what ? Anyone know the
answer - not imparative, just curious.
|>I noticed that the same source (.asm) file assemlbed with the older MPASM
>from microchip (prior to ByteCraft assembler) that created an .obj file is
>different in size than one assembled with the latest version of assembler, that
I am only familiar with mpalc for the PIC, but this is a common situation
with object files when moving between assemblers.
The line length (number of data bytes per line) in the Intel hex object
file can vary between assemblers. Since there are 6 bytes of overhead
per line (plus the end of line character(s)), this affects the total bytes.
Also, some assemblers might treat gaps in the code differently, filling them
in some way, but this isn't common.
When I switched assemblers for an Intel micro some years ago I used a
utility to compare the binary results just to be sure that we didn't make
several hundred OTP chips with a bug.
Spehro Pefhany "The Journey is the reward"
Fax:(905) 332-4270 (small micro system devt hw/sw + mfg)
More... (looser matching)
- Last day of these posts
- In 1995
, 1996 only
- New search...