From: Dave McGuire <mcguire@ne...> - 2007-06-24 18:35:41
On Jun 24, 2007, at 8:02 AM, Gudjon I. Gudjonsson wrote:
> Sorry, perhaps I am sending it to the wrong forum but could you
> please add
> this file to the project.
Ahh, I'm glad to see someone else using that family of chips.
I've used lots of 8051 variants, and that one is one of the most
pleasant. I did a few commercial products with it (and SDCC!) 4-5
I never thought to submit the header file to the SDCC project for
inclusion, though...Good thinking!
Port Charlotte, FL
I'm using an 89C668 too, but not with SDCC. One of my customers has an=20
application which is regularly upgraded or updated, every two years or so=20
since 1990. Back then, I developed the original program with PLM/51 and an=
87c654 (I2C). I never took the time to convert the PLM program to C. For ea=
update, I start a 486 PC running MSDOS and tell myself it's the last time ;=
Thinking about retirement, I'll have to talk the customer into ordering the=
conversion from me, if he ever wants maintenance by younger people he's bee=
Le Dimanche 24 Juin 2007 20:35, Dave McGuire a =E9crit=A0:
> On Jun 24, 2007, at 8:02 AM, Gudjon I. Gudjonsson wrote:
> > Sorry, perhaps I am sending it to the wrong forum but could you
> > please add
> > this file to the project.
> > Cheers
> > Gudjon
> > <P89c66x.h>
> Ahh, I'm glad to see someone else using that family of chips.
> I've used lots of 8051 variants, and that one is one of the most
> pleasant. I did a few commercial products with it (and SDCC!) 4-5
> years ago.
> I never thought to submit the header file to the SDCC project for
> inclusion, though...Good thinking!
Never jump into a loop!
thanks for providing the nice header file!)
It could go in "as is".
Yet I want to draw your attention to the latest
NXP/Philips header file distributed with SDCC:
This most modern format which #includes <compiler.h>
allows to use the _same_ header file for quite a few compilers
(SDCC, Keil, Raisonance, IAR, Hi-Tech, Tasking, Crossware, Wickenhäuser)
While it may or may not be in our best interest to provide
such an easy path to walk away from SDCC and use another
compiler we (naturally I can only speak for myself but I
think this is consensus) want to push that format.
It gives users more freedom, avoids duplicate work,
and may lead to more (and/or more reliable) header files.
I'm not sure whether this has been mentioned previously but with
this format one should _also_ be able to derive an assembly
include file (*.inc file) semi-automatically from a C-header
Adapt the macro definitions within compiler.h
which do the conversion for the compiler syntax and typically look like:
#define SFR(name, addr) __sfr __at(addr) name
to something that pleases the assembler syntax
and then run a C-preprocessor over the header file:)
(most C-compilers will also have a preprocessonly mode)
Get latest updates about Open Source Projects, Conferences and News.