gnupic: Re: [gnupic] Usinc SDCC for pic16f877a or 18f452?
Subject:
Re: [gnupic] Usinc SDCC for pic16f877a or 18f452?
From:
msw ####@####.####
Date:
15 Jan 2007 00:34:45 +0000
Message-Id: <1168821125.3373.23.camel@mwaters.bom.gov.au>
Hi Iain,
The following are only my opinions / experiences; take them or leave
them. Also, I am very biased towards GNU software; beware.
I've been using SDCC for PIC16 development for about 2 years and have
few reservations about recommending it. I've tried Hi-Tech C, CCS C
but have settled on SDCC. The following points may be of interest:
* SDCC uses RAM very efficiently which is good since the PICs are
relatively program memory rich and RAM poor.
* The learning curve for SDCC is initially steep since the documentation
is a bit difficult understand at first. Some things like libraries
I've had to work out from the SDCC source code.
* C comments are retained in the ASM files. Essential for debugging at
times.
* The PIC16 compiler isn't perfect but I can't recall coming across any
bugs myself. I have come across two assembler bugs however.
* SDCC is continuously being developed which means support is available
if needed.
Mike W.
On Sat, 2007-01-13 at 15:09 -0800, iain duncan wrote:
> Hi folks, I'm interested in trying out the SDCC ( have already done a
> fair bit of simple assembly stuff ) for the Pic 16F877 or 18F452. I use
> PikDev and a JDM programmer. I notice that the SDCC page says there is
> "some support" for these chips, but I don't know what to make of that.
> How usable is SDCC? How would one know if you are asking too much of it?
> Being a self taught hobbyist, I am warry of using it if it means that I
> will get frustrated by bugs in the compiler that I can't understand.
>
> I'm not doing anything too complex, but I would like to work up to doing
> USB serial communication and high res ADC/DAC conversions with either
> the DSPIC or external converter chips.
>
> Thanks
> Iain
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
