Lpc2000

Greetings,

Being a little green with LPC2106 debugging, I need some help.

I have the Olimex LPC2106 dev. board and it appears to function fine 
with the Philips ISP software, also the supplied test program in 
flash works fine.

Now am trying to get my (home made) Wiggler to work with it, but keep 
getting a message from OcdLibRemote to the effect that the "cable is 
not connected". The DBGSEL jumper is inserted (i.e., pin 27 pulled 
high) and the board seems to have NTRST pulled high as well (NC on 
the Wiggler interface).

When connecting this same JTAG debug hardware to my EB40A, it works 
just fine. So, I guess it must be something with the LPC2106 or 
perhaps circuit loading thats different?

Scoping the RST line, the EB40A comes nicely out of reset under 
control of OcdLibRemote, but all I see for the Olimex board is a 
brief blip on the RST line.

Any ideas would be appreciated.

Thanks much.

Johan.

----- Original Message ----- 

From: "Johan" <jbforrer@...>
To: <lpc2000@yahoogroups.com>
Sent: Sunday, April 11, 2004 12:03 AM
Subject: [lpc2000] Wiggler JTAG problem


> Greetings,
>
> Being a little green with LPC2106 debugging, I need some help.
>
> I have the Olimex LPC2106 dev. board and it appears to function fine
> with the Philips ISP software, also the supplied test program in
> flash works fine.
>
> Now am trying to get my (home made) Wiggler to work with it, but keep
> getting a message from OcdLibRemote to the effect that the "cable is
> not connected". The DBGSEL jumper is inserted (i.e., pin 27 pulled
> high) and the board seems to have NTRST pulled high as well (NC on
> the Wiggler interface).
>
> When connecting this same JTAG debug hardware to my EB40A, it works
> just fine. So, I guess it must be something with the LPC2106 or
> perhaps circuit loading thats different?
>
> Scoping the RST line, the EB40A comes nicely out of reset under
> control of OcdLibRemote, but all I see for the Olimex board is a
> brief blip on the RST line.

Have you tried it with OCD Commander? That is what I used for getting my
interface working.

Leon

--- Leon Heller <leon_heller@...> wrote:
> 
> ----- Original Message ----- 
> From: "Johan" <jbforrer@...>
> To: <lpc2000@yahoogroups.com>
> Sent: Sunday, April 11, 2004 12:03 AM
> Subject: [lpc2000] Wiggler JTAG problem
> 
> 
> > Greetings,
> >
> > Being a little green with LPC2106 debugging, I
> need some help.
> >
> > I have the Olimex LPC2106 dev. board and it
> appears to function fine
> > with the Philips ISP software, also the supplied
> test program in
> > flash works fine.
> >
> > Now am trying to get my (home made) Wiggler to
> work with it, but keep
> > getting a message from OcdLibRemote to the effect
> that the "cable is
> > not connected". The DBGSEL jumper is inserted
> (i.e., pin 27 pulled
> > high) and the board seems to have NTRST pulled
> high as well (NC on
> > the Wiggler interface).
> >
> > When connecting this same JTAG debug hardware to
> my EB40A, it works
> > just fine. So, I guess it must be something with
> the LPC2106 or
> > perhaps circuit loading thats different?
> >
> > Scoping the RST line, the EB40A comes nicely out
> of reset under
> > control of OcdLibRemote, but all I see for the
> Olimex board is a
> > brief blip on the RST line.
> 
> Have you tried it with OCD Commander? That is what I
> used for getting my
> interface working.
> 
> Leon
> 

Thanks for the suggestion Leon --- OCD Commander seem
to work OK with my JTAG debug hardware. 

I suspect a hardware initialization issue with
OCDLibRemote and the LPC210x. It is possible to do
device initialization when OCDLibRemote starts up that
may solve this initialization issue, not sure exactly
how yet. 

Has anyone been successful in using the LPC2106 with a
WIGGLER using OcdLibRemote?

Thanks,

Johan

At 05:00 PM 4/12/04 -0700, you wrote:
>Has anyone been successful in using the LPC2106 with a
>WIGGLER using OcdLibRemote?

I have, although it sometimes takes me a couple of tries to connect 
successfully.  Usually if I'm having a real problem connecting it's because 
I either didn't set dbgsel correctly for I forgot to plug the cable into 
the printer port :)

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

Hi all

I have some questions regarding the JTAG interface ...

I've been writing embedded software for quite some years now and relied upon
the UART , port pins or LCD as the main way to debug my code and funny
enough I have ALOT of software out in the real world working like a charm so
I was wondering what you guys that use the JTAG has to say about it ...
opions etc...
does it work with all compilers ? does it work inline in C programming ? all
these things ...

regards
Lasse Madsen
Embedded Engineer

--- In lpc2000@yahoogroups.com, "Lasse Madsen" <lm@h...> wrote:
> Hi all
> 
> I have some questions regarding the JTAG interface ...
> 
> I've been writing embedded software for quite some years now and 
relied upon
> the UART , port pins or LCD as the main way to debug my code and 
funny
> enough I have ALOT of software out in the real world working like a 
charm so
> I was wondering what you guys that use the JTAG has to say about 
it ...
> opions etc...
> does it work with all compilers ? does it work inline in C 
programming ? all
> these things ...


It does make debugging a lot more convenient and easy. The MCU needs 
a JTAG interface, of course. They are getting a lot more common, many 
of the newer devices like the LPC2000 have it and it is well worth 
making use of it.

It works with most of the available compilers on the LPC2000.

Leon

--- Robert Adsett
<subscriptions@...> wrote:
> At 05:00 PM 4/12/04 -0700, you wrote:
> >Has anyone been successful in using the LPC2106
> with a
> >WIGGLER using OcdLibRemote?
> 
> I have, although it sometimes takes me a couple of
> tries to connect 
> successfully.  Usually if I'm having a real problem
> connecting it's because 
> I either didn't set dbgsel correctly for I forgot to
> plug the cable into 
> the printer port :)
> 
> 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
> 
> 
Thanks Robert --- at least I know that it can work
like that.

One other tidbit I learned along the way ... even with
the target not being powered up, the Wiggler interface
provides a weak power source to the target via the LPT
cable, guess trough leakage along pullups etc. This
weak power source is enough to get the LPC2106 locked
up in a bad state -- it is doubtful whether it will
never get into debug state like that. 

The solution is to be careful about the order you
power up and connect things up. Start out by having
the Wiggler disconnected from the LPT cable, then
connect up the target. Next power up the target to
supply power to the Wiggler, and finally connect the
LPT cable. This way the LPC2106 is in a good state and
ready for the JTAG-debug session.

Johan Forrer

At 08:37 AM 4/13/04 +0200, you wrote:
>enough I have ALOT of software out in the real world working like a charm so
>I was wondering what you guys that use the JTAG has to say about it ...
>opions etc...
>does it work with all compilers ? does it work inline in C programming ? all
>these things ...

JTAG is somewhere between printf type debugging and a fully functional 
ICE.  It doesn't have the power of a full ICE but (especially if you add 
embedded trace) it comes close at a fraction of the cost.  I don't think 
I've seen a micro with JTAG available also have an ICE.

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

Robert,

your statement about micros with JTAG not having an ICE is definitely
true. What JTAG is lagging is trace. ARM provides a debug interface
called ETM, Embedded Trace Macrocell(tm). Surpisingly this trace
interface did not make it onto many devices yet, usually only the high
priced versions, except the LPC2000 devices. They have the ETM
interface built in. So, if you need more than just 2 HW-breakpoints
offered if debugging from Flash, the ETM offers trace and tells you
HOW you got to the location you were never suppossed to end up at.

Cheers, Bob


> 
> JTAG is somewhere between printf type debugging and a fully functional 
> ICE.  It doesn't have the power of a full ICE but (especially if you
add 
> embedded trace) it comes close at a fraction of the cost.  I don't
think 

> I've seen a micro with JTAG available also have an ICE.
> 
> 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

Bob,

> your statement about micros with JTAG not having an ICE is definitely
> true. What JTAG is lagging is trace. ARM provides a debug interface
> called ETM, Embedded Trace Macrocell(tm). Surpisingly this trace
> interface did not make it onto many devices yet, usually only the high
> priced versions, except the LPC2000 devices. They have the ETM
> interface built in. So, if you need more than just 2 HW-breakpoints
> offered if debugging from Flash, the ETM offers trace and tells you
> HOW you got to the location you were never suppossed to end up at.

And on the LPC210x you pay by losing half your I/O to JTAG and ETM.  I
can't see the use of ETM on a device with limited I/O capability.

-- Paul.