[U-Boot-Users] Noob question regarding uncompressed kernel image

[Peter Poulsen]

Here we try again.

First the environment info:
=> print
ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate
$othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr
$fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off
console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr
$fdtfile;bootm $loadaddr - $fdtaddr
baudrate=115200
loads_echo=1
ethaddr=00:e0:5e:00:e5:14
preboot=echo;echo Type "run nfsboot" to mount root filesystem over NFS;echo
hostname=mpc5121ads
loadaddr=1000000
netdev=eth0
consoledev=ttyPSC0
hostname=mpc5121ads
ramargs=setenv bootargs root=/dev/ram rw
addip=setenv bootargs $bootargs
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off panic=1
addtty=setenv bootargs $bootargs console=$consoledev,$baudrate
flash_self=run ramargs addip addtty;bootm $kernel_addr $ramdiskaddr $fdtaddr
load=tftp 100000 /tftpboot/ads5121/u-boot.bin
update=protect off fff00000 fff3ffff; era fff00000 fff3ffff; cp.b 100000 fff00000
$filesize
upd=run load;run update
ramdiskaddr=2000000
ramdiskfile=rootfs.ext2.gz.uboot
fdtaddr=3000000
ethact=FEC ETHERNET
fdtflashaddr=ffec0000
kernelflashaddr=ffc40000
jffs2boot=setenv bootargs console=$consoledev,$baudrate root=/dev/mtdblock1 rw
rootfstype=jffs2 $otherbootargs; bootm $kernelflashaddr - $fdtflashaddr
fdtfile=mpc5121/mpc5121ads.dtb
rootpath=/tftpboot/mpc5121/rootfs
bootcmd=run nfsboot
bootargs=root=/dev/nfs rw nfsroot=192.168.1.70:/tftpboot/mpc5121/rootfs
ip=192.168.1.75:192.168.1.70:192.168.1.1:255.255.0.0:mpc5121ads:eth0:off
console=ttyPSC0,115200
filesize=3000
fileaddr=3000000
gatewayip=192.168.1.1
netmask=255.255.0.0
ipaddr=192.168.1.75
serverip=192.168.1.70
bootfile=mpc5121/uImage
stdin=serial
stdout=serial
stderr=serial

When I boot I run 'run nfsboot'.

<snip>
>> I make the image like this:
>>
>> mkimage  -A ppc -O linux -T kernel -d vmlinux -C none -n "uImage" uImage
>
> I don't see the (required) "-a" and "-e"  options  in  your  call  to
> mkimage...
>
I didn't know they were required. How do I figure out what they should be?

>> Unfortunately my board boots like this:
>
> Like this? What is "this"? You don't shouw us which exact boot
> commands you used, nor what your environment settings are.
>
> How are we supposed to help you without all this important information?
>
>> ## Booting image at 01000000 ...
>>    Image Name:   uImage
>>    Image Type:   PowerPC Linux Kernel Image (uncompressed)
>>    Data Size:    4242375 Bytes =  4 MB
>>    Load Address: 00000000
>>    Entry Point:  c000000c
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Where is this coming from?
>
>>    Verifying Checksum ... OK
>> OK
>
> If boot time plays a role, you might consider turning off the checksum
> verification - which will take a looong time on an uncompressed kernel
> image. See "verify" environment variable.
>
>> And that was it :-(
>
> No big surprise if you jump right in the middle of nowhere...
>
>> it boots fine, so I think that my vmlinux/vmlinux.bin.gz image is fine.
>
> No, it is not.
>
que? please explain.

<snip>

/peter

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?