Hi,
I find my problem! it was like you said a problem with the command line in u-boot. I had defined CONFIG_EXTRA_ENV_SETTINGS before CONFIG_BOOTARGS, that's it! and you have to do the opposite.
Thanks for your help, Guillaume Berthelom
Leonid a écrit :
Grant is right - kernel command line (defined by u-boot variable "bootargs") is also very important, though it's difficult to see how wrong command line can crash printk(). It definitely can prevent serial output from showing up on console though.
Leonid.
-----Original Message----- From: u-boot-users-bounces@lists.sourceforge.net [mailto:u-boot-users-bounces@lists.sourceforge.net] On Behalf Of Grant Likely Sent: Wednesday, May 02, 2007 10:19 AM To: Guillaume Berthelom Cc: u-boot-users@lists.sourceforge.net Subject: Re: [U-Boot-Users] problem to load uImage but not zImage (onvirtex-4 board)
On 5/2/07, Guillaume Berthelom guillaume.berthelom@cleode.fr wrote:
When I load the zImage directly with xilinx xmd debugger, the kernel
start
without problem (if I don't have KGDB or SERIAL_TEXT_DEBUG option in
my
kernel config). But when I try to load the uImage with u-boot, the
kernel
start but crach befor I can see something on output. The kernel start because I debug it and the platform_init is ok,
setup_arch
too and it crach after ppc4xx_setup_arch at printk(KERN_INFO "Xilinx
ML403
Reference System (Virtex-4 FX)\n") line when the kernel access in
printk.c.
I use the opb_uart16550 IP in my Xilinx design and the associat
drivers in
u-boot and linux.
What are you passing for the kernel command line? Can you post your .config?
Cheers, g.