That's one of my greatest doubts. I have seen circuit topologies that use
no pull-up resistors for the JTAG pins, topologies with pull-ups in TDI, TDO,
TMS and TRST_N, some with pull-ups for RTCK and TCK and others with pull-down
resistors for these two last. And all claim to work. I designed based in MCB2300
from Keil, but their topology and the ones used in other sourcebooks
(lpc-ARM-book_srn.pdf and lpc-arm-book_rev10-screen.pdf) don't agree with
each other. Since CrossWorks and CrossConnect can program to MCB2300 (and I used
the same topology) I think they'll work almost like plug 'n play.
--- On Tue, 5/13/08, Paul Curtis wrote:
> From: Paul Curtis
> Subject: RE: [lpc2000] Trouble with programming
> To: l...
> Date: Tuesday, May 13, 2008, 3:49 PM
> Hi,
>
> > Any ideas? Like using a transistor to generate a
> strong reset? Or
> > should I go to Voltage Supervisor?
>
> I'm no expert. Why not just copy what some reference
> boards have done which
> are known to work... Isn't that what they're there
> for?
>
> --
> Paul Curtis, Rowley Associates Ltd
> http://www.rowley.co.uk
> CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3
> processors
>
> Any ideas? Like using a transistor to generate a
strong reset? Or
> should I go to Voltage Supervisor?
I'm no expert. Why not just copy what some reference boards have done
which
are known to work... Isn't that what they're there for?
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
Reply by ●May 13, 20082008-05-13
Any ideas? Like using a transistor to generate a strong reset? Or should I go to
Voltage Supervisor?
--- On Tue, 5/13/08, Paul Curtis wrote:
> From: Paul Curtis
> Subject: RE: [lpc2000] Trouble with programming
> To: l...
> Date: Tuesday, May 13, 2008, 3:15 PM
> Hi,
>
> > -----Original Message-----
> > From: l...
> [mailto:l...] On
> > Behalf Of Luiz Roberto Guimars
> > Sent: 13 May 2008 14:25
> > To: l...
> > Subject: Re: [lpc2000] Trouble with programming
> >
> > I called victory too soon.
> > I'm using a simple resistor-capacitor reset
> system, event with that
> > (and reset level staying above 2.2V) the RSTOUT pin
> don't get off 0V.
> > In the first connect attempt, CrossWorks returns
> Target not responding.
> > Even if the connect occurs (in a 5% rating) I get
> "Cannot halt target
> > at reset" when I attempt to download code.
>
> Sounds like your target JTAG/reset has serious problems.
>
> --
> Paul Curtis, Rowley Associates Ltd
> http://www.rowley.co.uk
> CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3
> processors
>
>
>
>
>
Reply by Paul Curtis●May 13, 20082008-05-13
Hi,
> -----Original Message-----
> From: l... [mailto:l...] On
> Behalf Of Luiz Roberto Guimars
> Sent: 13 May 2008 14:25
> To: l...
> Subject: Re: [lpc2000] Trouble with programming
>
> I called victory too soon.
> I'm using a simple resistor-capacitor reset system, event with that
> (and reset level staying above 2.2V) the RSTOUT pin don't get off 0V.
> In the first connect attempt, CrossWorks returns Target not responding.
> Even if the connect occurs (in a 5% rating) I get "Cannot halt target
> at reset" when I attempt to download code.
Sounds like your target JTAG/reset has serious problems.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
Reply by ●May 13, 20082008-05-13
I called victory too soon.
I'm using a simple resistor-capacitor reset system, event with that (and
reset level staying above 2.2V) the RSTOUT pin don't get off 0V. In the
first connect attempt, CrossWorks returns Target not responding. Even if the
connect occurs (in a 5% rating) I get "Cannot halt target at reset" when I
attempt to download code.
--- On Mon, 5/12/08, Leon wrote:
> From: Leon
> Subject: Re: [lpc2000] Trouble with programming
> To: l...
> Date: Monday, May 12, 2008, 6:56 PM
> ----- Original Message -----
> From: "Paul Curtis"
> To:
> Sent: Monday, May 12, 2008 6:26 PM
> Subject: RE: [lpc2000] Trouble with programming
> > Hi,
> >
> >> > (a) Have you connected up RTCK to the JTAG
> header? If yes,
> >> > use adaptive
> >> > clocking ALWAYS.
> >>
> >> Yes, it's connected.
> >>
> >> > (b) There is no point using non-adaptive
> clocking because
> >> > core frequency
> >> > will change and the JTAG adapter doesn't
> know about it;
> >> > if this happens it's
> >> > quite likely that the target can't be
> identified as the
> >> > clocking will be too
> >> > fast.
> >> >
> >> > A divider of 100 will be about 6MHz/100 > 60kHz which is
> >> > too fast if you're
> >> > clocking at 32kHz for example.
> >>
> >> I'm using a 12MHz clock for the core.
> >> And every time that I use adaptive clocking, the
> CrossWorks says "The
> >> RTCK is not responding, disable "Adaptive
> Clocking" mode."
> >
> > If you've designed your own board and RTCK is
> connected and the
> > CrossConnect
> > says it's not working, then I suggest you check
> your hardware.
>
> Make sure that the LPC leads are actually connected.
> I've had problems with
> them looking OK, but the JTAG doesn't work. Going over
> tham again with a
> soldering iron fixed the problem.
>
> Leon
> --
> Leon Heller
> Amateur radio call-sign G1HSM
> Yaesu FT-817ND transceiver
> Suzuki SV1000S motorcycle
> l...@btinternet.com
> http://webspace.webring.com/people/jl/leon_heller/
>
Reply by ●May 12, 20082008-05-12
Thanks Leon and Paul,
Connected to LPC, now download program. Damn those soldering problems.
--- On Mon, 5/12/08, Leon wrote:
> From: Leon
> Subject: Re: [lpc2000] Trouble with programming
> To: l...
> Date: Monday, May 12, 2008, 6:56 PM
> ----- Original Message -----
> From: "Paul Curtis"
> To:
> Sent: Monday, May 12, 2008 6:26 PM
> Subject: RE: [lpc2000] Trouble with programming
> > Hi,
> >
> >> > (a) Have you connected up RTCK to the JTAG
> header? If yes,
> >> > use adaptive
> >> > clocking ALWAYS.
> >>
> >> Yes, it's connected.
> >>
> >> > (b) There is no point using non-adaptive
> clocking because
> >> > core frequency
> >> > will change and the JTAG adapter doesn't
> know about it;
> >> > if this happens it's
> >> > quite likely that the target can't be
> identified as the
> >> > clocking will be too
> >> > fast.
> >> >
> >> > A divider of 100 will be about 6MHz/100 > 60kHz which is
> >> > too fast if you're
> >> > clocking at 32kHz for example.
> >>
> >> I'm using a 12MHz clock for the core.
> >> And every time that I use adaptive clocking, the
> CrossWorks says "The
> >> RTCK is not responding, disable "Adaptive
> Clocking" mode."
> >
> > If you've designed your own board and RTCK is
> connected and the
> > CrossConnect
> > says it's not working, then I suggest you check
> your hardware.
>
> Make sure that the LPC leads are actually connected.
> I've had problems with
> them looking OK, but the JTAG doesn't work. Going over
> tham again with a
> soldering iron fixed the problem.
>
> Leon
> --
> Leon Heller
> Amateur radio call-sign G1HSM
> Yaesu FT-817ND transceiver
> Suzuki SV1000S motorcycle
> l...@btinternet.com
> http://webspace.webring.com/people/jl/leon_heller/
>
Reply by Leon●May 12, 20082008-05-12
----- Original Message -----
From: "Paul Curtis"
To:
Sent: Monday, May 12, 2008 6:26 PM
Subject: RE: [lpc2000] Trouble with programming > Hi,
>
>> > (a) Have you connected up RTCK to the JTAG header? If yes,
>> > use adaptive
>> > clocking ALWAYS.
>>
>> Yes, it's connected.
>>
>> > (b) There is no point using non-adaptive clocking because
>> > core frequency
>> > will change and the JTAG adapter doesn't know about it;
>> > if this happens it's
>> > quite likely that the target can't be identified as the
>> > clocking will be too
>> > fast.
>> >
>> > A divider of 100 will be about 6MHz/100 = 60kHz which is
>> > too fast if you're
>> > clocking at 32kHz for example.
>>
>> I'm using a 12MHz clock for the core.
>> And every time that I use adaptive clocking, the CrossWorks says "The
>> RTCK is not responding, disable "Adaptive Clocking" mode."
>
> If you've designed your own board and RTCK is connected and the
> CrossConnect
> says it's not working, then I suggest you check your hardware.
Make sure that the LPC leads are actually connected. I've had problems with
them looking OK, but the JTAG doesn't work. Going over tham again with a
soldering iron fixed the problem.
> > (a) Have you connected up RTCK to the JTAG header?
If yes,
> > use adaptive
> > clocking ALWAYS.
>
> Yes, it's connected.
>
> > (b) There is no point using non-adaptive clocking because
> > core frequency
> > will change and the JTAG adapter doesn't know about it;
> > if this happens it's
> > quite likely that the target can't be identified as the
> > clocking will be too
> > fast.
> >
> > A divider of 100 will be about 6MHz/100 = 60kHz which is
> > too fast if you're
> > clocking at 32kHz for example.
>
> I'm using a 12MHz clock for the core.
> And every time that I use adaptive clocking, the CrossWorks says "The
> RTCK is not responding, disable "Adaptive Clocking" mode."
If you've designed your own board and RTCK is connected and the
CrossConnect
says it's not working, then I suggest you check your hardware.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
Reply by ●May 12, 20082008-05-12
> (a) Have you connected up RTCK to the JTAG header?
If yes,
> use adaptive
> clocking ALWAYS.
Yes, it's connected.
> (b) There is no point using non-adaptive clocking
because
> core frequency
> will change and the JTAG adapter doesn't know about it;
> if this happens it's
> quite likely that the target can't be identified as the
> clocking will be too
> fast.
>
> A divider of 100 will be about 6MHz/100 = 60kHz which is
> too fast if you're
> clocking at 32kHz for example.
I'm using a 12MHz clock for the core.
And every time that I use adaptive clocking, the CrossWorks says "The RTCK is
not responding, disable "Adaptive Clocking" mode."
Is there any changes in the MCB2300 keil design about RTCK?
> I recently acquired a CrossConnect for ARM, along
with CrossWorks. I
> have developped a prototype board using the same JTAG system as MCB2300
> from keil. The board power is working fine, at 3.3V. However, every
> time I try to program (fresh programming) the LPC2368, I allways get
> the "Cannot identify target" annoying message. I have already tryed
> with 1, 10 and 100 clock dividers, every one with and without Adaptive
> Clocking. With an oscilloscope, the signals from TDI, TDO, TMS and
> nRST are changing. The RTCK and TCK, however, are not. From the RSTOUT
> pin, I can see the device isn't in reset state.
> Any suggestions?
(a) Have you connected up RTCK to the JTAG header? If yes, use adaptive
clocking ALWAYS.
(b) There is no point using non-adaptive clocking because core frequency
will change and the JTAG adapter doesn't know about it; if this happens
it's
quite likely that the target can't be identified as the clocking will be
too
fast.
A divider of 100 will be about 6MHz/100 = 60kHz which is too fast if
you're
clocking at 32kHz for example.
