Lpc2000

----- Original Message ----- 
From: "mgiaco82" <mgiaco82@...>
To: <lpc2000@yahoogroups.com>
Sent: Saturday, April 15, 2006 8:59 AM
Subject: [lpc2000] Re: LPC2148 - Crossworks


> --- In lpc2000@yahoogroups.com, "FreeRTOS Info" <nospam@...> wrote:
>>
>> > 1) Can I use this compiler for lpc2148 because i found no
>> > informations on the website. And i also found no sample code for
>> > lpc2148 on the sample files.
>> 
>> Yes.  You can use the compiler for any LPC chip, for any ARM7 for 
> that 
>> matter.
>> 
>> When creating a new solution I suggest choosing a target chip that 
> has the 
>> same memory map as the LPC2148 (LPC2138 looks like a good candidate 
> from a 
>> quick scan of the Philips WEB site, and is an option in 
> CrossWorks), then 
>> the project should have the startup code and linker setting you 
> need 
>> automatically.
>> 
>> 
>> > 2) Is difficult to rewrite the sample programs from Phillips (Keil
>> > bundle or ARM bundle) to Crossworks? What must i look for.
>> 
>> Slightly different syntax required for:
>> + ARM/THUMB interworking,
>> + declaration of interrupt service routines
>> + intrinsic functions.
>> 
>> Generally it is straight forward.
>> 
>> > 3) Is the tasking libary from rowley the same as an operating 
> system
>> > like ucos-ii.
>> 
>> Have not used it but looks similar: 
>> http://www.rowley.co.uk/documentation/arm/ctl.htm
>> 
>> 
>> > 4) Is there any port for ucos-ii for rowley crossworks?
>> 
>> Just use a GCC port, it will work with CrossWorks.  I think there 
> is also an 
>> LPC2148 FreeRTOS.org port in the files section of this group.
>> 
>> Regards,
>> Richard.
>> 
>> http://www.FreeRTOS.org
>> *Now for ARM CORTEX M3!*
>>
> 
> 
> Thanks, Today I will start with Crossworks. What do you mean with 
> ARM/THUMB interworking ?

Mixing ARM and Thumb code.

Leon
--
Leon Heller, G1HSM
leon.heller@...
http://www.geocities.com/leon_heller
---
[This E-mail has been scanned for viruses but it is your responsibility 
to maintain up to date anti virus software on the device that you are
currently using to read this email. ]