A Brick is a brick

[stuffduff]

Got a sheevaplug for a project at work.  Model: 003-SP1001 SKU#: RD88F6281-BPLUG-A.

Took it home, put it on my network, traced the mac & found the IP, ssh'd in ok.

Wrote a little python ditty to report it's assigned IP to a server.

Brought it back to work, plugged it in, IP reported correctly, ssh'd in and started running top.

Figured I'd let it sit for a while to see if it got hot.

Ran two weeks w/o problems, slightly warm but not hot.

Came in this Monday morning and saw that there was no Ethernet activity.

Unplugged, replugged.  Single green light and no activity.

PSU checked out at 5.02 V.  Newer PSU so no brown glue or bulging capacitors.

Let sit over night and plugged it in, again no response.

Followed:

http://plugcomputer.org/plugforum/index.php?topic=3680.0

Tried the reinstall commands on Windows and Linux.

Connected power, mimiusb and usb stick to it and was able to set it up as COM6, puttyd in but no response.

On Windows I get:

C:\Documents and Settings\xxxx\Desktop\Sheevaplug\sheevaplug-installer-v1.0>r

unme.exe nand



 ****   Preparing environment variables file ...

reading uboot\uboot-env\uboot-dflt.txt

uboot\uboot-env\fw_setenv.exe baudrate 115200

CRC read error on uboot-env.bin: No error

uboot\uboot-env\fw_setenv.exe loads_echo 0

uboot\uboot-env\fw_setenv.exe ipaddr 10.4.50.165

uboot\uboot-env\fw_setenv.exe serverip 10.4.50.5

uboot\uboot-env\fw_setenv.exe rootpath /mnt/ARM_FS/

uboot\uboot-env\fw_setenv.exe netmask 255.255.255.0

uboot\uboot-env\fw_setenv.exe stdin serial

uboot\uboot-env\fw_setenv.exe stdout serial

uboot\uboot-env\fw_setenv.exe stderr serial

uboot\uboot-env\fw_setenv.exe console console=ttyS0,115200 mtdparts=nand_mtd:0xc

0000@0(uboot)ro,0x1ff00000@0x100000(root)

uboot\uboot-env\fw_setenv.exe mainlineLinux no

uboot\uboot-env\fw_setenv.exe CASset min

uboot\uboot-env\fw_setenv.exe enaMonExt no

uboot\uboot-env\fw_setenv.exe enaCpuStream no

uboot\uboot-env\fw_setenv.exe enaWrAllo no

uboot\uboot-env\fw_setenv.exe pexMode RC

uboot\uboot-env\fw_setenv.exe disL2Cache no

uboot\uboot-env\fw_setenv.exe setL2CacheWT yes

uboot\uboot-env\fw_setenv.exe disL2Prefetch yes

uboot\uboot-env\fw_setenv.exe enaICPref yes

uboot\uboot-env\fw_setenv.exe enaDCPref yes

uboot\uboot-env\fw_setenv.exe sata_dma_mode yes

uboot\uboot-env\fw_setenv.exe MALLOC_len 1

uboot\uboot-env\fw_setenv.exe ethprime egiga0

uboot\uboot-env\fw_setenv.exe netbsd_en no

uboot\uboot-env\fw_setenv.exe vxworks_en no

uboot\uboot-env\fw_setenv.exe bootargs_root root=/dev/nfs rw

uboot\uboot-env\fw_setenv.exe bootargs_end :::DB88FXX81:eth0:none

uboot\uboot-env\fw_setenv.exe image_name uImage

uboot\uboot-env\fw_setenv.exe bootcmd tftpboot 0x2000000 $(image_name);setenv bo

otargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):

$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig);  bootm 0x2000000;

uboot\uboot-env\fw_setenv.exe standalone fsload 0x2000000 $(image_name);setenv b

ootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end

) $(mvPhoneConfig); bootm 0x2000000;

uboot\uboot-env\fw_setenv.exe bootdelay 3

uboot\uboot-env\fw_setenv.exe disaMvPnp no

uboot\uboot-env\fw_setenv.exe ethaddr 00:50:43:4e:2a:14

uboot\uboot-env\fw_setenv.exe ethmtu 1500

uboot\uboot-env\fw_setenv.exe mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs

uboot\uboot-env\fw_setenv.exe mvNetConfig mv_net_config=(00:11:88:0f:62:81,0:1:2

:3),mtu=1500

uboot\uboot-env\fw_setenv.exe usb0Mode host

uboot\uboot-env\fw_setenv.exe yuk_ethaddr f0:ad:4e:00:09:c0

uboot\uboot-env\fw_setenv.exe nandEcc 1bit

uboot\uboot-env\fw_setenv.exe netretry no

uboot\uboot-env\fw_setenv.exe rcvrip 169.254.100.100

uboot\uboot-env\fw_setenv.exe loadaddr 0x02000000

uboot\uboot-env\fw_setenv.exe autoload no

uboot\uboot-env\fw_setenv.exe enaAutoRecovery yes

uboot\uboot-env\fw_setenv.exe ethact egiga0

reading uboot\uboot-env\uboot-nand-custom.txt

uboot\uboot-env\fw_setenv.exe bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstyp

e=ubifs

uboot\uboot-env\fw_setenv.exe mtdpartitions mtdparts=orion_nand:0x400000@0x10000

0(uImage),0x1fb00000@0x500000(rootfs)

uboot\uboot-env\fw_setenv.exe ethaddr f0:ad:4e:00:09:c0

uboot\uboot-env\fw_setenv.exe real_bootcmd setenv bootargs $(bootargs_console) $

(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000;

bootm 0x00800000

uboot\uboot-env\fw_setenv.exe bootargs_console console=ttyS0,115200

uboot\uboot-env\fw_setenv.exe bootcmd run recover1

uboot\uboot-env\fw_setenv.exe recover1 setenv mainlineLinux yes; setenv arcNumbe

r 2097; setenv bootcmd run recover2; saveenv; reset

uboot\uboot-env\fw_setenv.exe recover2 run recover3; setenv bootcmd $(real_bootc

md); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram

0 rw ramdisk=0x01100000,8M install_type=nand; bootm 0x00800000 0x01100000

uboot\uboot-env\fw_setenv.exe recover3 run recover4; nand erase clean 0x00100000

 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000

uboot\uboot-env\fw_setenv.exe recover4 usb start; fatload usb 0 0x00800000 uImag

e; fatload usb 0 0x01100000 initrd



 ****   Burning uboot and environment variables ... This will take few minutes .

..

 ****   When uboot.bin is written to NAND/SD, Disconnect and connect your mini U

SB cable

Open On-Chip Debugger 0.2.0 (2009-07-27-16:41) Release

$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd

.c $

For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS

2000 kHz

jtag_nsrst_delay: 200

jtag_ntrst_delay: 200

dcc downloads are enabled

Error: JTAG communication failure: check connection, JTAG interface, target powe

r etc.

Error: trying to validate configured JTAG chain anyway...

Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x00. tap=

feroceon.cpu pos=0 expected 0x1 got 0

Warn : Could not validate JTAG chain, continuing anyway...

Error: unexpected Feroceon EICE version signature

Error: unexpected Feroceon EICE version signature

Error: timed out while waiting for target halted

Runtime error, file "openocd\config\board\sheevaplug.cfg", line 21:

     ****       openocd FAILED

 ****   Is the mini USB cable connected?

 ****   Try powering down, then replugging the Sheevaplug

C:\Documents and Settings\xxxx\Desktop\Sheevaplug\sheevaplug-installer-v1.0>


On Linux I get:

It shows up as ttyUSB0 and I can connect to it and open a putty session, but it is deader than a doornail.

[xxxx@localhost uboot]# openocd -f openocd/config/board/sheevaplug.cfg -s openocd/config/ -c init -c sheevaplug_reflash_uboot_env -c sheevaplug_reflash_uboot -c exit
Open On-Chip Debugger 0.5.0-dev-00732-g859cccc (2011-02-03-10:16)
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
Error: No valid NAND flash driver found (0)
Available NAND flash controller drivers:
  nonce
  davinci
  lpc3180
  orion
  s3c2410
  s3c2412
  s3c2440
  s3c2443
  s3c6400
  imx27
  imx31
  at91sam9
  nuc910
sheevaplug_reflash_uboot_env
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
Error: unexpected Feroceon EICE version signature
Info : Halt timed out, wake up GDB.
Error: timed out while waiting for target halted
Runtime Error: openocd/config/board/sheevaplug.cfg:21:
in procedure 'sheevaplug_reflash_uboot_env'
in procedure 'sheevaplug_init' called at file "openocd/config/board/sheevaplug.cfg", line 117
in procedure 'wait_halt' called at file "openocd/config/board/sheevaplug.cfg", line 21
[xxxx@localhost uboot]#

Both systems 'see' a usb device but I cannot communicate with it.


Anything I'm missing in the Windows Errors?

Error: JTAG communication failure: check connection, JTAG interface, target powe

r etc.

Error: trying to validate configured JTAG chain anyway...

Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x00. tap=

feroceon.cpu pos=0 expected 0x1 got 0

Warn : Could not validate JTAG chain, continuing anyway...

Error: unexpected Feroceon EICE version signature

Error: unexpected Feroceon EICE version signature

Error: timed out while waiting for target halted

Or the Linux Errors:

Error: No valid NAND flash driver found (0)
Available NAND flash controller drivers:
  nonce
  davinci
  lpc3180
  orion
  s3c2410
  s3c2412
  s3c2440
  s3c2443
  s3c6400
  imx27
  imx31
  at91sam9
  nuc910
sheevaplug_reflash_uboot_env
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
Error: unexpected Feroceon EICE version signature
Info : Halt timed out, wake up GDB.
Error: timed out while waiting for target halted
Runtime Error: openocd/config/board/sheevaplug.cfg:21:
in procedure 'sheevaplug_reflash_uboot_env'
in procedure 'sheevaplug_init' called at file "openocd/config/board/sheevaplug.cfg", line 117
in procedure 'wait_halt' called at file "openocd/config/board/sheevaplug.cfg", line 21

Do I need a new Feroceon.cfg?

Error: No valid NAND flash driver found (0)

Is simething wrong in the sheevaplug.cfg file?

Can someone confirm that this brick is unbrickable?  Or possibly show me the error of my ways?

Feedback sincerely appreciated!

[marcus]

Did you ever use openocd / installer prior to the current problem? If so, did you run the same commands as you are running now, and was it successful then?

If this is the first time you've tried running the installer, linux host seems to be preferred, but 64 bit hosts - either linux or Windows - might be the cause the errors you seem to be having.

[stuffduff]

I had never tried openocd before.  With the exception of the python program and a crontab entry it was all original content.

The fact that the device is recognized as a usb device, but consistently fails attempts at serial/usb connections makes me think that the nand image may be completely gone and that I'm trying to reach a blank machine.

[radael]

When trying to use the Installer on a Windows 7, 64-bit machine, my attempt also ended with the messages:

  ****       openocd FAILED
  ****   Is the mini USB cable connected?

. . . However, I do not recall the messages about the JTAG chain and Feroceon EICE version signature (which appear in both your Windows and Linux reports).

A message in the Linux output also seems significant:

  Error: No valid NAND flash driver found (0)


It's been several weeks since I've waded through these forums, but I don't recall an error exactly like this one.  I recall the problems falling mainly into two categories -- the PSU, and attempting to change/upgrade the software.  With a few issues about poor mini-usb or SD card connectors.  Other than the PSU, not much about the system just failing.

If you did nothing to the box between the time when it was seen working and the time when it stopped, then this suggests some sort of one-off hardware issue.  On a whole, my board look acceptable, but those reports by some others about loose mini-usb, etc., suggest there may be variations in the quality of some individual units.

Just guessing, but I don't think this is a matter of configuration, or U-boot just quitting.  I suspect this may be an actual hardware error which would justify a replacement unit under the warranty.  Others may think differently.

Best of Luck

[Zectbumo]

A message in the Linux output also seems significant:

  Error: No valid NAND flash driver found (0)

I think I solved the NAND error in this conversation with myself.  Does this solve the issue?

http://www.plugcomputer.org/plugforum/index.php?topic=6041.0