avr-libc-dev
[Top][All Lists]
Advanced

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

Re: [avr-libc-dev] AT43USB35x support!


From: Marek Michalkiewicz
Subject: Re: [avr-libc-dev] AT43USB35x support!
Date: Sat, 1 Mar 2003 00:30:45 +0100
User-agent: Mutt/1.4i

On Fri, Feb 28, 2003 at 10:34:49PM +0100, Joerg Wunsch wrote:
> Are they for IAR compatibility?  If that's the case, we might move them
> out to <compat/ina90.h> (doesn't exist yet in that directory).  Hmm,
> just a thought.  Alternatively, we could e. g. define a symbol like
> __COMPAT_IAR there, and maintain device-specific IAR compatibility
> defines inside the various ioXXX.h files.  It would be nice to have
> them universally available, i. e. to know what to write into the
> other .h files.  Whatever makes migration between the various compilers
> easier for our users is IMHO a win.

OK, I've just added at43usb320 support, and removed the IAR defines
from both io43u32x.h and io43u35x.h for now (can be added later, when
we decide what is the best place for them, ideally for all devices).

One thing about the at43usb320 is not clear to me - it appears to
support 128K bytes (64K*16) of external program memory, but if
FLASHEND is defined as 0x1ffff, RAMPZ must be defined, otherwise
gcrt1.S (using ELPM to copy initialized data) fails to build.

 a. RAMPZ exists, but the datasheet forgot to document it
 b. RAMPZ doesn't exist, upper 64K is only for executable code
 c. RAMPZ doesn't exist, upper 64K is a mistake in the datasheet
 d. give me an easier question ;)

What is the correct answer?

Thanks,
Marek





reply via email to

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