Sheeva Plug now doing absolutely nothing

[jammer]

Hi,

Been playing around with my sheeva plug and I think I finally "bricked" it... I am unable to get Installer 1.0 to help, so figured I'd ask the experts. Everything worked fine until I followed the directions here: http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html.

I attempted a uBoot upgrade via USB... Everything went smoothly, but at the end I got a FAT checksum error... From then on only the green light comes on and the serial USB port is unresponsive...

Been trying to use Sheevaplug Installer 1.0, but not having much luck with that... I'm on Ubuntu 9.10 64bit... When I plug in the Sheevaplug, Ubuntu finds it and assigned it ttyUSB0 (as one would expect)... Here is what I get when I run the runme.php:

****   Burning uboot and environment variables ... This will take few minutes ...
openocd/openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory
 ****   openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

Already have libftdi1. One thing I did notice is that to get openocd to run I have to refer to it as /usr/bin/openocd... Can't just do ./openocd.....? If I run a sudo /usr/bin/openocd -f ./board/sheevaplug.cfg I get this:

$ sudo /usr/bin/openocd -f ./board/sheevaplug.cfg
Open On-Chip Debugger 0.2.0-in-development (2009-06-30-01:49) svn:r2403


BUGS? Read /usr/share/doc/openocd/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : JTAG Tap/device matched

So I'm thinking that openocd 'can' find it, just the script assumes a PATH environment I don't have....



Ideas, further info I need to provide?


Thanks!!!!

[mgillespie]

Firstly, get the statically linked openocd (see the Installer 1.0 thread for the attachment), that will totally rule out any library problems, and fixes many issues.

Secondly, make sure your have edited the config file if you have a new plug, with the new USB Vendor/DeviceID.

[jammer]

OK, maybe on to something here... I looked at the README file and it says to edit the uboot-custom.txt file... Where is that? It was not included in the installer 1.0 tarball... I can create one if I know the format.......

[jammer]

OK, uninstalled openocd and ftdi downloaded from ubuntu repository. Followed the directions here: http://www.openplug.org/plugwiki/index.php/Build_OpenOCD. Installed everything from source... Now, something has changed as runme.php now says this:

****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.3.1 (2009-11-14-13:28)
$URL$
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
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Warn : use 'feroceon.cpu' as target identifier, not '0'
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
Error: couldn't bind to socket: Address already in use
 ****   openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug



?

[jammer]

OK, looks like I got past this one... I'll have to do more troubleshooting as all I did to get past the "Socket already in use" was reboot... I now see uboot via termonal, but now have a kernel panic... I'll search the posts to see if I can find the answer to this one........


lib80211: common routines for IEEE802.11 drivers
rtc-mv rtc-mv: setting system clock to 2040-09-27 01:34:39 UTC (2232322479)
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            4096 mtdblock0 (driver?)
1f01          519168 mtdblock1 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[<c00309c0>] (unwind_backtrace+0x0/0xe0) from [<c003db50>] (panic+0x50/0x120)
[<c003db50>] (panic+0x50/0x120) from [<c0008ec0>] (mount_block_root+0x1d4/0x214)
[<c0008ec0>] (mount_block_root+0x1d4/0x214) from [<c000908c>] (prepare_namespace+0x90/0x1c4)
[<c000908c>] (prepare_namespace+0x90/0x1c4) from [<c0008734>] (kernel_init+0xc0/0xec)
[<c0008734>] (kernel_init+0xc0/0xec) from [<c0040b3c>] (do_exit+0x0/0x6ac)

[mgillespie]

OK, maybe on to something here... I looked at the README file and it says to edit the uboot-custom.txt file... Where is that? It was not included in the installer 1.0 tarball... I can create one if I know the format.......

Don't try following the instructions, they are messed up beyond belief.   You may as well follow the installation instructions for Microsoft Word, they would be just as relevant!!!