Error: JTAG scan chain interrogation failed: all zeroes

[tjoe]

Hello,

I bricked my sheevaplug by that I mean I used to get the wonderfull 'Marvell >>' prompt when connecting to the plug console,
but not anymore, now the screen just stays blank.

I tried to revive it from linux 64 bits, 32 bits and even windows xp, but I always get one error or another  from openocd.

Q1: Is there a easy way to revive the plug that does not involve openocd ?
Q2: What's the problem with the output below ?
it looks like it can communicate to the device since it get the deviceid and serial number,
but what about that 'all zeroes' error, what does it mean ?

Code:

$ sudo /usr/local/bin/openocd -f /usr/local/share/openocd/scripts/board/sheevaplug.cfg  -c init -c sheevaplug_reflash_uboot
Open On-Chip Debugger 0.5.0-dev-00220-gf32492c (2010-05-07-16:49)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.berlios.de/doc/doxygen/bugs.html
2000 kHz
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Warn : use 'feroceon.cpu' as target identifier, not '0'
Info : device: 4 "2232C"
Info : deviceID: 18446744072074337935
Info : SerialNumber: FTS00D6A A
Info : Description: SheevaPlug JTAGKey FT2232D B A
Info : clock speed 2000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Command handler execution failed
Warn : jtag initialization failed; try 'jtag init' again.
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
Error: unexpected Feroceon EICE version signature
Warn : target was in unknown state when halt was requested
Info : Halt timed out, wake up GDB.
Error: timed out while waiting for target halted
Command handler execution failed

[metrotrak]

+1

Same symptoms for me.

TJoe, did you resolve this, and how???

Thanks!

[MoeDee]

Hello!


I do have the exact same issue.. however the first time I could get the JTAG to work.. put the original uboot.bin on .. with ./runme.sh uboot.bin.

however still there was no serial consol.. only ONE LED lit on top.. and system did not boot up like beeing able to use WiFi or ETH
any time I tried counlessly including power cycles, USB unplug and hand stands, etc -
No Success - yet I do see that avery try using the JTAG the PLUG is flickering all the LED's as when you press the RESET button.
I contacted GlobalScale - I will post results if any..

Any success tjoe with your issue - anyone?

[tjoe]

No guys,  the plug has been gathering dust for a while.
now that I have a bit more time I hope I can bring it back to life.

[tjoe]

Let's try to proceed logically 
here are the 3 hypothesis I came up with that could explain why it is not working

1. openocd or libftd2xx have not been compiled with the right options
2. the config files for openocd are not correct
3. there is a problem with the JTAG cable or the plug

Concerning 1, I doubt I have a problem with openocd or libftd2xx because
when I run openocd I can see it can talk to the plug, it gets the DeviceID
and the SerialNumber, the LEDs on the network port of the device are also flashing.
I guess that means that openocd and libftd2xx are okay.

I think the culprit is number 2,  I notice that those config files are different depending on where
you get them from and reading the posts on the forum it often came down to changing a parameter
in one of those:
interface/sheevaplug.cfg
board/sheevaplug.cfg
target/feroceon.cfg

I would like to review each warn/error message one by one
and see if someone can give us some insight on what to do to get rid of each one.

Warn : use 'feroceon.cpu' as target identifier, not '0'

could it be that some parameter in 'target/feroceon.cfg' could help us get rid of this one ?

Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.

Not sure what this one means, maybe it's just because uboot is trashed on the plug ?

Warn : jtag initialization failed; try 'jtag init' again.

Error: unexpected Feroceon EICE version signature

Warn : target was in unknown state when halt was requested

Error: timed out while waiting for target halted

I think the last errors are related to the sheevaplug_init function in 'board/sheevaplug.cfg':

       
        jtag_reset 0 1
        feroceon.cpu arp_examine
        halt 0
        jtag_reset 0 0
        wait_halt

is that sequence correct ?

[Dammuozz]

I think I've got another stucked plug...

I was messin' round with the u-boot and after a reboot I couldn't even get a serial connection...

I really need my plug back...there's my site database on the NAND!!!


please any help would be appreciated!

dammuozz