[ELDK] U-Boot version required to boot kernel 3.10 on PowerPC

[Peter Oruba]

Thank you for the prompt reply. The uboot environment looks like follows:

baudrate=115200

netdev=eth0

netmask=255.255.255.0

ipaddr=192.168.100.101

serverip=192.168.100.200

gatewayip=192.168.100.1

ntpserverip=192.168.100.1

hostname=motion5200b

blobaddr=0x001f0000

maddr=0x00400000

uaddrs=0xfff00000

uaddre=0xfffdffff

uprg=setenv uprotoff protect off ${uaddrs} ${uaddre};setenv uerase erase
${uaddrs} ${uaddre};setenv uget tftpboot ${maddr} ${uboot};run u

get;setenv uprog cp.b ${maddr} ${uaddrs} ${filesize};run uprotoff uerase
uprog

daddrs=0xfffe8000

daddre=0xfffeffff

dprg=setenv dprotoff protect off ${daddrs} ${daddre};setenv derase erase
${daddrs} ${daddre};setenv dget tftpboot ${maddr} motion5200b.dt

b;run dget;setenv dprog cp.b ${maddr} ${daddrs} ${filesize};run dprotoff
derase dprog

kaddrs=0xffc80000

kaddre=0xffefffff

kprg=setenv kprotoff protect off ${kaddrs} ${kaddre};setenv kerase erase
${kaddrs} ${kaddre};setenv kget tftpboot ${maddr} ${bootfile};ru

n kget;setenv kprog cp.b ${maddr} ${kaddrs} ${filesize};run kprotoff kerase
kprog

faddrs=0xff480000

faddre=0xffc7ffff

fprg=setenv fprotoff protect off ${faddrs} ${faddre};setenv ferase erase
${faddrs} ${faddre};setenv fget tftpboot ${maddr} initrd.boot;ru

n fget;setenv fprog cp.b ${maddr} ${faddrs} ${filesize};run fprotoff ferase
fprog

baudrate=115200

rootpath=/tftpboot/rootfs

ramargs=setenv bootargs root=/dev/ram rw ramdisk_size=40000

nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath}

addip=setenv bootargs ${bootargs}
ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off
panic=2

addipd=setenv bootargs ${bootargs} ip=::::${hostname}:${netdev}:dhcp
panic=2

addcons=setenv bootargs ${bootargs} console=${console},${baudrate}

flash_self=run ramargs addip addcons;bootm ${kernel_addr} ${ramdisk_addr}

flash_nfs=run nfsargs addip addcons;bootm ${kernel_addr}

net_nfs=tftp ${kernel_addr} ${bootfile};run nfsargs addip addcons;bootm

boot_nfs=tftp ${kernel_addr} ${bootfile_fdt};tftp ${fdt_addr}
${fdt_file};setenv console ttyPSC0;run nfsargs addip addcons adddebug;bootm

 ${kernel_addr} - ${fdt_addr}

upgall=run dprg; run kprg; run fprg

mtdids=nor0=MOTION5200B

mtdparts=mtdparts=MOTION5200B:64m(datafs),48m(optfs),4608k(logs),8m(initrd),2560k(kernel),896k(uboot),32k(tmcfg),32k(dtb),32k(env1),32k(e

nv2)

bootfile=uImage_revG

bootfile_fdt=uImage_revG

fdt_file=motion5200b.dtb

uboot=u-boot.bin_revG

load=tftp ${kernel_addr} ${uboot}

ramdisk_addr=0x00410000

ramdisk_file=uRamdisk

untethered_args=setenv console ttyPSC0;run ramargs addip addcons

boot_flash=run untethered_args;bootm ${kaddrs} ${faddrs} ${daddrs}

dhcp_bootm=dhcp;run untethered_args;bootm ${kaddrs} ${faddrs} ${daddrs}

erase_env=protect off 0xffff0000 0xffffffff; erase 0xffff0000 0xffffffff;
reset

setup=setenv serverip 192.168.100.200; setenv ipaddr 192.168.100.100;run
kprg;run fprg;run dprg;setenv rootpath /tftpboot_init/rootfs_ini

t;run t

update=protect off fff00000 fffdffff;erase fff00000 fffdffff;cp.b 200000
fff00000 ${filesize};protect on fff00000 fffdffff

bootfile=uImage

t=tftp ${kernel_addr} ${bootfile_fdt};tftp ${fdt_addr} ${fdt_file};setenv
console ttyPSC0;run nfsargs addip addcons;bootm ${kernel_addr}

- ${fdt_addr}

u=run untethered_args;bootm ${kaddrs} ${faddrs} ${daddrs}

du=dhcp;run u

dt=dhcp;run t

autoload=no

machinename=Factory Fresh Default

console=ttyPSC0

bootargs=root=/dev/ram rw ramdisk_size=40000 ip=192.168.100.101:192
.168.100.200:192.168.100.1:255.255.255.0:motion5200b:eth0:off panic=2

console=ttyPSC0,115200

ethaddr=00:50:c2:df:81:c0

eth1addr=00:50:c2:df:81:c1

partition=nor0,0

mtddevnum=0

mtddevname=datafs

bootcmd=run u

bootdelay=10

kernel_addr=0x400000

fdt_addr=0x100000

stdin=serial

stdout=serial

stderr=serial

ethact=FEC ETHERNET


Like already mentioned, this environment settings already work with kernel
2.6.38. There was an issue with the kernel TFTP loading address so that the
kernel was overwriting itself when unpacking, but that got solved thanks to
the excellent ELDK FAQ.

Thanks,

Peter