Lpc2000

I also have the same timeout errors with an Olimex LPC-P1 board and 
the Olimex JTAG cable using CrossStudio Eval.

I tried with different PC configuration (PII and PIII, Win2K and XP, 
ECP and EPP parallel port) but I gave up and I am using the RAM 
configuration for the moment.

HAO


--- In lpc2000@yahoogroups.com, "nw_mcu" <nw_mcu@y...> wrote:
> --- In lpc2000@yahoogroups.com, pontus.oldberg@i... wrote:
> > You shouldn't have any problems at all.
> > I am using the Olimex 2106-MT board together with CrossWorks and 
> > everything works like a charm.I have tried compiling into all 
> > different kind of targets and they all work perfectly.
> 
> I'm using the LPC-P1 (no LCD).  
> 
> 
> > Did you remove both the DEBUG and BSL jumper ?
> 
> The DBG jumper has to be ON with the P1 board.  This pulls DBGSEL 
> high to allow the JTAG interface to work.  The BSL jumper has to be 
> off.
> 
> If this is a problem that only some of us are having, I'm wondering 
> where the problem is?  Is it an issue with the parts?  The Olimex 
> board appears to be reasonably well designed and made.  It's very 
> simple.  The power supply lines are bypassed, etc.
> 
> It might be the Olimex JTAG Wiggler is the problem.  The Olimex 
> website mentions the following in using the Wiggler with 
IAR: "driver 
> for ARM-JTAG have some glitches on newer and faster computers and 
> does several crashes before connect to target".  That may well be 
an 
> IAR problem, but it's not too far off from what I'm seeing with 
> CrossStudio.
> 
> It's really frustrating to have to be debugging tool/part problems 
> instead of my own code.  I'd hoped the LPC parts (and certainly 
ARM7 
> tools) were sufficiently mature to avoid this sort of thing, but 
that 
> doesn't seem to be the case so far.  Admitedly, however, the tools 
> I'm using are at the bargain end of the scale.