> The resulting hex
> file
> after I compile and assemble is 3.5K. Which might prove interesting
fitting
> into 1K of space unless I have things wrong and it will fit?.

You can't go by the size of the HEX file.  It has much overhead.  The data
itself is stored as hexadecimal ASCII digits, so each byte takes a factor of
2 right there.  Then there is an additional overhead of at least (from
memory, so this may be a little off) 1 colon, 2 length, 4 address, 2 type, 2
checksum, and 2 end of line characters for a total of 13 overhead bytes per
line.

The right way to find the code size is by looking at the load map.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads