Yahoo Groups archive

Lpc2000

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

Message

Re: [lpc2100] Re: Wiggler JTAG interface

2003-11-26 by Robert Adsett

At 06:29 PM 11/26/03 +0000, you wrote:
>--- In lpc2100@yahoogroups.com, Robert Adsett <radsett@a...> wrote:
> > At 05:55 PM 11/26/03 +0000, you wrote:
> > >15)RST
> > >17)Pull low via 10K resistor
> > >19)N/C
> > >
> > >Richard
> >
> > Hmmm, I've got pins 15, 17, and 19 as N/C (As does Nohau on their
> > evaluation board).  All the interface specs I saw indicated that should
> > work.  Perhaps the Wiggler's requirements are different?  I do have an
> > issue making connections consistently to either the Nohau board or my
> > own.  Once they communicate everything seems fine.
>
>I've got 17 and 19 NC, with 15 pulled up and connected to nRST.

As it turns out it is none of those.  15,17,19 as N/C works fine (I came up 
with that after reading documentatio from ARM, Nohau and Ashling and 
attempting to resolve the apparent contradictions).  I will probably revise 
the board at some point to allow the pull-dn and connection to reset.

The real problem I was having turned out to be the parallel port.  The 
wiggler will not work with the port in ECP mode (since it literally shows 
up with no documentation that was not apparent).  I switched it to EPP and 
have had no problems since.  I can even set breakpoints now.  The last time 
I checked my parallel port mode was probably more than 5 years ago.  Since 
the problem was appear to get worse I tracked down the faq on Macraigors site.

Of course it also didn't help that I did part of my testing with the JTAG 
disabled on the board.  I KNEW I put those jumpers on for a reason ;)

Scream!

Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

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.