• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Sheevaplug bricked - uboot still working, please help  (Read 1922 times)
jakblak
Newbie
*

Karma: 0
Posts: 16


View Profile
« on: February 07, 2012, 04:31:07 AM »

Hi All, my sheeva bricked after trying to update to ubuntu 11 or so (I know, I am an idiot, I should have read the forum before upgrading since this is not working)

So, I get currently:
Code:
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address b368
mmcblk0: mmc0:b368 SDC   7.46 GiB
 mmcblk0: p1
IP-Config: Complete:
     device=eth0, addr=192.168.0.77, mask=255.255.255.0, gw=192.168.0.11,
     host=DB88FXX81, domain=, nis-domain=(none),
     bootserver=192.168.0.11, rootserver=192.168.0.11, rootpath=
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p1): using internal journal
EXT3-fs (mmcblk0p1): recovery complete
EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:1.
Freeing init memory: 156K
eth0: link up, 1000 Mb/s, full duplex, flow control disabled

sheevainstaller does not work for me on on two different Linux boxes :-(
I installed php5-cli and libftdi1. lsusb shows only 406:1060 (or so, not the one with 9...)
Code:
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469:
     ****       openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

on one of the linux boxes I get:
Code:
openocd[2359]: segfault at 80 ip 0058b50b sp bfdffdcc error 4 in libc-2.11.1.so[54b000+153000]
how to get my sheevaplug to life again?
« Last Edit: February 07, 2012, 04:33:01 AM by jakblak » Logged

jakblak
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #1 on: February 07, 2012, 04:49:33 AM »

above is when I add on uBoot

Code:
setenv bootargs_root=console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) root=/dev/mmcblk0p1 rw,noatime ip=192.168.0.77:192.168.0.11:192.168.0.11:255.255.255.0:DB88FXX81:eth0:none  init=/bin/sh

boot

by removing the init=/bin/sh I get following
Code:
EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:1.
Freeing init memory: 156K
init: illegal runlevel: rw,noatime
Try `init --help' for more information.
Kernel panic - not syncing: Attempted to kill init!
[<c0034724>] (unwind_backtrace+0x0/0xe0) from [<c03ffba0>] (panic+0x58/0x17c)
[<c03ffba0>] (panic+0x58/0x17c) from [<c0048ca4>] (do_exit+0x64/0x728)
[<c0048ca4>] (do_exit+0x64/0x728) from [<c00496b0>] (do_group_exit+0xb8/0xec)
[<c00496b0>] (do_group_exit+0xb8/0xec) from [<c00496f4>] (sys_exit_group+0x10/0x18)
[<c00496f4>] (sys_exit_group+0x10/0x18) from [<c002faa0>] (ret_fast_syscall+0x0/0x2c)
eth0: link up, 1000 Mb/s, full duplex, flow control disabled


on both it stops booting after eth0....

any help is much appreciated
Logged

Juanisan
Newbie
*

Karma: 0
Posts: 20


View Profile
« Reply #2 on: February 07, 2012, 11:41:45 PM »


Try seting the env parameters back to what your documentation says.

SheevaPlug Development Kit - USB Flash Recovery from U-Boot-Rev1.2.pdf
Page 3
Logged

jakblak
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #3 on: February 08, 2012, 02:33:05 AM »

Hi
I did not change the bootenv's permanentaly, but temporary (so no saveenv was performed)

In the meanwhile, I downloaded the sheeva installer, extracted the rootfs which is included in the installer directory and copied over to a new mmc. The new mmc is working fine (missing indeed some modules, but easy to fix). but my old MMC not. Even if I overwrite the content of the filesystem of the old MMC.

What are the minimus requirements to boot a new MMC up if uboot is still working like in my case ?

1. /sbin/init
2. /dev
what else?

I tried also the debian version which can be found here anywhere in the forum. This works also, but after doing a apt-get upgrade I receive for every command: "Illegal instruction".
which rootfs is safe to use with the sheeva and have more chance to get upgrades? Ubuntu really sucks due to theier new updates which does not work with the sheeva anymore :-( !

Thanks
J!
Logged

Juanisan
Newbie
*

Karma: 0
Posts: 20


View Profile
« Reply #4 on: February 08, 2012, 03:22:07 AM »

Yes "Illegal Instruction" means your cpu isn't supported.

I couldn't tell you what to do in debian as I use armedslack on my sheeva/guru/dockstar plugs.

 http://www.armedslack.org/

If you are interested, these are armedslack (Slackware for ARM) installation instructions which may or may not  help with your current situation or help consider switching. 
http://ftp.slackware.org.uk/armedslack/armedslack-current/INSTALL_KIRKWOOD.TXT
Logged

jakblak
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #5 on: February 08, 2012, 05:52:18 AM »

which distribution would you or anyone else recommend which will work on this sheeva and also will have future updates (I know, noone can say for sure, but at the current situation.. ect)

I read anywhere debian, but this doesnt seem to be true due to "illegal instruction" problem...

thanks
J
Logged

Pages: [1]
Print
Jump to: