Hello,
I have connected the JTAGKey-Tiny directly to the Colibri board (without
buffers) as Marek suggested but the situation remained the same. After
'reset' or 'flash info 0' I get the following error:
//> reset
JTAG tap: pxa270.cpu tap/device found: 0x79265013 (mfg: 0x009, part:
0x9265, ver: 0x7)
Failed to receiving data from debug handler after 1000 attempts
time out writing RX register
> flash info 0
time out writing RX register
auto_probe failed -302
Command handler execution failed
in procedure 'flash'
I have checked the reset signals and I have seen the followings:
0ms --- trst asserted (pulled down)
1ms --- srst asserted
2ms --- trst released
251ms --- srst released
551ms --- srst asserted
553,2ms --- srst released
Is this normal?
I have also seen that after switching on the board and starting openocd,
the target it in 'unknown' state:
> targets
TargetName Type Endian TapName State
-- ------------------ ---------- ------ ------------------ ------------
0* pxa270.cpu xscale little pxa270.cpu unknown
Thanks a lot for any ideas/hints!
Áron
I also changed for the git version of openocd (checked out on sep. 07.)
and compiled it with the debug option enabled.
2010-09-06 10:33 keltezéssel, Marek Vasut írta:
Dne Po 6. září 2010 08:59:21 Takács Áron napsal(a):
Thanky you, Marek!
Yes I use a Colibri board. Bypassing the buffers needs some HW hacking
but I'll try it. Thank you!
Keep the DAMNED CC !!
You don't need any hardware hacking, you can just connect the jtag to the CPU
card directly, check the Toradex datasheets and schematics for more details.
Áron
2010-09-06 08:53 keltezéssel, Marek Vasut írta:
Dne Po 6. září 2010 08:50:09 Takács Áron napsal(a):
Hello,
Hi, keep the CC please
thanks for the answers of Wookey and Marek!
You are right, marek, there are buffers on the board. I have tried to
increase the reset delays (jtag_nsrst_delay, jtag_ntrst_delay 250) and
also the timeout value in xscale.c:409 and :499, but the situation
remained the same.
Any ideas what to try now? Thank you!
You use colibri board, right? Either try a different JTAG adapter or
connect yours directly to the CPU card (there's that white strap
connecting the JTAG on the card to the board ... you can use that to tap
directly on the CPU JTAG pins).
Cheers
Áron
2010-09-03 21:44 keltezéssel, Marek Vasut írta:
Dne Pá 3. září 2010 16:46:59 Wookey napsal(a):
+++ Takács Áron [2010-09-03 16:15 +0200]:
Hi,
I want to use openocd to reflash PXA270 board (Colibri by Toradex). I
am using JTAGKey-Tiny interface (by Amontec). I can connect the board
but I always get the error message:
'time out writing RX register'. Here is the output for 'reset' and
'flash info 0':
We've used openocd with amontec jtagkey-tiny and pxa270 (balloonboard)
successfully for some time now. It works since 0.3.1 and is also fine
with 0.4. You might find it useful to compare your config with ours:
http://balloonboard.org/trac/browser/balloon/trunk/utils/openocd
we have at least one extra pxa CPUID which should be upstreamed:
http://balloonboard.org/trac/browser/balloon/trunk/utils/openocd/targe
t/ pxa 270updated.cfg
but that's not going to make any difference, assuming you are seeing
the device.
The rest of the config looks OK to me, but I only checked quickly
It might be the colibri board buffer logic that causes trouble. There
are additional buffers on the baseboard.
I use a custom FT2232 based dongle compatible with amontec jtagkey, but
I heard people had trouble with original amontec dongles and colibri
boards.
> reset
JTAG tap: pxa270.cpu tap/device found: 0x79265013 (mfg: 0x009, part:
0x9265, ver: 0x7)
Failed to receiving data from debug handler after 1000 attempts
time out writing RX register
# set jtag_nsrst_delay to the delay introduced by your reset circuit
# the rest of the needed delays are built into the openocd program
jtag_nsrst_delay 260
# set the jtag_ntrst_delay to the delay introduced by a reset circuit
# the rest of the needed delays are built into the openocd program
jtag_ntrst_delay 250
Try upping these numbers? I know that Marvell parts have different
timing to Intel parts in reset. Bit of a long short but worth a try.
Wookey
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
