CASE CLOSED - DESTROYED a SheevaPlug in few minutes - Help wanted

[zentech]

Dear All,

I was quite trhilled when yesterady I received my SheevaPlug. I bought it because I have a Thecus NAS 4100PRO (6TB) a Squeezebox and now why to have a module to run Squeezecenter on the NAS. Reading differnt forum I have warmly suggested to have a SheevaPlug and run the Squeezecenter on it. Great!.

I followed all the procedure.
I'm connected to my SP via TeraTeam VT
I saw It
I have preparred my 8Gb USB key with all the necessary sw to be install on in (on the SD 4gb card)
and...

Maybe I do something wrong following the procedure.
After resetting it now I have a blank sad screen inf front of me.
No way to access to it.
If I plug/unplug the SP from my PC he recognize it (I hear the Bip ) but no way to access to it.

ANY suggestion on how recover it?

Thanks for any suggestion, help hints

Regards
Marco

[NewIT_Marcus]

Marco -

You're not providing enough information.

What is "Tera Team VT"? A serial console program?

Did you ever see any console output? If so, what exactly did you do afterwards? What serial settings are you using?

With the little information you have provided, it just sounds as though you're not making a proper serial connection. There's a good page on the plugcomputer wiki, but the site seems to be down right now. You can try searching there when it comes back up, or look here.

If you can't establish a connection, you must tell us what operating system you are using, and what software you have tried, and your serial settings. If you are using Windows you must ensure that you install the serial driver.

If you are trying to use ssh, again, you need to tell us what software you are using and how you have identified the IP address that you are trying to connect to.

[zentech]

Marcus,

following you instruction these are all the details I can give hoping to find a solution.

SheevaPlug is connected to the PC via USB. There are no SD or USB inserted into the Sheevaplug
To access to it I use Tera Team VT, a serial console program with baud rate set at 115200bps. With this configuration I was able to see the SheevaPlug

Following your suggestion I read as much I can on wiki and was able to understood that there is a reset micro button. If I press it finally I'm able to see again the sheevaplug but...

• pressing the button the sheevaplug is resetting if I press "Return key" many times I have this prompt Marvell>>
• If I simply press this button and leave the restarting process I got this message: "No filesystem could mount root, tried:  ext3 ext2 ext4 cramfs vfat msdos jfs
  Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)

I tryied to read all the documentation coming with the CD but with no success. No idea on how to reset to factory default the system.
Thanks for your patient and help
Regards
Marco

PS.. hereafter the whole message I got after pressing the micro button located next to the SD slot.

       |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ 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 0x300000

Reading data from 0x3ff800 -- 100% complete.
 3145728 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.
Linux version 2.6.30.2 (kelly@speedy) (gcc version 4.2.1) #11 PREEMPT Wed Jul 22 19:53:31 MDT 2009
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell SheevaPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0x00000(u-boot),0x300000@0x100000(uImage)ro,0x1fc00000@0x400000(rootfs)rw root=/dev/mtdblock2
NR_IRQS:114
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 513408KB 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
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:62:d4
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 175 at 0x0000015e0000
Bad eraseblock 3367 at 0x00001a4e0000
Bad eraseblock 3852 at 0x00001e180000
mtd: bad character after partition (r)
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 2010-02-09 17:29:31 UTC (1265736571)
List of all partitions:
1f00            1024 mtdblock0 (driver?)
1f01            4096 mtdblock1 (driver?)
1f02          519168 mtdblock2 (driver?)
No filesystem could mount root, tried:  ext3 ext2 ext4 cramfs vfat msdos jfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
[<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 [<c0009168>] (prepare_namespace+0x16c/0x1c4)
[<c0009168>] (prepare_namespace+0x16c/0x1c4) from [<c0008734>] (kernel_init+0xc0/0xec)
[<c0008734>] (kernel_init+0xc0/0xec) from [<c0040b3c>] (do_exit+0x0/0x6ac)

[NewIT_Marcus]

From the looks of your U-Boot version, you have an eSATA plug. Is that correct?

From the Marvell>> prompt, type printenv and copy & paste the output here. From your output, it looks as though your bootargs are:

Code:

console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0x00000(u-boot),0x300000@0x100000(uImage)ro,0x1fc00000@0x400000(rootfs)rw root=/dev/mtdblock2

And yet, the original factory settings should be:

Code:

console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none

When you said (in your first message) "I followed all the procedure", what procedure are you referring to? Have you changed the environment variables in order to enable SD card booting? The errors you are seeing may be caused by an inappropriate combination of settings.

The eSATA environment variables should be the same as those for the non-eSATA plug, and you can find them here.

[zentech]

Hello Marcus,

thanks for your support.

1) This is the model I bought trough Newit.co.uk : http://www.newit.co.uk/store/index.php?main_page=product_info&cPath=1&products_id=11
2) Resetting the SP and stopping to get the MARVELL >> prompt and typing printenv this is the result:  see hte end of the message
3) I bought it because I want to share all the music I have on my Thecus via Squeezebox. The procedure I'm referring is the one written by Thomas at: http://wiki.slimdevices.com/index.php/Sheevaplug_SBS_Server_for_dummies
4) I do not change the configuration ... or I think not to have done. But, at this point, I can think to misptype something while I was trying to follow the wiki for installin SBS

UPDATE
This night I kept workin on the Sheeva following the istruction I got and I was able to follow (I hope succesfully) the step Installing the base system of the wiki above mentioned. Installing the base system --> prepare the system --> Install debian --> newtwork setup ....
And now I'm stopped because I get confused on how to proceed.

Hope this info are usefull
Thansk again for the support
Marco


  |  \/  | __ _ _ ____   _____| | |
  | |\/| |/ _` | '__\ \ / / _ \ | |
  | |  | | (_| | |   \ 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
Marvell>>
Marvell>>
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
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
autoload=no
ethact=egiga0
bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
mtdpartitions=mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
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
bootargs_root_nand=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
bootcmd_nand=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root_nand); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootargs_root_mmc=root=/dev/mmcblk0p2 rootdelay=5
real_bootcmd=run bootcmd_mmc; run bootcmd_nand
loadaddr=0x2000000
mtd1Size=0x300000
e=ttyS0,115200
filesize=44AD000
console=a0000
e=ttyS0,115200
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
ethaddr=00:50:43:4c:02:26
run_diag=no
arcNumber=2097
bootargs_console=console=ttyS0,115200
bootcmd_mmc=mmcinit; ext2load mmc 0 0x0800000 /uInitrd; ext2load mmc 0 0x400000 /uImage
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_mmc; bootm 0x400000 0x0800000
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: 2517/131068 bytes
Marvell>>

[truehl]

Marco:

You can find the original settings of your plug here: http://www.newit.co.uk/forum/index.php/topic,194.0.html.

If you have used my wiki you have changed the following variables:
Marvell>> setenv mainlineLinux yes
Marvell>> setenv arcNumber 2097
Marvell>> setenv bootargs_console console=ttyS0,115200
Marvell>> setenv bootcmd_mmc 'mmcinit; ext2load mmc 0 0x0800000 /uInitrd; ext2load mmc 0 0x400000 /uImage'
Marvell>> setenv bootcmd 'setenv bootargs $(bootargs_console); run bootcmd_mmc; bootm 0x400000 0x0800000'

So changing this back, you should have the original setting.

What I don't understand is: Why do You have a 3.4.19 u-boot version? I thougt NewIt uses the 3.4.23.

Marcus: Please correct me if I'am wrong.

Greetings, Thomas

[NewIT_Marcus]

Marco -

First of all, don't panic.

The reason your plug isn't booting is because of an incorrect combination of:

• U-Boot
• Environment variable settings
• kernel

In order to solve the problem, you may need to make some decisions (and you already did, in a way, by saying that you are trying to set up SqueezeBox Server), and take appropriate steps to get the correct version / settings for each.

Firstly, U-Boot.

The plug that we sold you should have had U-Boot 3.4.23. You are reporting 3.4.19, and with a date that is different to any that I have seen before):

Code:

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

I have a version 3.4.19 here and it reports:

Code:

U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19

More than anything else, if you don't have the correct version of U-Boot, you may not be able to boot from SD card. If you had 3.4.23 when you received your plug, you really oughtn't to have downgraded to 3.4.19.

I have uploaded all the versions of U-Boot that I have here:

http://www.newit.co.uk/u-boot/

All have been downloaded from links provided at the plugcomputer forum, except (IIRC) one that came on the original CD and another that we got from Globalscale.

If you must pick one, we would recommend 3.4.23, I had some problems with several later versions.


Secondly, environment variable settings.

This is where it gets confusing. You are intending to boot from SD card, and yet the console messages that you copied show that it is booting from NAND:

Code:

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

and:

Code:

Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0x00000(u-boot),0x300000@0x100000(uImage)ro,0x1fc00000@0x400000(rootfs)rw root=/dev/mtdblock2

I do not see any messages that show any (failed) attempt to boot from SD card. Neither do I see any environment variables that support the boot command that seems to be in effect.

Perhaps there is a problem that we cannot see with U-Boot and your environment variables. If I were you, I would fix the U-Boot version and reset all the environment variables. It will take 5-10 minutes of copying and pasting. Here are the complete settings for the version we supplied to you:

http://www.newit.co.uk/forum/index.php/topic,194.0.html

All our multi-boot plugs are tested and booted both from NAND and from SD card after they have been configured. I wouldn't be at all surprised if the changes that you have applied have made it impossible for you to boot from the supplied debian SD card. But when you have U-Boot and the environment variables set up correctly, your easiest test will be to try booting from the original SD card, providing you haven't rewritten the data on it.

Thirdly, the kernel

We can see that you have 2.6.30.2 on the NAND. That's fine, that's the version we supply on the multi-boot plugs. But you also must have a suitable version on the SD card that you are preparing for SqueezeBox Server. But these issues can be looked at once you have dealt with U-Boot first.

[truehl]

Marcus:
If I want to set up the boot variables to the multi boot default I have to do some sentenv. For example:
bootcmd_mmc=setenv bootargs $(bootargs_console) $(bootargs_root_mmc); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000

so if i type: setenv bootcmd_mmc=setenv bootargs $(bootargs_console) $(bootargs_root_mmc); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000
It will not work, because this line are 3 commands I think. After each ";" starts a new command is this right? I think I have onla use the command before the fist ";"

Right???

I think for that reason Marco is not successful with his Plug?


Greetings,
Thomas

[NewIT_Marcus]

Thomas -

Consider:

Code:

setenv var1 'setenv var2 value2; setenv var2 value2'

It won't work the same without the quotation marks.

So yes, this might be an issue, but I'm not sure that I can reconcile the boot log with the environment variables posted by zentech.

[truehl]

Marcus:
o.K so Marco has to add Quote to every setenv if more the one commad is listed an separated by",". Looks like this:
setenv bootcmd_mmc='setenv bootargs $(bootargs_console) $(bootargs_root_mmc); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000'

Code:

setenv bootcmd_mmc 'setenv bootargs $(bootargs_console) $(bootargs_root_mmc); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000'

right?

Greetings Thomas

[truehl]

Marcus and one more question:
In my wiki for the Squeezebox installation on the plug i write that one have to change some u-boot variables:

Code:

Marvell>> setenv mainlineLinux yes
Marvell>> setenv arcNumber 2097
Marvell>> setenv bootargs_console console=ttyS0,115200
Marvell>> setenv bootcmd_mmc 'mmcinit; ext2load mmc 0 0x0800000 /uInitrd; ext2load mmc 0 0x400000 /uImage'
Marvell>> setenv bootcmd 'setenv bootargs $(bootargs_console); run bootcmd_mmc; bootm 0x400000 0x0800000'
Marvell>> run bootcmd

I think these settings must be enough for the Plug if I use one of your preset Plugs with a u-bbot version of 3.4.23, right? And the other question: Are these settings enough for a Plug witch was setup initial with the SheevaPlug installer?

Because of the fact a lot of people use my wiki, I hope that the things I wrote in the wiki are correct!

Is it possible, that you check the wiki for those things depending on preparing the Plug?

http://wiki.slimdevices.com/index.php/Sheevaplug_SBS_Server_for_dummies#Prepare_the_system

Thanks a lot,
Greetings Thomas

[NewIT_Marcus]

Thomas -

Those settings work against those we use for our multi-boot plugs. Our SD cards are prepared according to a different recipe and with the changes you quote, booting is not possible from either NAND or a NewIT-style SD card.

That's fine, so long as the settings work for your SBS and the user understands that.

[truehl]

Marcus:
o.k. but if someone uses one of your Plugs, my settings will work, right? Your configuration won't work any longer if they save the variavles, right? Therefore I wrote in the wiki that they should save the original configuration!

Thank a lot,
Thomas

[NewIT_Marcus]

Thomas -

If the values you advise are appropriate for the SD cards you are using, then I am sure it can work on our plugs. I haven't tested your SD card, so I can't say for sure that they might not be 1 or 2 additional environment variables that might need to be tweaked. But I can't see anything obviously wrong or problematic.

The issue is, of course, to recognise that things can and do go wrong from time to time, and to understand that with a modicum of patience and logical thought, there is a way to fix any problems.

To that I end, I would advise that you add a complete list of environment variables to your wiki page. They would serve as an example that was known to work. Remember that things like the recover variables are irrelevant to a running plug, they are only created for the purpose of automating the re-configuration process. But there are other variables, the presence or lack of which is very significant (mainlineLinux & arcNumber). However, as I said before, I see no obvious problems with zentech's values, so if it were me, in that situation I would reset and manually reconfigure all environment variables. (I've had problems before once or twice when everything looked OK, but just didn't work. Copying & pasting all the environment variables takes about 5 minutes - I have a text file with all the commands in it, ready for copy & paste - so it hardly takes any time).

[zentech]

Hello Marcus, Hello Thomas,

even if, with Thomas via skype, we have spent several hours together to unserstand why I do have so many problems with my SheevaPlug I'n not yet enter into panic mode

The SD card that I'm using are: ScanDisk SDHC 4Gb and 8Gb. I'm sure if a good one.

Reading and studiyng again your post (Marcus's one) I was only able to update U-Boot that, that now, is version 3.4.27.

When I informed Jason that unfortunately into my package there was NOT the 4Gb SD card I ordered with the SheevaPlug he gave me the link to the image if the SD in order to recreate it. I would like to try also this way but I do not know which tools I have to use to create the image with my XP . Should I use the USB Image tool?

In the desperate case we will not able to fix it do you think I have any chance to ask for an RMA?

The actual status of my SheevaPlug are these: (Printenv and Reset results at the bottom of the message)

Thanks again for your support.

Marco

PRINTENV
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
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
ethaddr=00:50:43:01:62:d4
cesvcid=ULULULULULULPPULULULULULDA
run_diag=no
bootargs_root_mmc=root=/dev/mmcblk0p2=rootdelay=5
bootargs_root_nand=ubi.mtd=1=root=ubi0:rootfs rootfstype=ubifs
bootcmd_nand=setenv=bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root_nand); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
console=console=ttyS0,115200=mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
real_bootcmd=run=bootcmd_mmc; run bootcmd_nand
recover1=setenv=mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run=recover3
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_usb=usb start; ext2load usb 0:1 0x0800000 /uInitrd; ext2load usb 0:1 0x400000 /uImage
bootargs_console=console=ttyS0,115200
bootargs_root=root=/dev/mmcblk0p2
bootcmd_mmc=mmcinit; ext2load mmc 0 0x0800000 /uInitrd; ext2load mmc 0 0x400000 /uImage
bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_mmc; bootm 0x400000 0x0800000
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 root=/dev/mmcblk0p2

Environment size: 2142/131068 bytes
Marvell>>


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

U-Boot 1.1.4 (Dec 23 2009 - 13:32:43) Marvell version: 3.4.27

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]
Hit any key to stop autoboot:  0
Error! cmd : 8, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
No MMC card found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 00400000 ...
Bad Magic Number
Marvell>>