Migrating from 2106 to 2138

Started by rtstofer October 22, 2005
Other than changing the device header file, am I going to get any big
surprises moving up to a more capable chip? Yes, less RAM but that
isn't important. Nor is flash. I just need the pins.

I am using arm-elf-gcc 3.4.3.

Thanks
Richard


An Engineer's Guide to the LPC2100 Series

http://www.geocities.com/michaelanburaj/downloads/lpc_1.00.zip

includes a ROM monitor image -- the same binary runs
fine on both 210x & 213x --except for memory sizes &
peripherals, there is not much difference (in terms of
basic functionality) between 210x & 213x.

Cheers,
-Mike.

--- rtstofer <rstofer@rsto...> wrote:

> Other than changing the device header file, am I
> going to get any big
> surprises moving up to a more capable chip? Yes,
> less RAM but that
> isn't important. Nor is flash. I just need the
> pins.
>
> I am using arm-elf-gcc 3.4.3.
>
> Thanks
> Richard


__________________________________


rtstofer wrote:

>Other than changing the device header file, am I going to get any big
>surprises moving up to a more capable chip? Yes, less RAM but that
>isn't important. Nor is flash. I just need the pins. >
Device Registers are greatly different in some cases. The SPI is
capable of sending more bytes per transfer and has a lot more settings.
You'll probably have to make changes to your code to get it to run
against these new settings in the registers. There is an
IO0{SET,CLR,PIN} and IO1{SET,CLR,PIN} macros...

Your experience with the LPC2106 will benefit you. BTW, do not trust
any device headers (e.g. LPC21xx.h) that you may download, I had to make
significant changes to the one I found so that it would work with the
LPC2138. There were missing definitions, a lot of them!

TomW
>I am using arm-elf-gcc 3.4.3.
>
>Thanks
>Richard >Yahoo! Groups Links


--
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------