Kernel stucks at Starting kernel....statement

Hi!

As i read about this issue... i am using x-loader and u-boot loader provided by the distributor which were supposed to boot android... do i need to compile a different u-boot source code for this ..if yes please suggest the link to download the source code.

i have pasted my printenv variables of board

TAM3517 # printenv

bootdelay=1
baudrate=115200
console=ttyS0,115200n8
memsize=256M
mpurate=600
touch_calibration=
nandparts=omap2-nand.0:512k(xloader),1024k(uboot),512k(params),6m(kernel),-(rootfs)
disp_mode_0=set def_disp lcd;set disp_mode panel-generic.disp_timings=8000,480/8/4/41,272/4/2/10,24;set touch_calibration ads7846.calibration=8235,28,-981716,17,4906,-1103000,65536
disp_mode_1=set def_disp lcd;set disp_mode panel-generic.disp_timings=33300,800/210/46/1,480/22/23/1,24;set touch_calibration ads7846.calibration=-13943,25,54444704,-124,-9117,34403056,65536 ads7846.swap_left_right=1 ads7846.swap_top_down=1 ads7846.x_min=180 ads7846.y_min=330 ads7846.x_max=3900 ads7846.y_max=3800
disp_mode_2=set def_disp lcd;set disp_mode panel-generic.disp_timings=54200,1024/320/320/1,600/25/25/1,18
disp_mode_3=set def_disp dvi;set disp_mode omapfb.mode=dvi:1280x720@60
disp_mode_4=set def_disp tv;set disp_mode omapfb.mode=tv:ntsc
disp_mode_5=set def_disp tv;set disp_mode omapfb.mode=tv:pal
disp_mode_6=run disp_mode_0
disp_mode_7=run disp_mode_0
sys_mode_0=
sys_mode_1=set rootfs ubi0:android;set rootfsmmc 3;set nfsroot /nfsroot/android vers=3;set android_args androidboot.console=ttyS0
sys_mode_2=run sys_mode_0
sys_mode_3=run sys_mode_0
sys_mode_4=run sys_mode_0
sys_mode_5=run sys_mode_0
sys_mode_6=run sys_mode_0
sys_mode_7=run sys_mode_0
boot_to_0=run nandboot
boot_to_1=run mmcboot
boot_to_2=run nfsboot
boot_to_3=run boot_to_0
vram_size=10M
android_args=
rootfs=ubi0:rootfs
rootfsmtd=4
rootfsmmc=2
nfsroot=/nfsroot/angstrom vers=3
defaultargs=run nandargs
nfsargs=run def_sys_mode;run def_disp_mode;setenv bootargs mem=${memsize} mpurate=${mpurate} console=${console} omapfb.vram=0:${vram_size} eth0addr=${eth0addr} eth1addr=${eth1addr} eth2addr=${eth2addr} eth3addr=${eth3addr} ${android_args} ${sys_mode} ${board_info} ${auto_run} omapdss.def_disp=${def_disp} ${disp_mode} ${touch_calibration} mtdparts=${nandparts} root=/dev/nfs rw ip=${ipaddr}:::::${nfseth}: nfsroot=${serverip}:${nfsroot}
mmcargs=run def_sys_mode;run def_disp_mode;setenv bootargs mem=${memsize} mpurate=${mpurate} console=${console} omapfb.vram=0:${vram_size} eth0addr=${eth0addr} eth1addr=${eth1addr} eth2addr=${eth2addr} eth3addr=${eth3addr} ${android_args} ${sys_mode} ${board_info} ${auto_run} omapdss.def_disp=${def_disp} ${disp_mode} ${touch_calibration} mtdparts=${nandparts} root=/dev/mmcblk0p${rootfsmmc} rw rootfstype=ext3 rootwait
nandargs=run def_sys_mode;run def_disp_mode;setenv bootargs mem=${memsize} mpurate=${mpurate} console=${console} omapfb.vram=0:${vram_size} eth0addr=${eth0addr} eth1addr=${eth1addr} eth2addr=${eth2addr} eth3addr=${eth3addr} ${android_args} ${sys_mode} ${board_info} ${auto_run} omapdss.def_disp=${def_disp} ${disp_mode} ${touch_calibration} mtdparts=${nandparts} ubi.mtd=${rootfsmtd} root=${rootfs} rw rootfstype=ubifs rootflags=bulk_read,chk_data_crc rw
load_b=tftp 80100000 boot/u-boot-32-256-nand-16.bin
load_xb=tftp 80100000 boot/mlo-32-256-nand-16
kernel_addr=200000
kernel_load=81000000
kernel_size=600000
uboot_nand_addr=80000
update_xb=run load_xb;nandecc hw;nand erase 0 20000;nand write 80100000 0 20000
update_b=run load_b;nandecc sw;nand erase ${uboot_nand_addr} 40000;nand write 80100000 ${uboot_nand_addr} 100000
update_k=run load_k;nandecc sw;nand erase ${kernel_addr} ${kernel_size};nand write.jffs2 ${kernel_load} ${kernel_addr} ${kernel_size}
load_nand_k=nandecc sw;nand read.jffs2 ${kernel_load} ${kernel_addr} ${kernel_size}
nfsboot=run nfsargs;run load_k;bootm ${kernel_load}
mmcboot=mmc init;run loaduimage; run mmcargs; bootm ${kernel_load}
nandboot=run nandargs;run load_nand_k;bootm ${kernel_load}
dieid#=30e20000000000000155dc140400f016
netmask=255.255.255.0
ethact=DaVinci EMAC
serverip=192.168.1.233
bootcmd=tftpboot 80008000 uImage;bootm 80008000
ipaddr=192.168.1.54
bootargs=console=ttyS2,115200n8
stdin=serial
stdout=serial
stderr=serial
eth0addr=00:1F:7B:15:01:10
eth1addr=00:1F:7B:15:01:11
eth2addr=00:1F:7B:15:01:12
eth3addr=00:1F:7B:15:01:13
ethaddr=00:1f:7b:15:01:10
board_info=CUSTOMER=TechNexion PRODUCT=tam3517 ID=1052000000000069 BOARD_TN=15 BOARD_REVISION_MAJOR=1 BOARD_REVISION_FIXED=0
def_disp_mode=run disp_mode_1
def_boot_to=run boot_to_0
def_sys_mode=run sys_mode_1
load_k=tftp ${kernel_load} boot/1/uImage
loaduimage=fatload mmc 0 ${kernel_load} boot/1/uImage
bootfile=boot/1/uImage
sys_mode=SYSTEM=1
nfseth=eth1

Environment size: 4368/131068 bytes
TAM3517 #

I ran into the same problem when I re-compiled Linux kernel (2.6.37). When configuring the kernel through the config menu utility, I switched from the AM3517EV board type to Logic SOM 350 board. Re-compiling with initial board type selection let the kernel boot again.

Hope that helps,

Yves

Hi Hrishikesh

Please use "console"  as ttyO2.  I'm not sure about androidboot.console, but bootargs cosole should be ttyO2 for you to be able to see boot messages on the serial console for 2.6.37

Hope it helps.

regards

Abhilash

That's true, I forgot about that last step when I installed kernel 2.6.37 on my boot device and never got the 'login' prompt. I edited /etc/fstab to set the console to ttyO2 and I got the login prompt on next reboot.

BTW, any stabilitiy issues with 2.6.37. Odd kernel numbers are under development, right?

Thanks,

Yves

Thanks for your reply!!

I will let u know ..if this helps mee.

Thanks and regards

Hrishikesh.

 Hi...

 I am also facing same kind of problem.

When I compile the kernel image using 'make' command, the following error comes

ERROR: "mmc_io_rw_direct" [drivers/net/wireless/wilink/sdio.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2

However 'Image' and 'zImage' gets created in the arch/arm/boot  directory.

When I make the kernel uImage using mkimage utility, and port that on to the AM1808 EVM , it gets stuck at 

Starting Kernel...

Please enlighten ...