Sheevaplug installer - version 1.0

[draimus]

You know I didn't even see the line "Ignoring serial port reserved for JTAG" in the dmesg output I posted. 

That's got to be some stupid udev or driver problem.  I'll work that out.

Though like I said I did get a later uboot installed (I did use the tftp method).  My original intent was to get a workable OS back on the NAND flash because originally all the plug does start uboot then reset because it doesn't like what it sees.   With the 3.4.27 patched uboot it comes up, reads "something" from NAND and then drops to the uboot console.

How I got here originally is fuzzy, I believe I had a working OS on the NAND (I think debian; used Martin Michlmayr's blog posts to get it on there).  At some point I think I tried to upgrade the linux kernel and through various experiments got it installed into NAND, but uboot obviously didn't like what I put there so I ended up with a non-bootable OS.

I was hoping the sheeva-installer would flash the NAND back to a known good state (including the OS on NAND).

[Kamikaze321]

Sorry for the confusion, I tried the whole installation again with ubi0, so right now I have ubi0 as you see below

Code:

Marvell>> printenv
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
mtdpartitions=mtdparts=orion_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
ethaddr=00:50:43:01:69:8B
real_bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootargs_console=console=ttyS0,115200
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand; bootm 0x00800000 0x01100000
recover3=run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
recover4=usb start; fatload usb 0 0x00800000 uImage; fatload usb 0 0x01100000 initrd
arcNumber=2097
bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no
bootargs=console=ttyS0,115200 mtdparts=orion_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
filesize=32D62A

Environment size: 2192/131068 bytes
Marvell>>

When running recover3 again I get

Code:

Marvell>> run recover3
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
reading uImage
...

2620504 bytes read
reading initrd
...

3331626 bytes read

NAND erase: device 0 offset 0x100000, size 0x400000
Erasing at 0x4e0000 -- 100% complete. Cleanmarker written at 0x4e0000.
OK

NAND write: device 0 offset 0x100000, size 0x400000

Writing data at 0x4ff800 -- 100% complete.
 4194304 bytes written: OK
Marvell>>

 when I restart it then I get the following

Code:

Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 980 bytes
NET: Registered protocol family 16
Kirkwood: MV88F6281-A0, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
Kirkwood: Gating clock using mask 0x1ac224
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
        (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
        (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
NET: Registered protocol family 1
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4012, nTxLock = 32100
msgmni has been set to 1003
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
Driver 'sd' needs updating - please use bus_type methods
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:50:43:01:69:8b
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 3673 at 0x00001cb20000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "uImage"
UBI: MTD device size:            4 MiB
UBI: number of good PEBs:        32
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 32
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 48/23
UBI: background thread "ubi_bgt0d" started, PID 446
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: plug:green:health
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
lib80211: common routines for IEEE802.11 drivers
rtc-mv rtc-mv: setting system clock to 2034-03-09 13:32:58 UTC (2025523978)
UBIFS error (pid 1): ubifs_recover_master_node: failed to recover master node
List of all partitions:
1f00            1024 mtdblock0 (driver?)
1f01            4096 mtdblock1 (driver?)
1f02          519168 mtdblock2 (driver?)
No filesystem could mount root, tried:  ubifs
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)

 

[birdman]

But something occurred to me recently.  I seem to recall that the sheeva plug is supposed to have 2 ttyUSB interfaces (one for the terminal and one for the JTAG).  Am I remembering this correctly? 

This is a function of the system you are using to talk to the Sheeva plug rather than the Sheeva plug itself.  Older kernels showed 2@tty ports, but one more recent ones the JTAG one is ignored.  From drivers/usb/serial/ftdi_sio.c:

Code:

/*
 * First port on JTAG adaptors such as Olimex arm-usb-ocd or the FIC/OpenMoko
 * Neo1973 Debug Board is reserved for JTAG interface and can be accessed from
 * userspace using openocd.
 */

So Mandriva 2009.1 had two, but on an upgrade to 2010.0 I was down to one.  But by then I'd already run the installer, and have had no need to run it since, as I run off an SDHC card so just copy kernel updates onto that and reboot.

[trampjuice]

I must say I have had real problems in getting this to work on windows XP. Its fully working on my other ubuntu partition.

I know what my problem is because I cannot even connect to the sheevabox with the console. Its the  FTDI 2232 drivers. I cannot get them to install. The ones mentioned in the plugcomputer.org serial connection guide are gone from the marvel site, and I have no cd. I went direct to the FTDI site, and downloaded CDM 2.06.00 WHQL Certified drivers. But I just cannot get them recognised in XP.

Device Manager just shows two SheevaPlug "JTAGKey FD 2232D B"'s as uninstalled.

[karkaris]

Did someone succed to run the installer on Windows 7 or XP? I've been tring this for the last 3 days. 
When I run "runme nand" I always get

Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469:
     ****       openocd FAILED
 ****   Is the mini USB cable connected?

I'm also a bit confused about the usb drivers needed. In readme.txt is written to install CDM 2.04.14 and LibUSB-Win32.
Attention: LibUSB-Win32 doesn't run on Windows 7 and will kill all your usb connections.
So I get instead lib usb from http://www.pruftechnik.com/condition-monitoring/support-and-downloads/software.html which supports Windows 7.
My question is which driver should I install,  the CDM or the libusb? 
How can I install both of them for one device?
So on one PC I installed the CDM and on the other I installed the libusb from pruftechnik but with both I got the save error as above.

You help will be much appreciated.

[paketecuento]

Did someone succed to run the installer on Windows 7 or XP? I've been tring this for the last 3 days. 
When I run "runme nand" I always get

Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469:
     ****       openocd FAILED
 ****   Is the mini USB cable connected?

I'm also a bit confused about the usb drivers needed. In readme.txt is written to install CDM 2.04.14 and LibUSB-Win32.
Attention: LibUSB-Win32 doesn't run on Windows 7 and will kill all your usb connections.
So I get instead lib usb from http://www.pruftechnik.com/condition-monitoring/support-and-downloads/software.html which supports Windows 7.
My question is which driver should I install,  the CDM or the libusb? 
How can I install both of them for one device?
So on one PC I installed the CDM and on the other I installed the libusb from pruftechnik but with both I got the save error as above.

You help will be much appreciated.

For XP it's ok. You should have both CDM 2.04.14 and LibUSB-Win32. If not, the error will still there. For W7 I have no idea.. sorry.

[tjoe]

Wouldn't it be more portable to have this script in /bin/sh instead?

you can grab it there: http://github.com/johanburati/stuff/blob/master/sheevaplug-install.sh

[truehl]

Hi,
two question depending to the NewIT multi-boot option:

1. If I use the SheevaPlug-Installer with the NAND option everything goes fine. If I use the MMC option everything goes fine too, but then the system boots only from SD-Card. That's is because I override the u-boot setting for multi-boot with sd-boot. So I have to do the MMC-option first and than the NAND-option to get a multi-boot Plug. So far so good. Do you have an idea how to change the uboot-mmc-custom.txt file so that is equal which option you run first?

2. What happens, if I run the installer with the MMC-Option and the Plug can't find an sd-card? It seems that in that case the NAND option is choosen automaticly and the installer overwright the NAND is that right?

Thanks a lot,
Thomas

[Louis_Cypher]

Hi everybody,

I'm starting getting desperate. I've run the installer at least 10-15 times having always the same result. The bootloader is ssuccessfully written and works. After rebooting he starts uncompressing linux. After ................................. he starts printing a tremendous amount of strange "letters" (looking like opening a binary using your favorite editor). After a couple of minutes my putty dies. A new putty session connects but doesn't give any output. I tried it on meego using gtkterm minicom and screen (I spent at least 20 hours compiling all the required software the installer needs ;-/) and also on SuSe 11.3 x_64.

When i switch off the plug for reboot after the bootprompt he starts the same behaviour again and again.

What did I mess up? Any hints?

Thanks a lot in advance,

Markus

P.S.: I tried to write the uImage and Initrd  like shown in http://nil-techno.blogspot.com/2009/10/upgrading-factory-sheevaplug-nand-to.html butI got bad magic number and didn't manage to fix this

Code:

U-Boot 1.1.4 (Jul 19 2009 - 16:03:28) Marvell version: 3.4.19

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

Soc: 88F6281 A1 (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
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

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:  3  2  1  0

NAND read: device 0 offset 0x100000, size 0x400000

^MReading data from 0x100000 --   0% complete.^MReading data from 0x10a000 --   1% complete.^MReading data from 0x114000 --   2% complete.^MReading data from 0x11e800 --   3% complete.^MReading d
ata from 0x128800 --   4% complete.^MReading data from 0x133000 --   5% complete.^MReading data from 0x13d000 --   6% complete.^MReading data from 0x147800 --   7% complete.^MReading data from 0x
151800 --   8% complete.^MReading data from 0x15c000 --   9% complete.^MReading data from 0x166000 --  10% complete.^MReading data from 0x170800 --  11% complete.^MReading data from 0x17a800 -- 
12% complete.^MReading data from 0x185000 --  13% complete.^MReading data from 0x18f000 --  14% complete.^MReading data from 0x199800 --  15% complete.^MReading data from 0x1a3800 --  16% complet
e.^MReading data from 0x1ae000 --  17% complete.^MReading data from 0x1b8000 --  18% complete.^MReading data from 0x1c2800 --  19% complete.^MReading data from 0x1cc800 --  20% complete.^MReading
 data from 0x1d7000 --  21% complete.^MReading data from 0x1e1000 --  22% complete.^MReading data from 0x1eb800 --  23% complete.^MReading data from 0x1f5800 --  24% complete.^MReading data from 0x1ff800 --  25% complete.^MReading data from 0x20a000 --  26% complete.^MReading data from 0x214000 --  27% complete.^MReading data from 0x21e800 --  28% complete.^MReading data from 0x228800 --  29% complete.^MReading data from 0x233000 --  30% complete.^MReading data from 0x23d000 --  31% complete.^MReading data from 0x247800 --  32% complete.^MReading data from 0x251800 --  33% complete.^MReading data from 0x25c000 --  34% complete.^MReading data from 0x266000 --  35% complete.^MReading data from 0x270800 --  36% complete.^MReading data from 0x27a800 --  37% complete.^MReading data from 0x285000 --  38% complete.^MReading data from 0x28f000 --  39% complete.^MReading data from 0x299800 --  40% complete.^MReading data from 0x2a3800 --  41% complete.^MReading data from 0x2ae000 --  42% complete.^MReading data from 0x2b8000 --  43% complete.^MReading data from 0x2c2800 --  44% complete.^MReading data from 0x2cc800 --  45% complete.^MReading data from 0x2d7000 --  46% complete.^MReading data from 0x2e1000 --  47% complete.^MReading data from 0x2eb800 --  48% complete.^MReading data from 0x2f5800 --  49% complete.^MReading data from 0x2ff800 --  50% complete.^MReading data from 0x30a000 --  51% complete.^MReading data from 0x314000 --  52% complete.^MReading data from 0x31e800 --  53% complete.^MReading data from 0x328800 --  54% complete.^MReading data from 0x333000 --  55% complete.^MReading data from 0x33d000 --  56% complete.^MReading data from 0x347800 --  57% complete.^MReading data from 0x351800 --  58% complete.^MReading data from 0x35c000 --  59% complete.^MReading data from 0x366000 --  60% complete.^MReading data from 0x370800 --  61% complete.^MReading data from 0x37a800 --  62% complete.^MReading data from 0x385000 --  63% complete.^MReading data from 0x38f000 --  64% complete.^MReading data from 0x399800 --  65% complete.^MReading data from 0x3a3800 --  66% complete.^MReading data from 0x3ae000 --  67% complete.^MReading data from 0x3b8000 --  68% complete.^MReading data from 0x3c2800 --  69% complete.^MReading data from 0x3cc800 --  70% complete.^MReading data from 0x3d7000 --  71% complete.^MReading data from 0x3e1000 --  72% complete.^MReading data from 0x3eb800 --  73% complete.^MReading data from 0x3f5800 --  74% complete.^MReading data from 0x3ff800 --  75% complete.^MReading data from 0x40a000 --  76% complete.^MReading data from 0x414000 --  77% complete.^MReading data from 0x41e800 --  78% complete.^MReading data from 0x428800 --  79% complete.^MReading data from 0x433000 --  80% complete.^MReading data from 0x43d000 --  81% complete.^MReading data from 0x447800 --  82% complete.^MReading data from 0x451800 --  83% complete.^MReading data from 0x45c000 --  84% complete.^MReading data from 0x466000 --  85% complete.^MReading data from 0x470800 --  86% complete.^MReading data from 0x47a800 --  87% complete.^MReading data from 0x485000 --  88% complete.
^MReading data from 0x48f000 --  89% complete.^MReading data from 0x499800 --  90% complete.^MReading data from 0x4a3800 --  91% complete.^MReading data from 0x4ae000 --  92% complete.^MReading data from 0x4b8000 --  93% complete.^MReading data from 0x4c2800 --  94% complete.^MReading data from 0x4cc800 --  95% complete.^MReading data from 0x4d7000 --  96% complete.^MReading data from 0x4e1000 --  97% complete.^MReading data from 0x4eb800 --  98% complete.^MReading data from 0x4f5800 --  99% complete.^MReading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK


4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30.2
   Created:      2009-07-23   1:53:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2620440 Bytes =  2.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
$qJeugA+B,Z(QWY4.da1-QP*EJeugAZ:"PFP$Zia()%Af-HRj:FP+Hi$!)ie7].*mYiJ*Fm(kQ;eAY(Q*imdfz'@R^.bZAjI1)AsB*6ey]6T;QqPEtW5kFm1+t-JC(kqje1^KnqP+IwqEQ3UEU^KE4-Bb,+3WA{VI2fU"j5+^KFPgI4eP7
te07Wi=J]yw7+Xwb3G2[,6'YWYqG4ugewh=2Y$^K@I8e]Q7A6)Z,B@BX,mC3mEB|
!,Y,B0:uir2Ui0g]w2.Cnw-jA:wi2qx-p*WIe)VFY$b(U+QIPe5G4X-:Ju$b%q8'U2~vGIE]yIi5/0IP.%L%]8)As
b;*^KEt-gi:nju+VY^K"~:JuPBXF((iqU"|wb3
DAy*^KE4-giz.*5yZ0PI1<Y2 B[)q8'U2juq\(iDKb@$AxAvPVY7:B\
l1.Et-\9]p-fIC8,FX]5-Bg(UwQ5mW6+IcY1F2T(
Y5N4IsB:]gVWE8B(ke_$~0FE$GQpVKQ6
$It,E]7<e: ]\7]%(eQv,R2JUPviv5C3
DA{*^KE4-giz.*5eC6#XqQ6
d5
irjeEI:7q\wW-A5Aqb0iq$v(.JO5Iz-
:_3GAr,Y=TS:]w)11!KbY)^KawIr+*eWKZZKXd6I:5IwXIC2wAf$6I:7K7+jPT+Q1^KawAui5,Ueq)U"rx]0.
iuwA37W'gMP/fU,WEZ6Qf:mIPE/TwYq-TZ+*bk2ex-6.YuKZV;]:t1isK6^KD]xE1(JQze2de2I^(kQ;JI0(WmPI:TKApVI:(+G7]zI3Iz-
1^Kj:xkeGW2M3.FiS6
iqU^Kj3/iwA0WC5+PgMwJ5qRT1*YqqUAuBkdF"f8=rI/)`(TI;.
QU+UA<]8gAo*Q6+qo-VaDH,B g"@KB0XA (^KB0Q(B 5GBX^KB 56 F[,V$.VY&@A`(^KB,PFu+BX'Q(RBX'b"F2,d*$BX (^KB0XQ(B uGBz"mU2'0YB,Eu'JY,V$qX,P>&bZ,E5+)BX'YDV$e"*X,Pu0B0X(B uG@j"/$F"*[B AUL,@~(I@,EuU+@'QBX'Yl%O,F^TY5
%`(we]xuPdvI(.JMuIx-
d77]t(*Y5)6%$iz-bE4-et(+E4-giz.*ukb(Is@+IV6Z(Ti1VU"F(jiqe4-
DA;*^KE4-gi:.juPkV&(IqVB)R4.i1VU"F((TgIPT8AqeuG,BTI1<i2 ZKFZ-i1U2Fhe4(+Y19]vM9
"qA2UI0(+VY^Kr6)IV[6J
j6jsI:-DrI(.JMuI:-
e77]v(*Y56UHePke;eAZzP*] &BZ,RJ -JIPR6U2L+)|wG78XH<5UP'rJ,dfe3UAt%I1;PKiFXdY3.tAxA2;-J]s(Q]3fdF_VIp-Wewa{Qy
I0u;WI{
1;Qx,e=({Q;JIrPwA;I9JAr-GQ6-BIsI:-D_VIp-We:ezGJit$I:.0%Z%Ee5+YP]:j(rQ15A07'Y1dI:nJ:Xj=g^KgBp2&#JX,d96[&21IV0aeew
h8PE4-Dpz7%AvI1d4ua^wI9
d_1

[big_ignoramus]

What did I mess up? Any hints?

I've got a GuruPlug, not a SheevaPlug so I won't be able to really run through the steps you did myself. However the first thing I'd have you check is the environment variables in u-Boot and make sure they match what the blog post you linked to has you set. Especially check this one:

Code:

bootargs_console console=ttyS0,115200

If that's all good, perhaps you could post your u-Boot environment as additional information for someone to help you.

[Louis_Cypher]

Thanks for your quick reply.

I checked the environment and found no errors. I did expect that since the first part of the installer works perfect. Perhaps I messed something else up so here's my environment:

Code:

Marvell>>  printenv
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=a0000
e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
mtdpartitions=mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
ethaddr=f0:ad:4e:00:00:53
real_bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootargs_console=console=ttyS0,115200
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand; bootm 0x00800000 0x01100000
recover3=run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
recover4=usb start; fatload usb 0 0x00800000 uImage; fatload usb 0 0x01100000 initrd
arcNumber=2097
filesize=32D62A
bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=a0000
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no

Environment size: 2064/131068 bytes
Marvell>>

Thanks a lot in advance,

Markus

P.S.: I'll try to replace the uboot and kernelimage within the installer to see wether that helps.

[Louis_Cypher]

fixed. I replaced KernelModules.tar.gz and Kernelimage uImage by the most recent ones found here (Version 3.6.34.2 http://sheeva.with-linux.com/sheeva/2.6.34.2/ started runme.php again and voila: alive and kickin. Thanks anyway!

Best Regards,

Markus

[stitch84]

Hi,

i have a big problem with the sheevaplug-installer on my virtual Ubuntu

Every time i try to recover my sheevaplug with the installer i get Segmentation fault

Code:

sudo php runme.php nand

PHP Notice:  Undefined index: OS in /home/thomas/Desktop/sheevaplug-installer-v1.0/runme.php on line 9

 **** exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f)
 **** Preparing environment variables file ...
reading uboot/uboot-env/uboot-dflt.txt
uboot/uboot-env/fw_setenv baudrate 115200
CRC read error on uboot-env.bin: Success
uboot/uboot-env/fw_setenv loads_echo 0
uboot/uboot-env/fw_setenv ipaddr 10.4.50.165
uboot/uboot-env/fw_setenv serverip 10.4.50.5
uboot/uboot-env/fw_setenv rootpath /mnt/ARM_FS/
uboot/uboot-env/fw_setenv netmask 255.255.255.0
uboot/uboot-env/fw_setenv stdin serial
uboot/uboot-env/fw_setenv stdout serial
uboot/uboot-env/fw_setenv stderr serial
uboot/uboot-env/fw_setenv console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0\(uboot\)ro,0x1ff00000@0x100000\(root\)
uboot/uboot-env/fw_setenv mainlineLinux no
uboot/uboot-env/fw_setenv CASset min
uboot/uboot-env/fw_setenv enaMonExt no
uboot/uboot-env/fw_setenv enaCpuStream no
uboot/uboot-env/fw_setenv enaWrAllo no
uboot/uboot-env/fw_setenv pexMode RC
uboot/uboot-env/fw_setenv disL2Cache no
uboot/uboot-env/fw_setenv setL2CacheWT yes
uboot/uboot-env/fw_setenv disL2Prefetch yes
uboot/uboot-env/fw_setenv enaICPref yes
uboot/uboot-env/fw_setenv enaDCPref yes
uboot/uboot-env/fw_setenv sata_dma_mode yes
uboot/uboot-env/fw_setenv MALLOC_len 1
uboot/uboot-env/fw_setenv ethprime egiga0
uboot/uboot-env/fw_setenv netbsd_en no
uboot/uboot-env/fw_setenv vxworks_en no
uboot/uboot-env/fw_setenv bootargs_root root=/dev/nfs rw
uboot/uboot-env/fw_setenv bootargs_end :::DB88FXX81:eth0:none
uboot/uboot-env/fw_setenv image_name uImage
uboot/uboot-env/fw_setenv bootcmd tftpboot 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) \$\(bootargs_root\) nfsroot=\$\(serverip\):\$\(rootpath\) ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvNetConfig\) \$\(mvPhoneConfig\)\;  bootm 0x2000000\;
uboot/uboot-env/fw_setenv standalone fsload 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) root=/dev/mtdblock0 rw ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvPhoneConfig\)\; bootm 0x2000000\;
uboot/uboot-env/fw_setenv bootdelay 3
uboot/uboot-env/fw_setenv disaMvPnp no
uboot/uboot-env/fw_setenv ethaddr 00:50:43:4e:2a:14
uboot/uboot-env/fw_setenv ethmtu 1500
uboot/uboot-env/fw_setenv mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs
uboot/uboot-env/fw_setenv mvNetConfig mv_net_config=\(00:11:88:0f:62:81,0:1:2:3\),mtu=1500
uboot/uboot-env/fw_setenv usb0Mode host
uboot/uboot-env/fw_setenv yuk_ethaddr 00:00:00:EE:51:81
uboot/uboot-env/fw_setenv nandEcc 1bit
uboot/uboot-env/fw_setenv netretry no
uboot/uboot-env/fw_setenv rcvrip 169.254.100.100
uboot/uboot-env/fw_setenv loadaddr 0x02000000
uboot/uboot-env/fw_setenv autoload no
uboot/uboot-env/fw_setenv enaAutoRecovery yes
uboot/uboot-env/fw_setenv ethact egiga0
reading uboot/uboot-env/uboot-nand-custom.txt
uboot/uboot-env/fw_setenv bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
uboot/uboot-env/fw_setenv mtdpartitions mtdparts=orion_mtd:0x400000@0x100000\(uImage\),0x1fb00000@0x500000\(rootfs\)
uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:c1:e6
uboot/uboot-env/fw_setenv real_bootcmd setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) \$\(bootargs_root\)\; nand read.e 0x00800000 0x00100000 0x00400000\; bootm 0x00800000
uboot/uboot-env/fw_setenv bootargs_console console=ttyS0,115200
uboot/uboot-env/fw_setenv bootcmd run recover1
uboot/uboot-env/fw_setenv recover1 setenv mainlineLinux yes\; setenv arcNumber 2097\; setenv bootcmd run recover2\; saveenv\; reset
uboot/uboot-env/fw_setenv recover2 run recover3\; setenv bootcmd \$\(real_bootcmd\)\; saveenv\; setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand\; bootm 0x00800000 0x01100000
uboot/uboot-env/fw_setenv recover3 run recover4\; nand erase clean 0x00100000 0x00400000\; nand write.e 0x00800000 0x00100000 0x00400000
uboot/uboot-env/fw_setenv recover4 usb start\; fatload usb 0 0x00800000 uImage\; fatload usb 0 0x01100000 initrd

 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0 (2009-07-26-14:56) 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
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : JTAG Tap/device matched
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 5 to 6 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 67.196655s
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 0 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
wrote file uboot.bin to NAND flash 0 up to offset 0x00074000 in 243.955460s
Segmentation fault
 **** openocd FAILED
 **** Is the mini USB cable connected?
 **** Try powering down, then replugging the Sheevaplug

Since my first try with the installer, i can not start linux on my plug computer. The only thing i can see is the uboot-prompt
Does anyone have a solution for me?

[marcus]

fixed. I replaced KernelModules.tar.gz and Kernelimage uImage by the most recent ones found here (Version 3.6.34.2 http://sheeva.with-linux.com/sheeva/2.6.34.2/ started runme.php again and voila: alive and kickin. Thanks anyway!

Best Regards,

Markus

Markus -

Possibly you had a newer revision cpu; I got the same symptoms running the installer on the A1 cpu plugs that we just received.

[stitch84]

Unfortunately this doesn´t work,

i replaced both files but i get the same segmentation fault error again