[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] Writing code to multiple targets

From: Andrew Vlasov
Subject: Re: [avr-gcc-list] Writing code to multiple targets
Date: Thu, 5 Apr 2001 16:45:06 +0400

I'm also very interested by this problem.

I think, not any "#ifdef <platform>" in your code, it's must be in IO *.h
files common to all platforms:
    IAR, GCC, ...,
        or may be:
    IAR_AVR, GCC_AVR, IAR_HC11, GCC_HC11, ..., PC-WIN32?.

The only company I found is Ramtex Inc. :
    1. Problems with lack of I/O standardization:
    2. www.ramtex.dk/standard/iostand.pdf
    3. SGSETUP also provides you with the possibility of standardizing the
syntax for I/O and interrupt operations :
http://www.ramtex.dk/ftp/freedemo.htm (NO ready AVR database):


----- Original Message -----
From: "Larry Barello" <address@hidden>
To: "AVR GCC List" <address@hidden>
Sent: Wednesday, March 21, 2001 7:22 PM
Subject: [avr-gcc-list] Writing code to multiple targets

> I have a bunch of code written for the classic AVR on
> avr-gcc/gas.  I want to port it to the IAR compiler series
> and I want to accommodate the various classes of AVR chips.
> The latter is not so big a deal since the differences are
> largely covered in the ioxxxx.h files. Yet, there are a few.
> For example the clock divisor bits for TC0 change between
> classic and mega103, the "names" of UCR and USR change
> between classic and mega163.
> 1. Is there a preferred approach to dealing with these
> differences beyond "#ifdef ATmega163 ..."
> 2. Does anyone have experience with writing code for both
> IAR and Avr-gcc and is willing to share any macros/headers
> they have developed to simplify the process?
> _______________________________________________
> avr-gcc-list mailing list
> address@hidden
> http://avr.jpk.co.nz/mailman/listinfo/avr-gcc-list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]