[U-Boot] Not able to boot using zImage
Hi all,
I've some problems trying to boot a zImage with following command after load the zImage and the fdt file on memory:
U-Boot > fdt addr ${dtbaddr}; fdt resize; bootz ${loadaddr} - ${dtbaddr}
But the sistem stops at Starting kernel ...
File transfer via NFS from server 192.168.2.245; our IP address is 192.168.2.242 Filename '/srv/nfs/sandbox/0/am335x/boot/zImage'. Load address: 0x80000000 Loading: ################################################################# done Bytes transferred = 4011728 (3d36d0 hex) link up on port 0, speed 100, full duplex Using cpsw device File transfer via NFS from server 192.168.2.245; our IP address is 192.168.2.242 Filename '/srv/nfs/sandbox/0/am335x/boot/am335x-base0033.dtb'. Load address: 0x81600000 Loading: ###T T Abort ## Flattened Device Tree blob at 81600000 Booting using the fdt blob at 0x81600000 reserving fdt memory region: addr=81600000 size=3000 Loading Device Tree to 8fe3b000, end 8fe40fff ... OK
Starting kernel ...
The same commands using the uImage instead of zImage works without problems. Is expected to work ? Any clue before diving into the problem ?
Thanks in advance, Enric
On Thu, Jun 20, 2013 at 12:27:02PM +0200, Enric Balletbo Serra wrote:
Hi all,
I've some problems trying to boot a zImage with following command after load the zImage and the fdt file on memory:
U-Boot > fdt addr ${dtbaddr}; fdt resize; bootz ${loadaddr} - ${dtbaddr}
[snip]
The same commands using the uImage instead of zImage works without problems. Is expected to work ? Any clue before diving into the problem ?
Same kernel tree? And you're setting bootargs before you do any of the above?
Hi Tom,
Thanks for your quick reply.
2013/6/20 Tom Rini trini@ti.com
On Thu, Jun 20, 2013 at 12:27:02PM +0200, Enric Balletbo Serra wrote:
Hi all,
I've some problems trying to boot a zImage with following command after load the zImage and the fdt file on memory:
U-Boot > fdt addr ${dtbaddr}; fdt resize; bootz ${loadaddr} - ${dtbaddr}
[snip]
The same commands using the uImage instead of zImage works without problems. Is expected to work ? Any clue before diving into the problem ?
Same kernel tree? And you're setting bootargs before you do any of the above?
Yes, same kernel tree and I set the bootargs before. But I think it was my bad, it's not an u-boot problem as I tested on beaglebone and works.
The difference between the two cases I tested are the address. The one that doesn't work using zImage and works with uImage is
dtbaddr=0x81600000 loadaddr=0x80000000
If I change the addresses like the used in beaglebone, then works
dtbaddr=0x80200000 loadaddr=0x80F80000
I need to check exactly what is thge problem with these addresses. Anyway it's not an u-boot problem. Thanks for the support.
Best regards, Enric
--
Tom
participants (2)
-
Enric Balletbo Serra -
Tom Rini