Lpc2000

Hi, Klaus, we are two guys working with the same environment for about three
months. Productivity has been reasonably good. Our biggest problem is the
Keil IDE (V3.20a) bombing out occasionally, especially when you start a
debug session or click on anything in the Edit menu. Right now, we are using
ULINK and the MCB2140 eval board from Keil. The project uses one I2C, one
SPI, two UARTS and four EINTs, all interrupt driven.

The environment is not trivial, and we have had quite a few problems with
our understanding of ARTX and JTAG debugging. Some recommendations:
- Include the ARTX source in your project so you can source code debug it
along with your project.
- Single step the part of your code where you start the tasks. It is not
obvious in what order your initialization code works. You may be waiting for
a Semaphore before it has been initialized, for example.
- Place breakpoints in the ABT and UNDEF vector addresses. The Link Register
(LR) will point to where bad things happened.
- Put a long (>0.5s) busy wait delay loop early in startup.s. This will
prevent your initialization to start before ULINK can halt the processor
when you reload or click on the Halt button.
- The source code browser, new in V3.20a, is really very useful.
- Put a counter in ARTX_Config.c, os_def_interrupt(). This will help you
discover spurious interrupts. 

Maybe you could be more specific about your problems?

Lars Marmsater

-----Original Message-----
From: Klaus [mailto:klaus276@...] 
Sent: Friday, August 19, 2005 2:51 AM
To: lpc2000@yahoogroups.com
Subject: [lpc2000] Keil CARM and ARTX

Does anybody work with the new Keil IDE, with CARM and ARTX? 
I have worked with it 4 months up to now, and my experiences are not
so good ( i dont want to use ****-words). 70% of my time, I am
searching the bugs, speaking with the support and waiting for the next
bugfix. My project should have been finished last month.
If you have similar experience, please let me know or contact me directly.
Klaus





 
Yahoo! Groups Links



 


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.12/77 - Release Date: 8/18/2005