jtag programming guruplug

[ml]

apologies for the dumb questions - i've bricked my guruplug, and am attempting to reflash it using the guruplug installer. running runme.sh gives me the following response:

root@ubuntu:~/guruplug-installer# ./runme.sh ../u-boot.bin
 ****     Preparing environment variables file ...
 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (Manufacturer: 0x071, Part: 0xc000, Version: 0xf)
Error: JTAG tap: feroceon.cpu             got: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Error: JTAG tap: feroceon.cpu expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Error: trying to validate configured JTAG chain anyway...
Warn : value captured during scan didn't pass the requested check:
Warn : captured: 0x00 check_value: 0x01 check_mask: 0x0F
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Error: timed out while waiting for target halted
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:
   
 ****   openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

I've tried using the reset button to restart the device with various timing on runme.sh - the following occurs if the reset button is held permanently, the following occurs:

dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: timed out while waiting for target halted
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:

can someone tell me what the timing requirement is please?

and out of interest - what's the error given with the reset button not held?

thanks!

[NewIT_James]

Hi ml,

Have a look at this post,

http://www.newit.co.uk/forum/index.php/topic,626.msg3646.html#msg3646

Reflashing Gurus involves some careful timing.

NewIT Technical

[ml]

thanks - i've had a look, the symptoms are the same - the suggestion it takes 500 attempts is a bit of a concern, i've spent the last hour trying and several yesterday - the idea of using a PC controlled PSU is very tempting.

Is there a set time from reset coming up to the device being available? not knowing anything about the JTAG interface isn't helping (hence my wishing to know what the reset button is changing), but the startup process must be defined, and as such be reproducible?

[NewIT_James]

Having spent a few hours with the same error myself this is the best I can offer at the moment.

Hit enter and power up the Guru at exactly the same time.

NewIT Technical

[ml]

ok. clearly i should keep trying.

what happens between reset, and recognition, that becomes non-recognition:

runme too late is:

info : JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (Manufacturer: 0x071, Part: 0xc000, Version: 0xf)
Error: JTAG tap: feroceon.cpu             got: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Error: JTAG tap: feroceon.cpu expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)

and

Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)


by understanding what's going on, a proper strategy can be chosen!

[ml]

for anyone interested, the "fix" was to reduce the jtag interface speed, at which point it all becomes repeatable.
from:
jtag_khz 2000

to:
jtag_khz 250

in the interface cfg file.

[NewIT_Marcus]

Thanks for the update. I had to do the same thing (although not down to 250) when I first started working on Sheevaplugs. I think that the root cause may have been my host O/S; I've upgraded a couple of versions of Ubuntu since then, and I'm sure I don't have the issue any more.

[tkteun]

No need to tamper with speed, the processor needs to be in halted state before flashing.

This happens a nanosecond after powering up or while holding the reset button, maybe openocd should reset the processor for us.

http://www.newit.co.uk/forum/index.php/topic,626.msg8181.html#msg8181

Thanks for the information, sorry your infrastructure makes me grave post.