LPC214x's BSP for RTEMS

[ray]

You can refer to the rtl22xx bsp, which is based on lpc2210. Hope it helps. rtl22xx is already in the CVS's ARM dir.
BTW, I noticed that lpc3xxx is a ARM926 core and the interrupt and uart module is different.

------------------
Thanks & Best Regards!
ray
2007-06-11

-------------------------------------------------------------
From: Todd_Peterson
Date: 2007-06-11 23:13:01
To:   rtems-users at rtems.org
CC:
Sub:  Re: LPC214x's BSP for RTEMS

>>Where in CVS is this BSP? I hunted around for it, but couldn't find it.
>I'm working with an LPC3180 board and hope that the LPC214x is somewhat
>close.
>
>Todd Peterson
>Management Sciences, Inc.
>
>
>
>
>Joel Sherrill <joel.sherrill at oarcorp.com>
>Sent by: rtems-users-bounces+todd_peterson=mgtsciences.com at rtems.org
>06/11/2007 08:04 AM
>
>To
>dave madden <dhm at mersenne.com>
>cc
>rtems-users at rtems.org
>Subject
>Re: LPC214x's BSP for RTEMS
>
>
>
>
>
>
>dave madden wrote:
>>>>>>> "RXU" == ray  <xr at trasin.net> writes:
>>>>>>>
>>
>>     RXU> Hi Joel and I had made some changes in RTEMS CVS.  The
>>     RXU> current rtl22xx BSP need 7K bss/data for hello. If you change
>>     RXU> the definition for stack size(RTEMS_MINIMUM_STACK_SIZE)from
>>     RXU> 4K to 1K. You can also save some memory.  Hope you can put
>>     RXU> RTEMS into you lpc214x board.
>>
>> Hi Ray.
>>
>> I had some free time, so I copied the rtl22xx BSP and started hacking
>> on it.  I got it to boot and prink() some messages, but it dies in
>> rtems_termios_initialize with error 5.  I'm not very familiar with GDB
>> remote debugging, so it's hard for me to move around efficiently, but
>> I think it was trying to allocate a semaphore when it failed.
>>
>
>You have to configure the number of each type of RTEMS object
>you want.  You didn't configure any semaphores and probably
>didn't link in  the semaphore manager either.
>
>But the bigger question is.. is Ray using the termios console
>driver?  I thought he was only using printk() and avoiding the
>full featured console device driver and the termios subsystem
>entirely.
>> Is there a way to get GDB's "next" and "step" commands to use hardware
>> breakpoints by default?  That would make my life *much* easier!
>> (Can't use normal breakpoints because the code is in flash.  Also,
>> there are only 2 hardware breakpoints...talk about tedious!)
>>
>>
>This is for someone else.
>> If you're interested, I can send what I've done.  Mostly, I adjusted
>> the linker script and startup code to reflect the 2148 memory map.
>>
>When it works, I would like to see another BSP merged.
>If the hardware is close enough, you might be able to
>share a BSP and use a "variant" to change compile time
>options.
>
>--joel
>> Regards,
>> dave madden
>> _______________________________________________
>> rtems-users mailing list
>> rtems-users at rtems.com
>> http://rtems.rtems.org/mailman/listinfo/rtems-users
>>
>
>_______________________________________________
>rtems-users mailing list
>rtems-users at rtems.com
>http://rtems.rtems.org/mailman/listinfo/rtems-users
>
>
>_______________________________________________
>rtems-users mailing list
>rtems-users at rtems.com
>http://rtems.rtems.org/mailman/listinfo/rtems-users
>