Yahoo Groups archive

Lpc2000

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

Thread

JTAG Debugging problem

JTAG Debugging problem

2004-11-03 by theeuwke

Hi everyone,

Because my wiggler didn't work (see topic: Wiggler by theeuwke),
i've got from an other department some nice equipment; a JEENI and an 
MAJIC from EPI. But stil, I can't get this stuff to work. 
First some info:

I have two boards; first one is an EVBA7 from Ashling;
http://www.ashling.com/datasheets/DS266-EvKitLPC2000.html
It has an LPC2106 microcontroller (ARM7TDMIS)

To debug with this board, I set the Secondary debug jumber on 
enabled, the primairy debug jumper on disabled, the onboard debug on 
disabled, and ISR on disabled. I flashed a program to enable the 
secondary JTAG port that was delivered with the board, but I also 
tried the one in the files section. I just connected the device with 
the JEENI and the MAJIC with a standard 20 pin connector, that commes 
from EPI. When I use the JEENI, and try to connect with GDB, it 
complanes that "Target World is Broken" ?. If I use Debugger from 
ARM, it says that the processor is Running, i've got the same problem 
with the wiggler. When I use the MAJIC, it says "RTCK is stopped or 
extremely slow.

The second board is a custom made board bassed on the LPC2292. It has 
a mini 10 pin header, with TDO connected, TDI, TCK connected to the 
header and 3v3 with a 33k resistor, TMS connected to the header, TRST 
to header and 3v3 by 100k resistor and SRST to the system reset. 
When I tried the JEENI, because it doen't use the RTCK, I connected 
to the ground with a 4k7 resistor, with the majic i just connect it. 
So everything is connected good i believe, and I measured all the 
inputs to the lpc, and the resets are going up and down propperly, 
tck gets there, and there goes data in, but there is nothing comming 
out. I tried to upload a program that implicit sets PINSEL2 to DEBUG, 
but it didn't help. I have still the same problems as the first board.
What the hell am I doing wrong?

Re: JTAG Debugging problem

2004-11-03 by theeuwke

--- In lpc2000@yahoogroups.com, "theeuwke" <theeuwke@y...> wrote:
> 
> Hi everyone,
> 
> Because my wiggler didn't work (see topic: Wiggler by theeuwke),
> i've got from an other department some nice equipment; a JEENI and 
an 
> MAJIC from EPI. But stil, I can't get this stuff to work. 
> First some info:
> 
> I have two boards; first one is an EVBA7 from Ashling;
> http://www.ashling.com/datasheets/DS266-EvKitLPC2000.html
> It has an LPC2106 microcontroller (ARM7TDMIS)
> 
> To debug with this board, I set the Secondary debug jumber on 
> enabled, the primairy debug jumper on disabled, the onboard debug 
on 
> disabled, and ISR on disabled. I flashed a program to enable the 
> secondary JTAG port that was delivered with the board, but I also 
> tried the one in the files section. I just connected the device 
with 
> the JEENI and the MAJIC with a standard 20 pin connector, that 
commes 
> from EPI. When I use the JEENI, and try to connect with GDB, it 
> complanes that "Target World is Broken" ?. If I use Debugger from 
> ARM, it says that the processor is Running, i've got the same 
problem 
> with the wiggler. When I use the MAJIC, it says "RTCK is stopped or 
> extremely slow.
> 
> The second board is a custom made board bassed on the LPC2292. It 
has 
> a mini 10 pin header, with TDO connected, TDI, TCK connected to the 
> header and 3v3 with a 33k resistor, TMS connected to the header, 
TRST 
> to header and 3v3 by 100k resistor and SRST to the system reset. 
> When I tried the JEENI, because it doen't use the RTCK, I connected 
> to the ground with a 4k7 resistor, with the majic i just connect 
it. 
> So everything is connected good i believe, and I measured all the 
> inputs to the lpc, and the resets are going up and down propperly, 
> tck gets there, and there goes data in, but there is nothing 
comming 
> out. I tried to upload a program that implicit sets PINSEL2 to 
DEBUG, 
> but it didn't help. I have still the same problems as the first 
board.
> What the hell am I doing wrong?

Well, ok, When I configure the MAJIC (to no use of the RTCK, just 
connected to GND by resister), it does something more, but still 
problems with "cpu not stopped, reset maybe required".

Re: JTAG Debugging problem

2004-11-03 by theeuwke

--- In lpc2000@yahoogroups.com, "theeuwke" <theeuwke@y...> wrote:
> 
> --- In lpc2000@yahoogroups.com, "theeuwke" <theeuwke@y...> wrote:
> > 
> > Hi everyone,
> > 
> > Because my wiggler didn't work (see topic: Wiggler by theeuwke),
> > i've got from an other department some nice equipment; a JEENI 
and 
> an 
> > MAJIC from EPI. But stil, I can't get this stuff to work. 
> > First some info:
> > 
> > I have two boards; first one is an EVBA7 from Ashling;
> > http://www.ashling.com/datasheets/DS266-EvKitLPC2000.html
> > It has an LPC2106 microcontroller (ARM7TDMIS)
> > 
> > To debug with this board, I set the Secondary debug jumber on 
> > enabled, the primairy debug jumper on disabled, the onboard 
debug 
> on 
> > disabled, and ISR on disabled. I flashed a program to enable the 
> > secondary JTAG port that was delivered with the board, but I 
also 
> > tried the one in the files section. I just connected the device 
> with 
> > the JEENI and the MAJIC with a standard 20 pin connector, that 
> commes 
> > from EPI. When I use the JEENI, and try to connect with GDB, it 
> > complanes that "Target World is Broken" ?. If I use Debugger 
from 
> > ARM, it says that the processor is Running, i've got the same 
> problem 
> > with the wiggler. When I use the MAJIC, it says "RTCK is stopped 
or 
> > extremely slow.
> > 
> > The second board is a custom made board bassed on the LPC2292. 
It 
> has 
> > a mini 10 pin header, with TDO connected, TDI, TCK connected to 
the 
> > header and 3v3 with a 33k resistor, TMS connected to the header, 
> TRST 
> > to header and 3v3 by 100k resistor and SRST to the system reset. 
> > When I tried the JEENI, because it doen't use the RTCK, I 
connected 
> > to the ground with a 4k7 resistor, with the majic i just connect 
> it. 
> > So everything is connected good i believe, and I measured all 
the 
> > inputs to the lpc, and the resets are going up and down 
propperly, 
> > tck gets there, and there goes data in, but there is nothing 
> comming 
> > out. I tried to upload a program that implicit sets PINSEL2 to 
> DEBUG, 
> > but it didn't help. I have still the same problems as the first 
> board.
> > What the hell am I doing wrong?
> 
> Well, ok, When I configure the MAJIC (to no use of the RTCK, just 
> connected to GND by resister), it does something more, but still 
> problems with "cpu not stopped, reset maybe required".

Oops, so i conigured the MAJIC to use a ARM7DTMI instead of ARM7DTMI-
S, so not using the RTCK pin.

Re: JTAG Debugging problem

2004-11-03 by leon_heller

--- In lpc2000@yahoogroups.com, "theeuwke" <theeuwke@y...> wrote:
> 
> Hi everyone,
> 
> Because my wiggler didn't work (see topic: Wiggler by theeuwke),


Did you try setting the parallel port to EPP mode?

Leon

Re: JTAG Debugging problem

2004-11-03 by theeuwke

--- In lpc2000@yahoogroups.com, "leon_heller" <leon_heller@h...> 
wrote:
> 
> --- In lpc2000@yahoogroups.com, "theeuwke" <theeuwke@y...> wrote:
> > 
> > Hi everyone,
> > 
> > Because my wiggler didn't work (see topic: Wiggler by theeuwke),
> 
> 
> Did you try setting the parallel port to EPP mode?
> 
> Leon

I have only a PS/2 and AT mode on my Dell machine, but windows XP 
says its in ECP. So I manually changed the driver to Standard LPT 
port in PS/2 mode (because it needs to be bidirectional). But no 
luck. But nu I have the JEENI and je MAJIC, and they both work with 
a ethernet connection.

Re: [lpc2000] JTAG Debugging problem

2004-11-03 by David Roethig

We have the Ashling board with the 2294 footprint adapter and
experienced problems with the Wiggler.
We were able to get the Wiggler to work by changing R39 from
10K to 1K.

The problem was that the RST line was too slow coming
out of reset.



theeuwke wrote:
Show quoted textHide quoted text
> 
> Hi everyone,
> 
> Because my wiggler didn't work (see topic: Wiggler by theeuwke),
> i've got from an other department some nice equipment; a JEENI and an
> MAJIC from EPI. But stil, I can't get this stuff to work.
> First some info:
> 
> I have two boards; first one is an EVBA7 from Ashling;
> http://www.ashling.com/datasheets/DS266-EvKitLPC2000.html
> It has an LPC2106 microcontroller (ARM7TDMIS)
> 
> To debug with this board, I set the Secondary debug jumber on
> enabled, the primairy debug jumper on disabled, the onboard debug on
> disabled, and ISR on disabled. I flashed a program to enable the
> secondary JTAG port that was delivered with the board, but I also
> tried the one in the files section. I just connected the device with
> the JEENI and the MAJIC with a standard 20 pin connector, that commes
> from EPI. When I use the JEENI, and try to connect with GDB, it
> complanes that "Target World is Broken" ?. If I use Debugger from
> ARM, it says that the processor is Running, i've got the same problem
> with the wiggler. When I use the MAJIC, it says "RTCK is stopped or
> extremely slow.
> 
> The second board is a custom made board bassed on the LPC2292. It has
> a mini 10 pin header, with TDO connected, TDI, TCK connected to the
> header and 3v3 with a 33k resistor, TMS connected to the header, TRST
> to header and 3v3 by 100k resistor and SRST to the system reset.
> When I tried the JEENI, because it doen't use the RTCK, I connected
> to the ground with a 4k7 resistor, with the majic i just connect it.
> So everything is connected good i believe, and I measured all the
> inputs to the lpc, and the resets are going up and down propperly,
> tck gets there, and there goes data in, but there is nothing comming
> out. I tried to upload a program that implicit sets PINSEL2 to DEBUG,
> but it didn't help. I have still the same problems as the first board.
> What the hell am I doing wrong?
> 
> 
> 
> 
> 
> 
> *Yahoo! Groups Sponsor*
> <http://us.ard.yahoo.com/SIG=129fm3jnj/M=281955.5530326.6602771.3001176/D=groups/S=1706554205:HM/EXP=1099573468/A=2343726/R=0/SIG=12idnga58/*http://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=1099487068145799> 
> 
> 
> Get unlimited calls to
> 
> U.S./Canada
> 
> <http://us.ard.yahoo.com/SIG=129fm3jnj/M=281955.5530326.6602771.3001176/D=groups/S=1706554205:HM/EXP=1099573468/A=2343726/R=1/SIG=12idnga58/*http://clk.atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=1099487068145799> 
> 
> 
> 
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
> 
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/lpc2000/
>        
>     * To unsubscribe from this group, send an email to:
>       lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>. 
> 
>

RE: [lpc2000] JTAG Debugging problem

2004-11-03 by Hugh O'Keeffe

I can confirm this. Here is my original post on the topic: 
 
http://groups.yahoo.com/group/lpc2000/message/3037
 
Newer EVBA7 boards will have this modification done at the factory.
 
Hugh @  <http://www.ashling.com/support/lpc2000/>
www.ashling.com/support/lpc2000/ 
Show quoted textHide quoted text
-----Original Message-----
From: David Roethig [mailto:daver@...] 
Sent: 03 November 2004 15:05
To: lpc2000@yahoogroups.com
Subject: Re: [lpc2000] JTAG Debugging problem



We have the Ashling board with the 2294 footprint adapter and
experienced problems with the Wiggler.
We were able to get the Wiggler to work by changing R39 from
10K to 1K.

The problem was that the RST line was too slow coming
out of reset.



theeuwke wrote:
> 
> Hi everyone,
> 
> Because my wiggler didn't work (see topic: Wiggler by theeuwke),
> i've got from an other department some nice equipment; a JEENI and an
> MAJIC from EPI. But stil, I can't get this stuff to work.
> First some info:
> 
> I have two boards; first one is an EVBA7 from Ashling;
> http://www.ashling.com/datasheets/DS266-EvKitLPC2000.html
> It has an LPC2106 microcontroller (ARM7TDMIS)
> 
> To debug with this board, I set the Secondary debug jumber on
> enabled, the primairy debug jumper on disabled, the onboard debug on
> disabled, and ISR on disabled. I flashed a program to enable the
> secondary JTAG port that was delivered with the board, but I also
> tried the one in the files section. I just connected the device with
> the JEENI and the MAJIC with a standard 20 pin connector, that commes
> from EPI. When I use the JEENI, and try to connect with GDB, it
> complanes that "Target World is Broken" ?. If I use Debugger from
> ARM, it says that the processor is Running, i've got the same problem
> with the wiggler. When I use the MAJIC, it says "RTCK is stopped or
> extremely slow.
> 
> The second board is a custom made board bassed on the LPC2292. It has
> a mini 10 pin header, with TDO connected, TDI, TCK connected to the
> header and 3v3 with a 33k resistor, TMS connected to the header, TRST
> to header and 3v3 by 100k resistor and SRST to the system reset.
> When I tried the JEENI, because it doen't use the RTCK, I connected
> to the ground with a 4k7 resistor, with the majic i just connect it.
> So everything is connected good i believe, and I measured all the
> inputs to the lpc, and the resets are going up and down propperly,
> tck gets there, and there goes data in, but there is nothing comming
> out. I tried to upload a program that implicit sets PINSEL2 to DEBUG,
> but it didn't help. I have still the same problems as the first board.
> What the hell am I doing wrong?
> 
> 
> 
> 
> 
> 
> *Yahoo! Groups Sponsor*
>
<http://us.ard.yahoo.com/SIG=129fm3jnj/M=281955.5530326.6602771.3001176/D=gr
oups/S=1706554205:HM/EXP=1099573468/A=2343726/R=0/SIG=12idnga58/*http://clk.
atdmt.com/VON/go/yhxxxvon01900091von/direct/01/
<http://us.ard.yahoo.com/SIG=129fm3jnj/M=281955.5530326.6602771.3001176/D=gr
oups/S=1706554205:HM/EXP=1099573468/A=2343726/R=0/SIG=12idnga58/*http://clk.
atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=1099487068145799>
&time=1099487068145799> 
> 
> 
> Get unlimited calls to
> 
> U.S./Canada
> 
>
<http://us.ard.yahoo.com/SIG=129fm3jnj/M=281955.5530326.6602771.3001176/D=gr
oups/S=1706554205:HM/EXP=1099573468/A=2343726/R=1/SIG=12idnga58/*http://clk.
atdmt.com/VON/go/yhxxxvon01900091von/direct/01/
<http://us.ard.yahoo.com/SIG=129fm3jnj/M=281955.5530326.6602771.3001176/D=gr
oups/S=1706554205:HM/EXP=1099573468/A=2343726/R=1/SIG=12idnga58/*http://clk.
atdmt.com/VON/go/yhxxxvon01900091von/direct/01/&time=1099487068145799>
&time=1099487068145799> 
> 
> 
> 
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
> 
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/lpc2000/
>        
>     * To unsubscribe from this group, send an email to:
>       lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>. 
> 
> 


Yahoo! Groups Sponsor	

ADVERTISEMENT
 
<http://us.ard.yahoo.com/SIG=1294pe6ba/M=315388.5543472.6613714.3001176/D=gr
oups/S=1706554205:HM/EXP=1099580743/A=2372354/R=0/SIG=12id813k2/*https://www
.orchardbank.com/hcs/hcsapplication?pf=PLApply&media=EMYHNL40F21004SS> click
here	
 
<http://us.adserver.yahoo.com/l?M=315388.5543472.6613714.3001176/D=groups/S=
:HM/A=2372354/rand=493684677> 	


  _____  

Yahoo! Groups Links


*	To visit your group on the web, go to:
http://groups.yahoo.com/group/lpc2000/
  

*	To unsubscribe from this group, send an email to:
lpc2000-unsubscribe@yahoogroups.com
<mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe> 
  

*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> . 




[Non-text portions of this message have been removed]

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.