Hi folks,

is there a package of the above around somewhere?
--
tnx & cheers

Hi rooster, though pingtoo's versions works for me same issue with yours as pancho reported.

Marvell>> version

U-Boot 1.1.4 (Dec 27 2009 - 22:03:21) Marvell version: 3.4.27 - pingtoo patch.01
Marvell>> bubt u-boot-rd88f6281Sheevaplug_400db_nand.bin
Using egiga0 device
TFTP from server 194.a.b.c; our IP address is 194.a.b.d
Filename 'u-boot-rd88f6281Sheevaplug_400db_nand.bin'.
Load address: 0x2000000
Loading: #################################################################
         ############################
done
Bytes transferred = 474592 (73de0 hex)

**Warning**
If U-Boot Endiannes is going to change (LE->BE or BE->LE), Then Env parameters should be overriden..
Override Env parameters? (y/n) n
Erase 0 - 655360 ...
Copy to Nand Flash...
done
Marvell>> reset
[...]
Marvell>> version

U-Boot 1.1.4 (Dec 29 2009 - 13:18:27) Marvell version: 3.4.27
Marvell>> run bootcmd_sd
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0

2860756 bytes read
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.3
   Created:      2010-01-07  23:31:19 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2860692 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

Hey pingtoo,


superb - works like a charm, now! :-) To you and all working a this a big thanx!


As far as I recall all of my SD cards show this error message, but none of my SDHC. Would this mean that it will be more save to use SDHC rather than SD as the plug ignores the message or can not offer the right voltage level?

And maybe two other notes while fixing the version. There are some little blemish in the "help" output
 IMO all command explanations should be aligned (if allowed by the command
 word lenght) starting with a dash and just start with a lower capital character and the
 sentences should end without a dot "."
 On command "map": change "Diasplay" to "display"

And I noticed this strange? behavior: while I made the update of the uboot I didn't reset the environment variables.

since then it came up with

[...]
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB
[...]
Marvell>> resetenv
Erase Env parameters offset 0xa0000... done
Warning: Default Environment Variables will take effect Only after RESET
Marvell>> reset
[...]
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
*** Warning - bad CRC or NAND, using default environment

Flash:  0 kB
[...]


I was upset when I first read it, because I thought I screwed something now.

Is "bad" really the right word here!? Shouldn't we better use "empty"?

Without modifying any environment variable I just did a
Marvell>> saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
Marvell>> reset
[...]
Marvell>> saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
Marvell>> reset
[...]

and the error is gone again. (just my 2 cent)

In .27 I first loaded the same kernel image once from usb (booting) and once from SD to the same memory location (having the strange idea that the ext2load in .27 might not fully load the image). Hence "CRC" error:

Marvell>> usb start
(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
Marvell>> fatload usb 0:1 0x8000000 /uimage.bin
reading /uimage.bin
...

2861324 bytes read
Marvell>> mmcinit
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0
Marvell>> ext2load mmc 0:1 0x8000000 /uImage

2861324 bytes read
Marvell>> bootm 0x8000000
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

BTW0: why does USB START report 2 and then just 1 USB device to be found? Is there another internal device connected by usb?!
BTW1: someone an idea, why the MMCINIT has the error message with SDs. As far as I can tell I don't get that message if I use SDHC!? And what does that message mean?

Another test .23 vs .27. I loaded the same kernel image once from usb (booting) and once from SD to different memory locations and did a memory comparison (cmp.b). When using .23 the loaded image in RAM is identical, if loaded with .27 they aren't (see attached files).

Came to the strange idea that the issue might be caused by an offset, but at least it's not as simple as

Marvell>>  ext2load mmc 0 0x8000000 /uImage

2861324 bytes read
Marvell>> bootm 0x8000001
## Booting image at 08000001 ...
Bad Magic Number
Marvell>> bootm 0x7ffffff
## Booting image at 07ffffff ...
Bad Magic Number
Marvell>> bootm 0x8000000
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
Marvell>> ext2load mmc 0:1 0x8000000 /uImage

2861324 bytes read
Marvell>> bootm 0x8000000
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

Though FAT from an USB-Pen works

Marvell>> usb start
(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
Marvell>> fatload usb 0 0x8000000 /uimage.bin
reading /uimage.bin
...

2861324 bytes read
Marvell>> bootm 0x8000000
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[...]
Debian GNU/Linux 5.0 debian ttyS0

debian login:

no, sure, np. Just happy to understand what I'm doing.

BTW: did another test with 3.4.23 vs. 3.4.27 and an SD formatted with FAT. With this .27 also has an issue though it looks a bit different. The fatload command goes wrong with .27 already (see attached file).

Saw you posted a startup script, but I didn't had time to look at it, yet. However will do for sure. Anyway I think the script won't work around the issue some of use are facing booting from SD since uboot 3.4.24!?

yep, you're right - unfortunately my sequence wasn't the best one to go with. I'll cleared the ram as advised between the tests now and the result is as you expected.

@ccp: Planning to do some more testing as advised, but I spent this morning to prepare some SD-Cards for another test:


@rooster: yes, I noted the error, however as I get it either with 2.4.23 and 2.4.27 I didn't paid it too much attention, so far.

I hoped that the issue might be related to SD vs SDHC cards, but I tested a few this morning, which makes me think it doesn't.

I just noted that the error message doesn't show up if I use an SDHC (alike) card.

Summary: I cloned my working Debian RFS used on my test plug to a couple of other SDs (see attached jpg; only one still had a copy of the Ubuntu FS from my primary plug).

As with uboot 2.4.23 all work, as with uboot 2.4.27 all get a "Bad Data CRC" and they fall back to the kernel in NAND (see attached txt-files).

If you want to play around with my image: I made one a couple of days ago for a friend and put onto a network share. I can send you details if just like, just contact me.

Would it be possible to build and send me some (four) 2.3.24 flavors, each just adding one of the four fixes you made from .23 -> .24?


 Thus I could at least identify with fix introduces the behavior I see.

But isn't that exactly what confuses me!?! I again made a small test with 4 ext2load / bootm combinations, both for uboot 3.4.23 and 3.4.27 (nothing changed else!). I call them x:y where x stands for the number of trailing "0"s in ext2load command and y for the number of trailing zeros in bootm statement.

With 3.4.23 all combinations except for the first (6:5) boot the Debian from SD
With 3.4.27 all combinations except for the first (6:5) give a "Bad Data CRC".

For both uboot 3.4.23 and 3.4.27 the combination 6:5 gives a Bad Magic Number (see txt-files attached).

I once used the instructions at http://computingplugs.com/index.php/Booting_entirely_off_an_external_USB_device#Copy_over_the_default_kernel_and_filesystem to move the FS from the NAND to an SD-Card. I guess you can do the same adapting it for USB-Stick to SD.

However I would even would make an easier approach: making an image (e.g. with Winimage) of my USB-Stick and put the image back to my SD.

Of course you'd need to adapt the boot parameters as well, but because the confusion I have with those myself I won't make any recommendations ;-)

I'm really getting confused: I find various versions in the Wikis, e.g.

http://www.plugcomputer.org/plugwiki/index.php/U-Boot_Quick_Reference
http://www.plugcomputer.org/plugwiki/index.php/External_Hard_Drives
http://computingplugs.com/index.php/Booting_entirely_off_an_external_USB_device
http://www.cyrius.com/debian/kirkwood/sheevaplug/unpack.html

Or does it depend on whether it's NAND, USB or SD?

However, either a get a "Bad Magic Number" error (bootm 0x00800000)
ot the "Bad Data CRC" error (bootm 0x008000000)

BTW: whether bootm 0x00800000 or bootm 0x008000000 makes no difference

Hit any key to stop autoboot:  0
Marvell>> mmcinit
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0
Marvell>> ext2load mmc 0 0x00800000 /uImage

2861324 bytes read
Marvell>> bootm 0x008000000
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

However with uboot 3.4.23

Marvell>> bubt u-boot-3.4.23.bin
Using egiga0 device
TFTP from server a.b.c.5; our IP address is a.b.c.253
Filename 'u-boot-3.4.23.bin'.
Load address: 0x2000000
Loading: #################################################################
         ############################
done
Bytes transferred = 474596 (73de4 hex)

**Warning**
If U-Boot Endiannes is going to change (LE->BE or BE->LE), Then Env parameters should be overriden..
Override Env parameters? (y/n) n
Erase 0 - 655360 ...
Copy to Nand Flash...
done
Marvell>> reset
ü
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Nov  4 2009 - 12:58:36) Marvell version: 3.4.23

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
Marvell>> mmcinit
Error! cmd : 8, err : 0201
SDa0000 found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0
Marvell>> ext2load mmc 0 0x00800000 /uImage

2861324 bytes read

Marvell>> bootm 0x00800000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.32.2 (kelly@speedy) (gcc version 4.2.1) #1 PREEMPT Fri Dec 18 22:54:28 MST 2009

Unfortunately no:

Hit any key to stop autoboot:  0
Marvell>> ext2load mmc 0 0x00800000 /uImage
** Bad partition 1 **
Marvell>> mmcinit
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0
Marvell>> ext2load mmc 0 0x00800000 /uImage

2861324 bytes read
Marvell>> bootm 0x00800000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

Yes, must be me being mistaken loading the kernel from NAND, but having the RFS running from SD :-(

Marvell>> setenv bootcmd_nand 'setenv bootargs $(bootargs_sd); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
Marvell>> run bootcmd_nand

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

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.32.2 (kelly@speedy) (gcc version 4.2.1) #1 PREEMPT Fri Dec 18 22:54:28 MST 2009
[...]
Starting periodic command scheduler: crond.

Debian GNU/Linux 5.0 debian ttyS0

debian login:

Puh, though really having no clue want I'm doing here neither understanding the bits and peaces of the boot variables I think I got it working, once!

While I was trying to boot the kernel from NAND but using the RFS from SD I figured that my NAND and SD strings differ at the following part (red):

bootargs_sd=console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=5 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw ip=a.b.c.253:a.b.c.254:a.b.c.1:255.255.255.0:DB88FXX81:eth0:none
bootargs_nand=rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=a.b.c.253:a.b.c.254:a.b.c.1:255.255.255.0:DB88FXX81:eth0:none
bootcmd_nand=setenv bootargs $(bootargs_nand); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_sd=setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage; bootm 0x8000000

Thus I think I changed it to

setenv bootcmd_sd 'setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage; bootm 0x800000'

and it worked as I could log into the Debian.

However while trying to make it permanent it's going wrong again.