This is very strange, I don't understand why you kernel boot does not display any messages, did you try to load kernel from tftp and boot?

After you try ppmt suggestion and if you already did tftp boot still not success, than we have to start from beginning, we need to get in sync. first we need to verify your u-boot version, then u-boot env. (in case typo somewhere we can see, please try cut&paste result) also bdinfo output.

OK, since yo upgrade u-boot, we can do some debugging. lets start by building some common understanding. What is your u-boot version? where do you think you root file system is? i.e usb device? NAND? or SD card? what is your kernel version? do you know if your kernel need initrd/initramfs?

please post output of following command at Marvell>> prompt,

What is boot error? Your u-boot environment looks OK. The ${x_cmd_usb} at beginning of  x_bootcmd is unnecessary but it doesn't hurt either. have you try to use kernel from http://sheeva.with-linux.com/sheeva/?

Your boot command argument setup to use NAND as root file system is this your intention?

You don't need to setup mainLineLinux or archNumber, those are for special patched u-boot for sheevaplug. Your u-boot is mainline das u-boot it does use those variables.

Your u-boot version looks OK, there are few more enhancement after your version on the ARM code but does not make it any better if all you want just boot linux from NAND.

there are some parameters is necessary to boot linux on a plug, like console=ttyS0,xxxx and root=??? you must setup or else linux will not come up. there may be something else depend on linux distro you are using. All these parameters are set in u-boot environment.

if you post output of "printenv" we can start from there.

Good luck

Thanks for the information, I looked at the datasheet, because the 1606E designation, I am not sure if they are same. I will try to research on the FreeBSD topic.

Thanks.

If you know for sure you have formated your SD card ext2, than why did you use "fatload"? even your own "bootcmd" setup run ext2load.

current dreamplug u-boot have "sleep" command.

Anybody know sample code on how to program MX25L1606 NOR flash? I work on my u-boot code but hit a problem here, the u-boot/driver/mtd/spi/macronix.c does not have support code for this chip. I googled cannot any reference on this either.

Any info appreciated.

Read my code again, I said load u-boot.elf

 

You can test u-boot without writing it in to storage. you will need to have access to u-boot elf file, not the .kwb file. I use openond to load it into ram.

I think the procedure is:
than from second windows I could be wrong since I don't have access to my plug now.

Good luck

The error "No init found" usually assoicate root file system is to setup incorrect, your root file system should have /sbin/init, so said your kernel command line parameter "root=sdb1" than if you take your sdb to a pc mount it on /mnt, you should see /mnt/sbin/init. otherwise you should try to rebuild your root file system.

Good luck

Thanks for the information. if you have sheevaplug or guruplug they come with a thing that use to inter change between power prong or this thing which allow you connect power cable to plug.

anyway, I will replace my root file system (RFS) with gentoo based system I am not too worry about losing it :-)


Thanks.

Good I was little bit of worry about the "saveenv" not working because the dreamplug is base on spi/NOR which the main stream u-boot is not clear on supporting kirkwood. you sure when you boot up u-boot did not said something about environment CRC error using default?

I will start working on my u-boot

Thanks.

What is current version of u-boot?

It looks like the usb key you use is not compatible with your sheevaplug, if you successful upgraded u-boot then I suggest find another usb key to try however if u-boot was not upgraded then please continue on the upgrade process, I am not a big fan on the sheeva-installer, may be we can use a manual process to upgrade the u-boot. I need to dig around to how to do this so please stay tuned.

good luck

First of all, I think you have failed to upgrade u-boot. from your early post, you state that you load u-boot.bin in memory but I did not see any description you write it back to nand. I could give you instruction on how to write the u-boot.bin in mmeory to NAND but I am not in front of plug, I don't trust my memory to give the right instruction so please search this fourms, I think you can find the right command sequence on how to write the uboot back to NAND.

the reset of message most likly because uboot 1.1.4 (3.4.16) have problem with USB device, so once you succeed upgrade u-boot you should have no problem.

Good luck