Yahoo Groups archive

Lpc2000

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

Message

Re: development tools for LPC2138

2005-02-16 by Owen Mooney

Hi Daniel

You will get many replies to this - and each reply will reflect the tools of the responder.

I use a Crossworks by Rowley (for the 2106) with a Wriggler compatible Jtag from Olimex. The Olimex hardware is cheaper than you could make it if you put any value at all on your time.

The Crossworks compiler is cheaper than most - but not as cheap as the gnu tools which are free. I understand that Rowley have now updated this complier to the 2138.

The  source level debugging is not bad (many breakpoints allowed) I wish the tool tip evaluator for char* types would show me the string rather than the pointer value !!!! but all in all - its an efficent tool. 

On the other had the "debug_printf" (comes out through the Jtag without hardware or memory overhead) is brilliant.

I never need trace. Hey 99.9% of the time you can run to breakpoint and look at the variables to sort your problems.

I hope this helps 

Owen Mooney.

(Kick back from Rowley would be appreciated - Nah - just kidding :-) )

Hi,
I plan to start with 2138 and I need to choose a dev. tool.

Can somebody tell me his development tool (IDE,compiler,debugger) 
and above all his JTAG debugger (with appreciation) ?

Debuggers with trace recording seems very expensive !

Does simple JTAG probe (no trace, 2 hard breakpoints) sufficient for 
debugging ?

Thank you
D.






____________

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.