• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2] 3
16  Hardware and U-Boot firmware / U-Boot stuff / Re: Need original bootcmd on: April 23, 2009, 12:37:31 PM
Gah.

There needs to be a public announcement somewhere.
17  General Category / General Discussion / Re: Updated Marvell Docs and Files on: April 23, 2009, 11:01:25 AM
The kernel panic is solved.  The zipped jffs2 image posted on Marvell's site is corrupt.  Use the one from your disk and it works great.

See here:
http://openplug.org/plugforum/index.php?topic=139.msg820#msg820
18  Hardware and U-Boot firmware / U-Boot stuff / Re: Need original bootcmd on: April 23, 2009, 10:57:11 AM
Yep, that's the answer.  The jffs2 image posted on the website is corrupt.  My plug now works fine with the image from the disk.

See here:
http://openplug.org/plugforum/index.php?topic=139.msg820#msg820

*shakes fist at Marvell*
19  Hardware and U-Boot firmware / U-Boot stuff / Re: 'Cannot open root device "mtdblock2"' when flashing from USB. on: April 23, 2009, 10:55:04 AM
I got it.  Finally.

The root filesystem image that Marvell has posted on their site is corrupt.  The stupid thing stole three days of my life while I tried to figure it out.

I got the idea after reading your suggestions over here:
http://openplug.org/plugforum/index.php?topic=133.0
I pulled out the original CD, and noticed that the filesystem zip is 132MB, whereas the one on their site is only 538k.  That should have been a strong indicator that something was wrong with the website one, but it zipped out to a big file, so I assumed it just had some amazingly good compression.

Anyway, I flashed my plug using the image from the disk, and it works fine.  It's currently the same version number as what they have posted online (9.0.5).

So, that's the answer: use the image from the disk, not from the website.  Thanks plugcomp for all the help.  No thanks to Marvell for wasting our time with corrupt crap left on their site for long periods of time.

If anyone has lost their disk, I'm uploading the zip of the 9.0.5 filesystem right here:
http://djpandemonium.com/plug/SheevaPlug_FileSystem.zip
20  Hardware and U-Boot firmware / U-Boot stuff / Re: 'Cannot open root device "mtdblock2"' when flashing from USB. on: April 23, 2009, 09:37:46 AM
I just did a NAND flash erase from uboot and then flashed it using a new USB drive wit the images freshly downloaded from the Marvell site.  Same thing.  It finishes writing mtd2 at 87c0000 and does a kernel panic when I reboot.

Plugcomp, do you still have the ubuntu image that you successfully flashed?  What is the filesize?  The one I download from Marvell is 135.9MB (142,475,264 bytes).
21  General Category / Success stories / Re: Sound anyone? on: April 23, 2009, 08:07:08 AM
On a (possibly) related note, while trying to do a USB flash of the latest kernel and image, I notice that the kernel from Marvell's site starts ALSA.  I thought this was quite odd, though I imagine it is useful for what you are doing.
22  Hardware and U-Boot firmware / U-Boot stuff / Re: 'Cannot open root device "mtdblock2"' when flashing from USB. on: April 23, 2009, 08:04:23 AM
Ah, that's it.  Mine is 0x87c0000.

But the question is "why?".  I've redownloaded the image twice, and one of the times I reformatted my USB drive one of the times and started from scratch.

I'm about to try it with a different flash drive.  I'll let you know what happens.
23  Hardware and U-Boot firmware / U-Boot stuff / Re: 'Cannot open root device "mtdblock2"' when flashing from USB. on: April 22, 2009, 11:10:58 PM
Oh, and to save you the time bfmorgan, don't bother trying to just drop in the virgin bootcmd and/or bootargs.  Tried it, and it locks up after booting the kernel.

To me, it seems like the problem is not in u-boot, but in the root filesystem.  When I boot from the USB drive images I should be able to mount mtd2 and see all the files just fine.  Instead, I'm getting a CRC error, and all I can see are the empty root directories with three executables in /bin.  Missing critical files would cause the init kernel panic that we're seeing, wouldn't it?  If what I'm seeing is correct when I mount mtd2, then we're missing critical files and a whole lot more.
24  Hardware and U-Boot firmware / U-Boot stuff / Re: 'Cannot open root device "mtdblock2"' when flashing from USB. on: April 22, 2009, 10:52:00 PM
I can.  I have access to a second plug, still in the box.

Here's a virgin printenv from it on its second boot:
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_root=root=/dev/nfs rw
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:C3:C2
run_diag=no
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
bootcmd=nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
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

Environment size: 1330/131068 bytes
Marvell>>
25  Hardware and U-Boot firmware / U-Boot stuff / Re: 'Cannot open root device "mtdblock2"' when flashing from USB. on: April 22, 2009, 08:59:34 PM
I've reflashed it now 11 times.  I only mounted the filesystem that last time just to take a peek and make sure the filesystem was all there.  I've done it at least five or six times identical to that time, except without mounting it.  Still nothing.

Frankly, I'm out of ideas.  The only other thing I can think to try is flashing it from NFS, though I have my doubts about whether that will turn out any differently.  I can't think why it would.  I went the USB method because I thought it would be easier and take less time.

Out of curiosity, had you used your plug at all before you flashed it?  What does your u-boot print dump look like?
26  Hardware and U-Boot firmware / U-Boot stuff / Re: 'Cannot open root device "mtdblock2"' when flashing from USB. on: April 22, 2009, 06:09:42 PM
There is something really wrong.

I reformatted my USB drive to ext3, and redownloaded both the filesystem and USB recovery zips from the Marvell site before unzipping them to the USB drive.  I verified that file sizes of the images were appropriate before unmounting the device.  I then followed the USB recovery documentation for reflashing.  After flashing mtd1 and mtd2, I mounted mtd2 at /mnt and took a look at it.  There's not much in there.  Most of the root directory structure is there, and there are a few binaries in /bin, but other than that it's completely empty.

You can view a log of what's going on here:
http://djpandemonium.com/sheevaflash2.txt
As far as I can tell, there's something really wrong with either the flashing process or the NAND memory in the device.

Why is it not flashing successfully?  Does it have to do with the bad eraseblocks?
27  Hardware and U-Boot firmware / U-Boot stuff / Re: 'Cannot open root device "mtdblock2"' when flashing from USB. on: April 22, 2009, 04:51:50 PM
Well, it seems that there's something wrong with either the image I'm flashing, or perhaps the NAND memory in my device.  If I boot onto the USB flash drive and then try to mount the root filesystem, look at what I find:
Code:
-sh-3.2# mount -t jffs2 /dev/mtdblock2 /mnt
-sh-3.2# JFFS2 notice: (310) check_node_data: wrong data CRC in data node at 0x00069000: read 0xc5585480, calculated 0xa78a6243.
JFFS2 warning: (310) jffs2_do_read_inode_internal: Truncating ino #22 to 30236 bytes failed because it only had 16384 bytes to start with!
cd /mnt
-sh-3.2# find
.
./bin
./bin/bash
./bin/bzcat
./bin/bunzip2
./dev
./etc
./lib
./mnt
./opt
./srv
./tmp
./sys
./var
./usr
./boot
./home
./proc
./sbin
./root
./media
./selinux

Woops.

It seems like there's a lot missing there.  I'm going to play around with it some more and see if I can figure out why.
28  Hardware and U-Boot firmware / U-Boot stuff / Re: 'Cannot open root device "mtdblock2"' when flashing from USB. on: April 22, 2009, 10:03:00 AM
Yep.

Code:
Marvell>> print
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_root=root=/dev/nfs rw
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;
ethaddr=00:50:43:d6:13:26
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:82
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
autoload=no
ethact=egiga0
loadaddr=0x2000000
mtd1Size=0x300000
filesize=0x44ad000
bootcmd=nand read.e 0x800000 0x100000 0x300000; bootm 0x800000
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0x00000(u-boot),0x300000@0x100000(uImage)ro,0x1fc00000@0x400000(rootfs)rw root=/dev/mtdblock2
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x300000@0x100000(uImage),0x1fc00000@0x400000(rootfs)rw
mainlineLinux=no
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

Environment size: 1341/131068 bytes
Marvell>>
29  Hardware and U-Boot firmware / U-Boot stuff / Re: 'Cannot open root device "mtdblock2"' when flashing from USB. on: April 22, 2009, 09:51:58 AM
Ah, you're right.  The documentation is missing that argument.

When I use the bootargs you posted I am now able to mount the file system, but then I get a kernel panic due to a missing init.
---
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 124K
scsi 0:0:0:0: Direct-Access     I-Stick2 IntelligentStick 0.00 PQ: 0 ANSI: 2
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
---

Any ideas?
30  General Category / General Discussion / Re: Marvell does not make the SheevaPlug on: April 22, 2009, 09:43:26 AM
Interesting.  This explains why one of the products announced that uses the Sheevaplug (can't remember which it is) has a somewhat different form factor.  They used their own design for manufacturing.

I don't see, however, why you couldn't just use the original design to have Globalscale manufacture it, except with a custom decal, packaging,  and software.

If/when you get access to the extranet, keep us posted on what is available there.
Pages: 1 [2] 3