Sheevaplug installer - version 1.0

[rooster]

please try using version 0.2.0 http://prdownload.berlios.de/openocd/openocd-0.2.0.tar.bz2
It was release with this version and there might be changes in recent versions that break.

[draimus]

Thanks for the reply.  I built openocd from the link you provided.  Now I get the same JTAG errors raj2009 reported a few posts ago.

Code:

**** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0 (2010-01-03-10:45) 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 power 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

[Guai888]

I would like to suggest that you run that openocd again right after you see this problem. It usually can connect in the next try. It work for me

[draimus]

The output I posted from openocd was after I had tried it four times in a row.

[Kamikaze321]

Hey guys, i need some help.

I use the Installer 1.0 to install the os on a Flash drive. During the installation I see a message that there is not enough free storage and when it restarts a see: bad magic number. During the installation it seems to write to a 4mb partition.
Here is my uboot-nand-custom.txt:

Code:

# 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)

Probably i have to change here something, but I dont know what to change. And I dont understand what i have to change to /dev/mtdblock1 . I tried to change ubi-mtd=1 to 0 and root=ubi0 to 1 but it didnt help. And suggestions?
Thanks

[rooster]

please post the installation output so we can see what went wrong in the procedure.

[Kamikaze321]

Ok I have attached the files.

Host.txt is the screen where i start the installation. And 2 screenshots is what I recieve from sheevabox. I hope its enough information.

[pingtoo]

Looks like your kernel mis-interpreter the mtdpart=, what is your kernel version? did you build it yourself?

[Kamikaze321]

No, I used a 2.6.32-3 kernel. Right now I tried  with the one delivered with the installer and I get the same error. 

[pingtoo]

No, I used a 2.6.32-3 kernel. Right now I tried  with the one delivered with the installer and I get the same error. 

OK, then please do printenv at Movell>> prompt. Also please post the kernel boot messages from beginning if you can. in the kernel message there some clues on what kernel parameters was passed on.

[Kamikaze321]

Hi, thank you for help.

I have attached printenv, but I dont know how to get kernel messages, on my desktop mashine I would try /var/log but I am lost with sheeva 

Code:

Marvell>> printenv | more
## Error: "|" not defined
## Error: "more" not defined
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_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
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
bootargs=console=ttyS0,115200 mtdparts=orion_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs

Environment size: 2210/131068 bytes
Marvell>>

[pingtoo]

You are doing just fine, to get kernel message just continue your booting process as you post. it looks like you are using a buggy version u-boot 3.4.23, please try to download from here http://plugcomputer.org/plugforum/index.php?topic=1134.msg7016#msg7016, rename it to uboot.bin in your sheeva-installer/uboot directory so your will have less chance to hit the ext2/SD bug.

To capture kernel message, at Marvell>> prompt do boot should be good enough.

[Kamikaze321]

Hey,

I have tried your version of uboot and its the same. I guess i already used it before cos the size was the same.

Code:

        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

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 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], egiga1
Hit any key to stop autoboot:  0

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>> 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]

You will find all u-boot have same size I am not sure why this is the case.

If you wish to stay on 3.4.19,  as long as you boot is from NAND or you boot off from a FAT partition you should be OK.

Since you got "BAD MAGIC" error that is a indication your installation was not successful may be you want to try to do the sheeva-installation again.

Or please describe your current environment. Do you have a SD/MMC card you know it work with your plugcomputer? or do you have an USB device that you know it work with your plugcomputer?

[Kamikaze321]

I am on 3.4.27 now, I know the log below is different.
Uboot delivered with the installer has a little bit different size and its not working too. I use an usb stick and its ofcourse working with this device (Kernel is loaded). When I used the factory defaults I could mount and access my usb device via ssh. And as you see the kernel is being loaded. When i got my sheevaplug I did run distro update, but ofcourse it didnt work but i had a still working sheevaplug (ssh access) but some dependencies were broken. But I cant imagine it has something todo with my current errors, since everything got deleted. I guess some parameter is wrong (installer).

What do you mean by "sheeva-instalation"? I am trying it all the time and evertime I get the same error: no space left on device because it writes in wrong partition.