[U-Boot-Users] boot kernel hanags with u-boot
Hi , I have booted my kernel (montavista) using flattened device tree that i supply as third argument in bootm command through U-boot .But kernel hangs after uncompressing the kernel and ramdisk image and i have attached the screen shot as attachment , of it for your reference.Infact ihave checked IMAP_ADDR and CFG_IMMR both are same in my case.Can anyone help me out where exactly i am going wrong.I could be of great help if anyone reply me ASAP as we already running out of time. Regards, K.V.Ramesh
Hi Ramesh,
I have booted my kernel (montavista) using flattened device tree that i supply as third argument in bootm command through U-boot .But kernel hangs after uncompressing the kernel and ramdisk image and i have attached the screen shot as attachment , of it for your reference.Infact ihave checked IMAP_ADDR and CFG_IMMR both are same in my case.Can anyone help me out where exactly i am going wrong.I could be of great help if anyone reply me ASAP as we already running out of time.
As we don't have the sources for your kernel tree, you cannot hope for much help on this specific hangup here (apart from being offtopic on the U-Boot mailing list).
Attach a debugger or ask the guys you have the kernel from.
Cheers Detlev
On 7/23/07, Detlev Zundel dzu@denx.de wrote:
Hi Ramesh,
I have booted my kernel (montavista) using flattened device tree that i supply as third argument in bootm command through U-boot .But kernel hangs after uncompressing the kernel and ramdisk image and i have attached the screen shot as attachment , of it for your reference.Infact ihave checked IMAP_ADDR and CFG_IMMR both are same in my case.Can anyone help me out where exactly i am going wrong.I could be of great help if anyone reply me ASAP as we already running out of time.
You need a patch to u-boot to fix initrd/fdt loading. As a workaround, you can try: setenv initrd_high 0x1000000
This will restrict the ramdisk to the first 16M, and thus the flat device tree, too. You can play around with that number. You want to make sure that the start of the initrd image is within the first 16M (address < 16M) of memory. If you can't do that, you'll need to grab the patch to fix that bug.
It can be found here: http://opensource.freescale.com/pub/scm/u-boot-85xx.git at the top of the tree. You can use gitweb to grab it, too:
http://opensource.freescale.com/git?p=u-boot-85xx.git;a=commitdiff;h=41fcfec...
Andy
In message 2acbd3e40708052225r64aaa5b7ncb354a07085e127c@mail.gmail.com you wrote:
You need a patch to u-boot to fix initrd/fdt loading. As a
...
It can be found here:
...
Or use u-boot-testing, which should have this incorporated (or even mainline, as I will merge -testing into main in the next few hours).
Best regards,
Wolfgang Denk
participants (4)
-
Andy Fleming -
Detlev Zundel -
rameah nathan -
Wolfgang Denk