[U-Boot] U-boot -printk kernel crash dump using md on PDK

[Magnus Lilja]

Hi

2009/4/27 alfred steele <alfred.jaquez at gmail.com>:
> Dear Magnus,
>
> Thanks for the reply!
>> And we need to know which U-boot patches you're using to boot the PDK
>> board.
> I am using the internal git tree code supplied to me by freescale. The
> tarball is called "uboot-imx-imx_v2009.01.tar.gz". I can boot uboot
> out of NAND successfully using that as the code base.  I had  started
> using this even before Magnus had posted the patches and i had to
> write a patch for the MMC/SD driver on top of that . To add to that ,
> i tried downloading the mainline using GIT but it seems the corporate
> firewall/proxy we have  blocks  it. Due to the shortage of time, i
> continued to use the Freescale supplied code. It would be great if you
> can supply me the code in a tarball(mainline git) with the patches you
> posted if you want me to try it out.

There's a 'snapshot' function in git-web
(http://git.denx.de/?p=u-boot.git;a=tree) which will produce a tarball
of the current tree.

My patches are in the mailing list archives so you should be able to
download and apply them as well.

>
>>In your original post you use the "go" command to boot the
>> kernel,
> I use the "bootm" command now. My sole intention of using go was to
> check whether or not zImage( instead of uImage) boots up as a generic
> application. I tried verify  the bootags in  the U-boot environment. I
> chacked on the machine id which gets registered with the kernel. They
> all seemed to be the expected values.
>
> Coming back to I am not sure about ,was when i tried dumping the
> address(0x80000100) which supposedly stores the bootargs, i get the
> following :
> => md 0x80000100
> 80000100: c0000100 c0000100 c0000108 c0000108    ................
> 80000110: c0000110 c0000110 c0000118 c0000118    ................
> 80000120: 92492492 24924924 00000149 736e6f63    .$I.$I.$I...cons
> 80000130: 3d656c6f 6d797474 2c306378 32353131    ole=ttymxc0,1152
> 80000140: c0000140 c0000140 c0000148 c0000148    @... at ...H...H...
>
> It looks like the console is not set correctly to 115200, assuming its
> in ASCII. Any clues as to what could be gone wrong?

No idea.

Your printk dump from the first mail seems to indicate that the kernel
was able to boot, but for some reason it doesn't print on the serial
port. And I can't see any init of the serial port in that log either.
Seems like a problem with your kernel or its configuration.

/Magnus