Piotr Zbysinski - EP(H) ha scritto: > Complete JTAG spec (with IEEE1532 included) I have
(can send if someone
> needs) and know very well. The "secret" is not here,
unfortunately.
Reply by Doug Sutherland●November 7, 20052005-11-07
I would greatly appreciate a copy of the JTAG spec also.
Could you please send to doug@doug...
TIA,
Doug
Piotr wrote: > Complete JTAG spec (with IEEE1532 included) I have
> (can send if someone needs)
Reply by Tom Walsh●November 6, 20052005-11-06
Landrum Haddix wrote:
>Hi,
>
>I found a really hard to track down hardware problem today
>that was forcing the JTAG port to not work.
>
>I am using an LCP2138 and JTAG quit working after a board rev.
> You probably are looking at an early release of the LPC213x manual? The
"Rev 01 - 24 June 2005" issue of "LPC213x User Manual"
clearly documents
that P0.31 must not be pulled low during reset...
I do know that the manual prior to that revision date was rather terse
(missing data).
TomW
>We had pulled P0.31 down because it was the enable
for a 485
>transciever and needed to be low during reset.
>
>Turns out there is an 'undocumented feature' on some of the LPC
>parts including the 2138 that will disable JTAG if P0.31 is low during
>reset. We all know about RTCLK needing to be high during reset
>for JTAG because it's documented, but P0.31 functions exactly the
>same way.
>
>I think it all has to do with a obscure thing called the secondary JTAG
>port. I think for some of the series P0.31 functions like RTCLK on the
>2138 and must be low at reset to enable the JTAG port.
>Apperently it's still in the silicon even on the 2138 even though
it's
>not documented.
>
>Anyhow it was very obscure and if it weren't for a single message
>buried deeply on the Keil site I would not have found until I removed
>every change on the new rev.
>Landrum Haddix
>lhaddix@lhad...
>http://web.qx.net/lhaddix
>Yahoo! Groups Links
Piotr, this may explain some confusion: (this is a direct quote from the
J-link documentation from www.segger.com)
Quote:
6.4.1 How does flash programming via J-Link work ?
This requires extra code. This extra code typically downloads a program into
the RAM
of the target system, which is able to erase and program the flash. This
program is
called Ram code and "knows" how to program the flash; it contains an
implementation
of the flash programming algorithm for the particular flash. Different flash
chips
have different programming algorithms; the programming algorithm also
depends on
other things such as endianess of the target system and organization of the
flash
memory (e.g. 1*8 bits, 1 * 16 bits, 2*16 bits or 32 bits) The Ram code
requires data
to be programmed into the flash memory. There are 2 ways of supplying this
data:
Data download to RAM or data download via DCC.
6.4.2 Data download to RAM
The data (or part of it) is downloaded to an other part of the RAM of the
target system.
The Instruction pointer (R15) of the CPU is then set to the start address of
the
Ram code, the CPU is started, executing the RAM code. The RAM code, which
contains
the programming algorithm for the flash chip, copies the data into the flash
chip. The CPU is stopped after this. This process may have to be repeated
until the
entire data is programmed into the flash.
6.4.3 Data download via DCC
In this case, the RAM code is started as described above before downloading
any
data. The RAM code then communicates with the PC (via DCC, JTAG and J-Link),
transferring data to the target. The RAM code then programs the data into
flash and
waits for new data from the host. The WriteMemory functions of J-Link are
used to
transfer the RAM code only, but not to transfer the data. The CPU is started
and
stopped only once. Using DCC for communication is typically faster than
using Write-
Memory for RAM download since the overhead is lower.
6.4.4 Available options for flash programming
There are different solutions available to program internal or external
flashes connected
to ARM cores using J-Link. The different solutions have different fields of
application, but of course also some overlap.
End Quote.
>From: "Ake Hedman, eurosource"
<akhe@akhe...>
>Reply-To: lpc2000@lpc2...
>To: lpc2000@lpc2...
>Subject: Re: [lpc2000] JTAG commands are secret?
>Date: Fri, 04 Nov 2005 09:11:53 +0100
>
> > Is there anybody who know why uCs producers are so secretive?
>Yes this is very sad as well as strange behavior and typical for
>European management. They are all in the thinking that they have to get
>payed for everything that are developed in house. They don't have
the
>vision to see that they get a much bigger return by putting the
>information out in the open and let others improve it. The LPC family is
>the best I have seen for many years (I'm actually mainly a PIC user)
but
>knowing that this type of old thinking still exists in Philips makes me
>hold back from using them on all major designs. I talked to a rather big
>Swedish company last week and they liked the LPC more then the
>competition but selected the AVR ARM instead because of the same
>reasons. And in that case we talk about a lot of pieces.
>
>I really hope that a company like Philips that so often show technical
>excelens could mature and show marketing excelens to...
>
>/Ake
>
>--
> ---
>Ake Hedman (YAP - Yet Another Programmer)
>eurosource, Brattbergavägen 17, 820 50 LOS, Sweden
>Phone: (46) 657 413430 Cellular: (46) 73 84 84 102
>Company home: http://www.eurosource.se
>Kryddor/Te/Kaffe: http://www.brattberg.com
>Personal homepage: http://www.eurosource.se/akhe
>Automated home: http://www.vscp.org
>
Reply by Richard●November 5, 20052005-11-05
As a commercial vendor, I am less interested in Open Source tools but I can
wholeheartedly agree about low cost tools. One "weakness" of our $199
ARM
compiler is that there was no corresponding low cost flash programmer
tools. I went around pitching to different vendors for licensing their
technology. I told them that I don't need fancy stuff, just a simple way to
burn as many different types of flash as possible. It's amazing the kind of
deafening silence I get (I guess I am not much of a salesman). In the end,
we did find someone and we are now shipping a PAR JTAG w/ Windows flash
downloader for $175. More than I would like but still cheaper than other
solutions. I am negotiating with another very famous JTAG maker to see if I
can convince them for a lower cost (~$400-$500 *ouch I know* but it will be
USB) solution.
At 12:53 PM 11/4/2005, Piotr Zbysinski - EP\(H\) wrote: >...
>Sure, but if tools will be expensive, speed of rising will be small - in
>most "small" applications, not in industry. I don't see any
reason for
>paying 100$ or more for simple program for Flash programming via JTAG.
This
>is necessary for programming uCs like STR family, OKI ARM family and
older
>Atmel AT91.
>
> > Go and find all the "secrets" (e.g. check the ARM website
may be you
> > will find a JTAG spec),
>
>Complete JTAG spec (with IEEE1532 included) I have (can send if someone
>needs) and know very well. The "secret" is not here,
unfortunately.
>
> > then publish them and may be then even in
> > Poland ARM can become #1
>
>Hmmm, popularity of ARM is a problem of manufacturers not mine. I'd
like to
>develop simple JTAG Flash programmer only.
>
// richard (This email is for mailing lists. To reach me directly, please
use richard at imagecraft.com)
Reply by Landrum Haddix●November 5, 20052005-11-05
OK,
it's in the LPC213x users manual at June 2005, but wasn't in the
Nov 2004 version. My bad.
I don't know about the '38, but seems like it would be the same thing.
Unfortunately, they don't talk about it on the data sheet for the '48
Dan
_____
From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
Of Landrum Haddix
Sent: Friday, November 04, 2005 6:24 PM
To: lpc2000@lpc2...
Subject: [lpc2000] Another JTAG issue. Heads up
Hi,
I found a really hard to track down hardware problem today
that was forcing the JTAG port to not work.
I am using an LCP2138 and JTAG quit working after a board rev.
We had pulled P0.31 down because it was the enable for a 485
transciever and needed to be low during reset.
Turns out there is an 'undocumented feature' on some of the LPC
parts including the 2138 that will disable JTAG if P0.31 is low during
reset. We all know about RTCLK needing to be high during reset
for JTAG because it's documented, but P0.31 functions exactly the
same way.
I think it all has to do with a obscure thing called the secondary JTAG
port. I think for some of the series P0.31 functions like RTCLK on the
2138 and must be low at reset to enable the JTAG port.
Apperently it's still in the silicon even on the 2138 even though
it's
not documented.
Anyhow it was very obscure and if it weren't for a single message
buried deeply on the Keil site I would not have found until I removed
every change on the new rev.
Landrum Haddix
lhaddix@lhad... http://web.qx.net/lhaddix
Reply by Landrum Haddix●November 4, 20052005-11-04
Hi,
I found a really hard to track down hardware problem today
that was forcing the JTAG port to not work.
I am using an LCP2138 and JTAG quit working after a board rev.
We had pulled P0.31 down because it was the enable for a 485
transciever and needed to be low during reset.
Turns out there is an 'undocumented feature' on some of the LPC
parts including the 2138 that will disable JTAG if P0.31 is low during
reset. We all know about RTCLK needing to be high during reset
for JTAG because it's documented, but P0.31 functions exactly the
same way.
I think it all has to do with a obscure thing called the secondary JTAG
port. I think for some of the series P0.31 functions like RTCLK on the
2138 and must be low at reset to enable the JTAG port.
Apperently it's still in the silicon even on the 2138 even though
it's
not documented.
Anyhow it was very obscure and if it weren't for a single message
buried deeply on the Keil site I would not have found until I removed
every change on the new rev.
Landrum Haddix
lhaddix@lhad... http://web.qx.net/lhaddix
Reply by Eric Engler●November 4, 20052005-11-04
--- In lpc2000@lpc2..., "Piotr Zbysinski - EP\(H\)"
<piotr.zbysinski@e...> wrote: > I'd like to
> develop simple JTAG Flash programmer only.
Did you look at the open source jtager project at SourceForge?
