A simple fix for you, switch to gpasm/gplink, the open source
alternative of MPASM/MPLINK. It works on lots of OSes,
including Windows and Linux.
Switch to gpasm and it does not created that useless section.
I find out the 2 bytes difference by comparing the hex
file generated by gpasm/gplink and MPASM/MPLINK.
Craig Franklin is the author of gputils (including gpasm/gplink).
So far I have no problems to assemble/link my MPASM code
However in general, that 2 bytes should not matter.
On 9/23/05, Craig Franklin < firstname.lastname@example.org
>I check the list file and find out they are indeed almost the same.
>The only difference is that the code section starts with 0x07 for
>MPASM/MPLINK and 0x05 for the gpasm/gplink. There is two word
>not used by MPASM/MPLINK, a bit strange. The linker scripts are
>exactly the same.
mplink always reserves space for .cinit even if no initialized data
sections exist. Run mplink with the /m option and you will see it.
gplink only creates the symbol if an initialized section is present.
The lesson here is map files are your friend. If anything looks strange