
Hi Detlev,
you were right. I can't debug, but I followed the code writing in a memory buffer and it doesn't hang, but the output display is not working.
I understand now that the problem is in the Linux kernel (version 2.6.15, for U-boot I am using 1.1.6) because the command "bdinfo" shows me the parameters and all is OK. I thought I would need to initialize the console because U-Boot has already done. I know my problem is now out of the reach of this mailing-list, but anyway, I would appreciate if you could tell me where and when I should initialize the console in the Linux kernel (in my case I am using a MPC866 and the console is on the SCM1).
Thanks,
Raúl Moreno
Detlev Zundel dzu@denx.de Detlev Zundel 08/08/2007 18:54
Para: raul.moreno@telvent.abengoa.com
cc: u-boot-users@lists.sourceforge.net
Asunto: Re: [U-Boot-Users] Linux hangs just at the beginning
Hi Raul,
U-Boot is already running in my board. I configured the Flash, SDRAM,
SRAM,
FEC (ethernet) and console. Apparently all is working and I can trace the code just before the call in order to transfer the control to Linux, that is: (* kernel) (kbd, initrd_start, initrd_end, cmd_start, cmd_end);
Congrats.
There it is supposed the U-Boot finishes its operation and then the
Liinux
kernel takes the control, but it hangs.
Are you sure it hangs or is it just that you don't see any output? Are you sure you are passing a correct console parameter to Linux? Search the archives, many people (including myself) already considered a perfectly working Linux kernel to be dead just because they did not see any console output...
I did the Linux image with entry address and load address 0x0. U-Boot can check the Multi-image correctly. So I don't know where the problem is. I think the problem is in the Linux image, not in U-Boot, I can not assure it. I can't trace the Linux booting because it hans at the beginning, even
the
console is not initialized.
Hook up a debugger if at all possible.
One question more, I wouldn't have to configure the memories again, I mean, Linux doesn't participate in the configuration of the memories because U-Boot has already done, right?
If the parameter passing between U-Boot and the kernel works, then yes, this is correct.
By the way, what kernel version on what arch are you trying to boot?
Cheers Detlev
-- "Win32 sucks so hard it could pull matter out of a Black Hole." -- Pohl Longsine -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de