gnupic: Re: [gnupic] gpasm&gplink with CC5X compiler?
Subject:
Re: [gnupic] gpasm&gplink with CC5X compiler?
From:
Craig Franklin ####@####.####
Date:
26 Mar 2005 01:32:10 +0000
Message-Id: <4244BC8A.3020208@users.sourceforge.net>
Jos van Eijndhoven wrote:
>Hi,
>for quite a while already, I am a happy user of the free version of
>the CC5X C-compiler (see http://www.bknd.com/cc5x/index.shtml) to
>create code for the PIC16F devices. The free version is limited to 1K
>output code words,
>and normally generates directly a downloadable .hex output file.
>
>Currently I am writing a larger program for the PIC16F870 device.
>To use this free C-compiler, I partitioned my program in 2 separate C files.
>These are now compiled to .asm by CC5X, and then to be assembled and
>linked through gpasm and gplink.
>According to the CC5X manual, I updated the '16f870.lkr' device description
>(use an ISR at address 04, reserve RAM locations 0x20 & 0xA0, add a
>few SECTION names).
>
>The separate files compile fine. If I check the generated .asm, I see
>the GLOBAL and EXTERN for the intended variables and functions.
>gplink indeed links without complaints, generating a .lst, a .cod, and a .hex.
>
>[
>Earlier, I got a linker error on a SECTION line as proposed in the CC5X manual:
>SECTION NAME=BANK0 RAM=gpr0
>which I then changed to:
>SECTION NAME=BANK0 RAM=gprnobank0
>as these latter are defined in the 16f870.lkr.
>This removed my earlier link error.
>]
>
>Unfortunately, the .hex created by gplink still doesn't do anything in
>my 16F870: the device stays completely dead :-(
>
>Any clues?
>
>
Have you simulated it?
Have you disassembled the output and verified it is correct?
>Are others using this combination of CC5X (version 3.2) with the gnupic tools?
>Thanks for any insight,
>
>Jos van Eijndhoven
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>
>
