gnupic: Re: [gnupic] gplink throws away configuration (PIC18F458)
Subject:
Re: [gnupic] gplink throws away configuration (PIC18F458)
From:
Craig Franklin ####@####.####
Date:
19 Dec 2005 21:17:16 +0000
Message-Id: <43A723DC.3080501@users.sourceforge.net>
Ian Jackson wrote:
>I've been using gputils on Debian with a PIC18F458 (and odyssey as the
>programmer). I'm currently using gputils 0.13.3 (actually, Debian's
>0.13.3-1). I'm having some problems with gplink leaving out the
>configuration section from my output .hex files, which confused me for
>a bit before I realised what was happening.
>
>As you can see from the complete transcript below:
> gpasm -p18f458 -c test.asm
> gpasm -p18f458 -c config.asm
> gplink test.o config.o
>produces an a.hex file which doesn't conttain the configuration.
>gpvo config.o suggests that the config.o is right. Using gpasm in
>absolute mode like this works:
> gpasm -p18f458 test.asm
> gpasm -p18f458 config.asm
> ./merge-hex test.hex config.hex >merged.hex
>
>
>
FYI.
In your files you specify the full path to the include. You shouldn't
have to do that. There is a compiled in default path that gpasm always
searches. If you don't like that location, you can change it with the
environmental variables. I added this to my .bashrc:
export GPUTILS_HEADER_PATH="/home/craig/gputils/cvs/gputils/header"
export GPUTILS_LKR_PATH="/home/craig/gputils/cvs/gputils/lkr"
The path being used is reported in the gpasm help.
>merge-hex is a small Perl script I wrote which effectively
>concatenates hex files (but checking for overlaps). I've attached
>that too.
>
>
>
Nice script. Are you distributing it anywhere? If not we should add it
to the gnupic website.
>------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
