Sheevaplug installer - version 1.0

[pingtoo]

Sorry, I mean to said "sheeva-installer". anyway you did not include kernel message. or you miss the attachment. I can not see anything you described.

I am bit of confuse by you description, you said

you can mount and access my usb device via ssh.

So does that mean you have a working plug computer, And you can ssh to this plug computer and access usb device attach to the plug computer using ssh? Now you are trying to setup second plug computer?

If my previous assumption is incorrect, And you are trying to setup your first plug computer then may I point out that you can access your usb device in linux is not equate to access usb device in u-boot. Access usb device in linux on plug computer simply prove A. your plug computer have working usb host controller. B. your linux is configurated correctly to access usb storage.

[Kamikaze321]

I mean my sheevaplug used to work with a preinstalled ubuntu. It had some bugs like described on the wiki pages, thats all. Then I wanted to install new OS with a new kernel without bugs etc. so I am here, so your first assumption was correct

You asked me for a kernel log by typing "boot", here it is:

Code:

Marvell>> boot

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

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
Bad Magic Number
Marvell>> version

U-Boot 1.1.4 (Dec 27 2009 - 22:03:21) Marvell version: 3.4.27 - pingtoo patch.01
Marvell>>

As you can see above, I use your uboot.

[pingtoo]

Finally we establish some understanding

So you currently have

• 3.4.27 u-boot with my patch.
• The kernel in NAND is corrupted
• You have used USB to load kernel previously #<-some hint form your previous post

You can

• A. Start everything from scratch do the sheeva-installer php runme.php.
• B. Using manual process I described below, however I have to warn you that I have not test this before, I do not know if it will work for sure.

The manual work

Some assumptions, your USB first partition is formated in FAT and you still have your u-boot environment intact(base from here).

Code:

Marvell>> reset #<- once you at autoboot prompt press key to stop it.
Marvell>> run recover3  #<- this will place your kernel in to NAND
Marvell>> setenv bootargs ${bootargs_console} root=/dev/ram0 rw ramdisk=0x01100000,8M rdinit=/bin/sh init=/bin/sh
Marvell>> bootm 0x00800000 0x01100000

If commands in above all run successfully then you should be at shell prompt, now I want to take a pause to example your environment.

Please post output of cat /proc/mtd

You may need to do following first,

Code:

~# mount -t proc proc /proc
~# mount -t sysfs sys /sys
~# mdev -s

I will be step away from my computer for next hour or bit more. So please be patient I will check as soon as I am back.

[Kamikaze321]

Hey, sorry I needed some sleep yesterday 

Yes you are right about what I am currently have, and I already tried to run the installer many times, the output is always the same. Now I tried your commands and I got this

Code:

Memory: 256MB 256MB = 512MB total
Memory: 510080KB available (4728K code, 998K data, 140K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
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
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 3252K
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"
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 03:34:43 UTC (2025488083)
RAMDISK: gzip image found at block 0
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing init memory: 140K
usb 1-1: new high speed USB device using orion-ehci and address 2
/bin/sh: can't access tty; job control turned off
# usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
scsi 0:0:0:0: Direct-Access     USB      DISK 2.0         1219 PQ: 0 ANSI: 0 CCS
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 3915776 512-byte hardware sectors: (2.00 GB/1.86 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk

# cat /proc/mtd
cat: can't open '/proc/mtd': No such file or directory
# mount -t proc proc /proc
# mount -t sysfs sys /sys
# mdev -s
# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 1fb00000 00020000 "root"
#

[pingtoo]

OK, we are on to something,

Here are some choices again,

• A. You can modify /etc/init.d/rcS. May be the easiest way.
• B. Manual work.

Run /etc/init.d/rcS.

Assume you want to install to NAND.

Code:

# install_type=nand
# export install_type
# sed -i -e 's/mtd1/mtd2/' -e 's/m 1/m 2/' /etc/init.d/rcS
# [ $? -eq 0 ] && /bin/sh /etc/init.d/rcS

If above sed -i -e ... command failed with sed not found, then you will have to manually modify /etc/init.d/rcS with vi and the run the /bin/sh /etc/init.d/rcS

At the end of run you might see some sort of reboot failure, this is to be expected since we break in to shell. See the note about after reboot below.
Manual work.

Again assume you want to install on NAND.

Code:

# ubiformat -y /dev/mtd2
# ubiattach /dev/ubi_ctrl -m 2
# mdev -s
# ubimkvol -m -N rootfs /dev/ubi0
# mdev -s
# ubiupdatevol /dev/ubi0_0 -t
# mkdir -p /mnt/usb
# mkdir -p /mnt/target
# mount /dev/sda1 /mnt/usb
# mount -t ubifs ubi0:rootfs /mnt/target
# cd /mnt/target
# tar zxpf /mnt/usb/rootfs.tar.gz
# [ -e /mnt/usb/modules.tar.gz ] && tar zxpf /mnt/usb/modules.tar.gz
# sync
# umount /mnt/target
# umount /mnt/usb

This is basically commands took out from /etc/init.d/rcS, doing so we have better control knowing where went wrong.
Ready Reboot

You need to use

Code:

# reboot -f

because we are in shell, normal reboot will not work.

At autoboot prompt, break it with any key to get in to u-boot.

Code:

Marvell>> setenv bootcmd ${real_bootcmd}
Marvell>> saveenv
Marvell>> boot  #<- this should take you in to your newly installed rootfs in NAND.

Please post any kernel output from here on, if it did not workout I need to see the kernel message in order to understand where went wrong.


Good luck

[Kamikaze321]

Hez again,

Ok, the first part did work and it saw like the OS is got installed to a big partition, but I dont know exactly and at the end I saw a reboot failure as you expected, so i did reboot -f
during the reboot I forgot to stop the boot and I got following at the end

Code:

lib80211: common routines for IEEE802.11 drivers
rtc-mv rtc-mv: setting system clock to 2034-03-09 06:08:17 UTC (2025497297)
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi2:rootfs", error -19
VFS: Cannot open root device "ubi2:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0 (driver?)
1f01            4096 mtdblock1 (driver?)
1f02          519168 mtdblock2 (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)

then I rebooted with a little button on a sheevaplug and interrupted the reboot as you described, and I typed

Code:

Marvell>> setenv bootcmd ${real_bootcmd}
Marvell>> saveenv
Marvell>> boot

and I got the following output (second part is after reboot)

Code:

Hit any key to stop autoboot:  0
Marvell>> setenv bootcmd ${real_bootcmd}
Marvell>> saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
Marvell>> boot

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

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>

Is the booting image at 00800000?

now I will post the whole output. as I saw it during the last steps*the outputs above are extracted from this one

Code:

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: 45/22
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 06:08:17 UTC (2025497297)
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi2:rootfs", error -19
VFS: Cannot open root device "ubi2:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0 (driver?)
1f01            4096 mtdblock1 (driver?)
1f02          519168 mtdblock2 (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)
�
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Dec 27 2009 - 22:03:21) Marvell version: 3.4.27

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

Soc: 88F6281 A0 (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]
Hit any key to stop autoboot:  0
Marvell>> setenv bootcmd ${real_bootcmd}
Marvell>> saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
Marvell>> boot

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

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>

[pingtoo]

This is kind of strange

This first unintented reboot work, only because missing root device.

After setup bootcmd, reboot stop working, not able to load correct kernel. hummm.

I need to review all of our post to see where went wrong.

Please post your current u-boot env. just in case my copy out of day.

[Kamikaze321]

hi

 

I hope these are the files you are looking for.

u-boot-dflt

Code:

baudrate 115200

loads_echo 0

ipaddr 10.4.50.165

serverip 10.4.50.5

rootpath /mnt/ARM_FS/

netmask 255.255.255.0

stdin serial

stdout serial

stderr serial

console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)

mainlineLinux no

CASset min

enaMonExt no

enaCpuStream no

enaWrAllo no

pexMode RC

disL2Cache no

setL2CacheWT yes

disL2Prefetch yes

enaICPref yes

enaDCPref yes

sata_dma_mode yes

MALLOC_len 1

ethprime egiga0

netbsd_en no

vxworks_en no

bootargs_root root=/dev/nfs rw

bootargs_end :::DB88FXX81:eth0:none

image_name uImage

bootcmd tftpboot 0x2000000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig);  bootm 0x2000000;

standalone fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;

bootdelay 3

disaMvPnp no

ethaddr 00:50:43:01:69:8B

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

enaAutoRecovery yes

ethact egiga0

uboot-nand-custom

Code:

#### Change ONLY in the following few lines

# Following for installation on SD card. If you want to boot from USB stick change it to /dev/sda1
# or /dev/mtdblock1 if you installed rootfs on the NAND inside the plug
bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs

# NAND flash partitions. If using kernel >= 2.6.30 then replace orion_nand with orion_mtd
mtdpartitions mtdparts=orion_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)

# The following is an example MAC address. Change it according the MAC on the back side of the plug
ethaddr 00:50:43:01:69:8B

#### DONT change the following.
# Automated process the sets arcNumer to 2097, reset, runs uImage and initrd from USB stick and set bootcmd to 'real_bootcmd' above
# Bootcmd to be used after all installation is done
real_bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootargs_console console=ttyS0,115200
bootcmd run recover1
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

[pingtoo]

@Kamikaze321,

Sorry, I mean printenv from u-boot prompt. we have some serious communication challenge

[Kamikaze321]

 

I thought uboot env thats a directory in my installer 

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=ubi2: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
filesize=32D62A
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=ubi2:rootfs rootfstype=ubifs

Environment size: 2192/131068 bytes
Marvell>>

[pingtoo]

OK, I fail to see anything wrong in post past or present, so I really don't understand where was problem.

please try following in u-boot prompt

Code:

Marvell>> nand read.e 0x02000000 0x00100000 0x00400000
Marvell>> imi 0x02000000 #<- this will do the usually CRC check.
Marvell>> nand read.e 0x00800000 0x00100000 0x00400000
Marvell>> imi 0x00800000 #<- again CRC check.
Marvell>> cmp.b 0x02000000 0x00800000 0x400000

The cmp.b should give you a message

Total of 4194304 bytes were the same

So, if the first and second imi ... command give you message about some sort of CRC/Magic error, the it mean the previous run recover3 did not successful write the kernel into NAND, we need to work on that.

I notice you have modify the u-boot environment bootargs_root=... root=ubi2:rootfs ..., this is wrong, it must be 0. However this is a issue only when you have successful load kernel.

Good luck

[draimus]

So I'm still having issues with getting the sheeva-installer to work at all.  I recently upgraded to the patched 3.4.27 uboot to see if it changes matters.  It did not.  OpenOCD still gives me JTAG errors.  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?  Right now the only interface I have is ttyUSB0 which is for the terminal.  dmesg reports the following about the interface:

Code:

[  939.740087] usb 5-1: new full speed USB device using uhci_hcd and address 4
[  939.954349] usb 5-1: configuration #1 chosen from 1 choice
[  939.962278] usb 5-1: Ignoring serial port reserved for JTAG
[  939.967391] ftdi_sio 5-1:1.1: FTDI USB Serial Device converter detected
[  939.967449] usb 5-1: Detected FT2232C
[  939.967454] usb 5-1: Number of endpoints 2
[  939.967459] usb 5-1: Endpoint 1 MaxPacketSize 64
[  939.967464] usb 5-1: Endpoint 2 MaxPacketSize 64
[  939.967468] usb 5-1: Setting MaxPacketSize 64
[  939.971187] usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 3193.606551] usb 5-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1

So perhaps there is something amiss with my driver (or udev)?  If JTAG doesn't have a device node to operate on that may explain my issues.

[Kamikaze321]

zour commands give me the following

Code:

Marvell>> nand read.e 0x02000000 0x00100000 0x00400000

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

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
Marvell>> imi 0x02000000

## Checking Image at 02000000 ...
   Bad Magic Number
Marvell>> imi 0x00800000

## Checking Image at 00800000 ...
   Bad Magic Number
Marvell>> cmp.b 0x02000000 0x00800000 0x400000
Total of 4194304 bytes were the same
Marvell>>

I did try to change bootargs_root=... root=ubi... but it didnt help, so I changed it again, and the last run was with 0, I have checked my files, or just look the post where I have attached some files instead of doing printenv, it already contains ubi0

[pingtoo]

@Kamikaze321,

Please clarify In your last post you stated that,

...
I did try to change bootargs_root=... root=ubi... but it didnt help, so I changed it again, and the last run was with 0, I have checked my files, or just look the post where I have attached some files instead of doing printenv, it already contains ubi0

What do you mean it is already contains "ubi0"?

Please look only two post before, I ask you to send me the the "printenv" from u-boot, which clearly set bootargs_root=ubi.mtd=1 root=ubi2:rootfs rootfstype=ubifs.

If you wish to make changes in between, I have no problem what's ever, But you need to make clear what change you make from last post or else my debug progress is chasing a moving target which I will never able to catch

Anyway, assume you have successful wrote the rootfs into NAND, please run the recover3 again.

[pingtoo]

So I'm still having issues with getting the sheeva-installer to work at all.  I recently upgraded to the patched 3.4.27 uboot to see if it changes matters.  It did not.  OpenOCD still gives me JTAG errors.  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?  Right now the only interface I have is ttyUSB0 which is for the terminal.  dmesg reports the following about the interface:

Code:

[  939.740087] usb 5-1: new full speed USB device using uhci_hcd and address 4
[  939.954349] usb 5-1: configuration #1 chosen from 1 choice
[  939.962278] usb 5-1: Ignoring serial port reserved for JTAG
[  939.967391] ftdi_sio 5-1:1.1: FTDI USB Serial Device converter detected
[  939.967449] usb 5-1: Detected FT2232C
[  939.967454] usb 5-1: Number of endpoints 2
[  939.967459] usb 5-1: Endpoint 1 MaxPacketSize 64
[  939.967464] usb 5-1: Endpoint 2 MaxPacketSize 64
[  939.967468] usb 5-1: Setting MaxPacketSize 64
[  939.971187] usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 3193.606551] usb 5-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1

So perhaps there is something amiss with my driver (or udev)?  If JTAG doesn't have a device node to operate on that may explain my issues.

If you can not past this ftdi problem, it does not matter which version of u-boot. only when you have successfully connect from your HOST to PLUG using the JTAG flush the u-boot then u-boot version matter. This is my demsg output

usb 3-2: USB disconnect, address 2
usb 3-2: new full speed USB device using ohci_hcd and address 3
usb 3-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected
drivers/usb/serial/ftdi_sio.c: Detected FT2232C
usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0
ftdi_sio 3-2:1.1: FTDI USB Serial Device converter detected
drivers/usb/serial/ftdi_sio.c: Detected FT2232C
usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB1
usbcore: registered new interface driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver

There is a solution bypass using JTAG. if you can follow the wiki page to setup a tftp server you can flush u-boot with tftp.

Good luck