Lpc2000

I have troubled with the same issue, both on an IAR/Philips "kick-
start" board and on my own design. I am using the IAR/Segger j-link 
JTAG if, IAR C-spy and LPC2106.

Most times it is not possible to do debugging directly from secondary 
JTAG without first loading code via primary JTAG. (Of course I have a 
program in flash setting PINSEL1 as described in AN10255.) But if I 
have loaded code once via JTAG1, it is no problem to download over 
JTAG2 until next power down. The error message is "Invalid core ID". 
Trying with the Segger JMem utility gives a similar result.

I have tried removing the RTCK pin from the JTAG connector, without 
any effect. Removing the pull-up resistor does not seem to have any 
effect either.

Jon V

--- In lpc2000@yahoogroups.com, "Jim Beagley" <jim5272@h...> wrote:
> --- In lpc2000@yahoogroups.com, "Jim Beagley" <jim5272@h...> wrote:
> > 
> OOPS! __SORRY__
> 
> So, I was playing with my board today, and while laying out a new 
rev,
> I decided I would try to see what would happen if I removed the RTCK
> pin from the Nohau connection ( pulled header pin asside so it
> wouldn't connect to the dongle ).
> 
> I launched the debugger. I had previously set it up to program the
> board by default, however in the past, the board would throw an 
error,
> and not program. BUT, this time it came right up - IN SECONDARY JTAG
> MODE - and programmed succesfully. The target is now a delight to
> connect to. it connects every try, and programs fine over the
> secondary port. -* sighs in relief *- 
> 
> So it appears that the RTCK pin has been the crux of all the 
problems
> I have been having with the target.
> 
> I removed the connection from the new board, and I feel much better
> about the part now (LPC2104).
> 
> Hope this experience will help someone trying this as well.