OMAP 3530 use the kernel 2.6.37 for Android 2.3 can't boot

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Download the source code with parameter "rowboat-gingerbread.xml"
2.Compile the Android Filesystem & Kernel with parameter 
"TARGET_PRODUCT=omap3evm"

What is the expected output? What do you see instead?
The omap 3530 evm board version G system should boot into Android system.
But the system stop in "Uncompressing Linux... done, booting the kernel."

What version of the product are you using? On what operating system?

Please provide any additional information below.
If I change the kernel to 2.6.32, the omap 3530 evm board can boot into Android 
2.3 

Original issue reported on code.google.com by sting...@gmail.com on 22 Jun 2011 at 2:09

[GoogleCodeExporter]

Are you able to see the android homescreen on lcd?
kernel 2.6.37 is newly added and may not be fully stable yet.
iirc in 2.6.37 the console names have been changed to ttyOx from ttySx. You 
would need to modify your bootargs accordingly.

Original comment by vishvesh...@aim.com on 22 Jun 2011 at 8:53

[GoogleCodeExporter]

I ever changed the console names to ttyOx(not 0x/zero x) from ttySx.   
But the system still hang on "Uncompressing Linux... done, booting the 
kernel.". 
I can't see any data after "Uncompressing Linux... done, booting the kernel." 
from console. Do you have any idea about it ? 

Original comment by sting...@gmail.com on 23 Jun 2011 at 1:24

[GoogleCodeExporter]

The following bootargs works for me with 2.6.37:

setenv bootargs 'init=/init console=ttyO0,115200n8 noinitrd 
androidboot.console=ttyO0 rootwait mem=256M omap_vout.vid1_static_vrfb_alloc=y 
vram=8M omapfb.vram=0:8M root=/dev/mmcblk0p2 rw rootfstype=ext3 ip=off'

Original comment by vishvesh...@aim.com on 23 Jun 2011 at 5:54

[GoogleCodeExporter]

At first, thank your help. I solve this bug. But I found the other bug. After 
booting,
the system show "Kernel panic - not syncing: No init found." and system hang on.
Please see the attach file 062308.txt . About it, do you have any idea about it 
?   

Original comment by sting...@gmail.com on 23 Jun 2011 at 9:40

Attachments:

• 062308.TXT

[GoogleCodeExporter]

The kernel tries to run /sbin/init, /etc/init, /bin/init, /bin/sh in this order 
from the mountet root filesystem. So you have to check if you selected the 
right rootfs. If the fs is healthy. And if your Binaries are executeable.

Original comment by oliver.metz on 30 Aug 2011 at 8:10