eSata Sheevaplug does not enter u-boot

Hello,

I just got a brand new esata Sheeva plug. I installed debian on it, following the instructions from cyrius. Everything worked fine, I did NOT upgrade u-boot. I also did some warm reboots, and it works great.

Now, once I did a cold reboot by removing the power, the sheeva does not even enter u-boot ~~in most cases~~ (it works again if I remove power for over 10-15 minutes). So I cannot see any output on the usb console. If it manages to enter u-boot, I can start debian without a problem.

To debug the porblem, I tried connecting via openocd:

When there is an empty console, no u-boot and a green LED, openocd fails with:

Code:

$ sudo openocd -f /usr/local/share/openocd/scripts/board/sheevaplug.cfg
Open On-Chip Debugger 0.5.0-dev-00949-gac43d7a (2011-07-08-12:01)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
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'
sheevaplug_load_uboot
Info : clock speed 2000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: feroceon.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
Error: unexpected Feroceon EICE version signature

While, if u-boot is entered, I do have a red and blue LED and it connects:

Code:

$ sudo openocd -f /usr/local/share/openocd/scripts/board/sheevaplug.cfg
Open On-Chip Debugger 0.5.0-dev-00949-gac43d7a (2011-07-08-12:01)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
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'
sheevaplug_load_uboot
Info : clock speed 2000 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit

I guess my CPU does not come up when I connect power, right? I also have an other sheevaplug which once had a failed PSU. Put this beast seems to have power, and is brand new!

Any advice?

mabl

UPDATE:

If it boot's that's the output:

Code:

__ __ _ _
   | \/ | __ _ _ ____ _____| | |
   | |\/| |/ _` | '__\ \ / / _ \ | |
   | | | | (_| | | \ V / __/ | |
   |_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Jul 14 2009 - 06:46:57) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CF120

Soc: MV88F6281 Rev 3 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Flash: 0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled

USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0
Marvell>>

UPDATE2:
I just compiled my own uboot version based on git://git.denx.de/u-boot-marvell.git it shows the same behaviour.
If I let the sheeva rest without power for 10 minutes, it works again until i try to cold boot again.

I strongly guess this is a hardware problem.