[U-Boot] Beginners Questions on modding a NAS

[Michael Cashwell]

On Mar 4, 2013, at 10:40 AM, JPT <j-p-t at gmx.net> wrote:

> It's a Netgear ReadyNAS Duo V2, and the original sofware sucks. ;)
> standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
> bootcmd=nand read.e 0x1200000 0x200000 0x600000;nand read.e 0x2000000 0x800000 0x1000000;bootm 0x1200000 0x2000000

Strange for a NAS to have a u-boot environment variable called "mvPhoneConfig". But anyway...

> I dumped the kernel from mtd2, it is:
> u-boot legacy uImage, Linux-2.6.31.8.duov2, Linux/ARM, OS Kernel Image (Not compressed), 3442208 bytes, Tue Aug 28 05:21:43 2012, Load Address: 0x00008000, Entry Point: 0x00008000, Header CRC: 0xDA1ECA31, Data CRC: 0x269C27DE
> 
> I tried to load the kernel through tftp, but it crashed:
> Marvell>> go  0x02000000


You're likely are off the rails here. Note the last command in your standalone and bootcmd variables: bootm.

If your kernel is in a uImage (a u-boot wrapper) you have to use bootm to start it. Further, Linux kernels expect hardware information either as an ATAG list or a device tree. bootm sets this up before passing control but a bare "go" doesn't.

Try bootm instead of go.

HTH,
-Mike