[U-Boot-Users] output to serial console stops after uncompressing kernel
Hi All,
We are using Cogent CSB535FS board running Freescale's i.MX21 with U-Boot. We have downloaded the updated linux kernel 2.6.16 from the Microcross site (supposedly patched for the board). The load address and entry address are set to C0600000. And the image is downloaded to C0200000. When we run the bootm command, the kernel unzips but there are no messages on the serial console. The screen buffer dump is as follows:
U-Boot 1.2.0 (Jun 4 2007 - 16:32:54)
BOARD: Cogent CSB535FS DRAM: 64 MB Flash: 8 MB In: serial Out: serial Err: serial => loadb C0200000 ## Ready for binary (kermit) download to 0xC0200000 at 115200 bps... ---------------------------------------------------- C-Kermit>send /BINARY linux-2.6.16/arch/arm/boot/uImage C-Kermit>connect Connecting to /dev/ttyS0, speed 115200 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. ---------------------------------------------------- ## Total Size = 0x000f8a5c = 1018460 Bytes ## Start Addr = 0xC0200000 => bootm C0200000 ## Booting image at c0200000 ... Image Name: Linux-2.6.16-csb Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1018396 Bytes = 994.5 kB Load Address: c0600000 Entry Point: c0600000 Verifying Checksum ... OK OK
Starting kernel ...
ArchID=0x000002a3 output_data: 0xc0008000 Uncompressing Linux.................................................................... done, booting the kernel.
There are no further messages printed on the serial console after the above line. However, the LCD on the board seems to have initialized (kernel configuration also had framebuffer support) and the penguin logo is displayed on the LCD.
We tried changing baud rate but that did not solve the problem. The boot arguments are just the ones setup as default by U-Boot (bootargs=mem=32M console=ttyS0,115200 root=/dev/nfs rw init=/sbin/init ip=on). We have not provided any filesystem yet because we wanted to see output until the filesystem error.
What could be the problem?
Thanks, Midhun.
It seems to me more like a Linux problem then a U-boot problem. According to the screen dump, U-boot has given control to the kernel and is not operating any more. You should check the kernel configuration that it fits your hardware.
participants (2)
-
Midhun Agnihotram -
Ori Idan