Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: Choosing an IDE for the LPC2114

2004-03-14 by johnnorgaard2003

--- In lpc2000@yahoogroups.com, "thomasleuthner" <thomas@m...> wrote:
> Hello,
> 
> We have the same problem at the moment.
> 
> We consider the Hitech system (www.hitech.com.au) -
> 
> or a chinese system with the GNU compiler and a JTAG debugger 
> (www.embedinfo.com).
> 
> Anybody has experience with these?
> 
> Somebody asked why one would need an integrated development system. 
> Answer: just for the debugger - not for the compiler and linker, 
> since "make" is a tool with much more options than any IDE I saw up 
> to now.
> 
> Regards
> 
> Thomas Leuthner

Hi 

I have also seen that Hitech have a ARM compiler and an IDE.
I have downloaded the compiler and read some of the manual and sent
them som questions !

Here they are
I have downloaded the ARM Evaluation C compiler.
1)Is is possible to use JTAG debug with the compiler together with ex.
Philips LPC2104 ?
2)I can not find anything about JTAG in the USER Manual ??

3)Is the compiler based on GNU or is it your own work ?

The answers from HItech

1) I am not 100% about the JTAG for Philips LPC2104. Hi-Tide uses 
Seehau ARM
debugger to debug the chips. I believe they do, but you might want to 
contact them
directly to confirm.

2) The manual does not mention debugger for the reason that it is a 
third party
tool. You should be able to find some info on it in "getting started" 
guide.

3) The compiler is our own work. You should find it fairly easy to 
use if you have
worked with gcc in the past, as both of them are ANSI C compliant and 
quite a few
compiler options in our compilers mirror those found in gcc.

--------------------------------------------------------------------

I am self considering  compiler and IDE. I think I will go for IAR or
Rowley

Best regards

John Noergaard

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.