gnupic: Re: [gnupic] gpasm&gplink with CC5X compiler?
Subject:
Re: [gnupic] gpasm&gplink with CC5X compiler?
From:
Jos van Eijndhoven ####@####.####
Date:
28 Mar 2005 00:28:47 +0100
Message-Id: <81d6653805032715283f3c0586@mail.gmail.com>
Hi,
I spent more time in studying .asm and .lst files....
After a long while I realised that there was no error in the program,
nor in the tooling...!!!!
There was an unreliability in my hardware, which happened to pop-up just at
the moment that I started using the gnupic tools $#@^%$#&*^.
My setup with CC5X separate C-compilation, and gpasm + gplink for
assembling and linking the files, works great now! (well.... sorry
that CC5X is a windows program......)
Thanks for the feedback that I received !
Greetings,
Jos
On Fri, 25 Mar 2005 19:36:10 -0600, Craig Franklin
####@####.#### wrote:
> 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).
> >
......
> >Unfortunately, the .hex created by gplink still doesn't do anything in
> >my 16F870: the device stays completely dead :-(
>
> Have you simulated it?
> Have you disassembled the output and verified it is correct?
