compiling linux-2.6.37 for Devkit8000 | Kernel gets hung at "Starting kernel..."

GoogleGroups
1

Hi,

I am builiding kernel 2.6.37 for devkit 8000. I got the kernel src
from following location
git clone git://gitorious.org/devkit8000/linux-omap-devkit8000.git

I configured and created uImage. But I boot the kernel it get hung at
Starting Kernel ...

Here is the log.

## Booting kernel from Legacy Image at 80300000 ...
   Image Name: Linux-2.6.37-rc3-g3153f68
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 2353760 Bytes = 2.2 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

I am using following version of uBoot
U-Boot 2010.03

I compiled Uboot and linux src using ARM cross compiler version =
(Sourcery G++ Lite 2009q1-203) 4.3.3

Here is my uboot printenv
bootdelay=3
baudrate=115200
ethaddr=aa:bb:cc:dd:ee:ff
bootfile="uImage"
bootcmd=tftp 80300000 /tftpboot/uImage
bootm=80300000
filesize=207570
fileaddr=80300000
gatewayip=192.168.1.1
netmask=255.255.255.0
ipaddr=192.168.1.4
serverip=192.168.1.2
bootargs=console=ttyS2,115200n8 noinitrd root=/dev/nfs rw
nfsroot=192.168.1.2:/target
ip=192.168.1.4:192.168.1.2:192.168.1.1:255.255.255.0:localhost.localdom
ain:eth0::off init=/init
arcNumber=2554
stdin=serial
stdout=serial
stderr=serial
dieid#=2a40000400000000040364320e01500b
ethact=dm9000

Please help me if I am missing any steps or configuration.

Regards,
-Alok

2

This has been covered quite a bit lately in this forum, you should try
searching.. :wink:

with 2.6.37+ use ttyO2 (O in omap) vs ttS2

Regards,

3

Hi Robert,

Thank you very much. changing ttyS2 to ttyO2 solved my problem.

I am facing similar problem on Zoom2 board. there I have Android
kernel 2.6.32. I tried u-boot memory dump (md) to read the pritk
buffer data.I can see contents of __log_buf. It looks like kernel is
booting.

Could you please give me some pointers on that? I have also tried main
line linux 2.6.32 with zoom2 defconfig, and I was able to read the
debug messages but if I download android kernel 2.6.32, it gets hung
at starting kernel... ...
I tried various android sources. Tried to debug kernel using
printascii and md but could not see the kernel debug messages.

any help is highly appreciated.

Regards,
-Alok

4

I am having the same issue with my kernel build for beagle-xm. Did you
fix your problem?

5

You need to set console=ttyO2,115200 with newer (2.6.35+) kernels

6

I'm facing same problem. Try to run 2.6.38 on my devkit board but
when u-boot load it to ram I see just:

## Booting kernel from Legacy Image at 80300000 ...
   Image Name: Linux-2.6.38-06570-g79c21b4
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 2967164 Bytes = 2.8 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

I have changed bootargs to: bootargs=console=ttyO2,115200n8 doesn't
help.

Any ideas?

7

I had a similar problem. I fixed it by copying the u-boot.bin file
that was created when I compiled the kernel.

--Mark

8

Well.... I was wrong. The new u-boot is pulling the kernel from /boot/
uImage on the 2nd partition rather than uImage on the FAT partition.

I'm still stuck too.

--Mark

9

Hi Alok,
I am trying a similar task, will the source from http://gitorious.org/devkit8000/linux-omap-devkit8000.git run on embest devkit8000 as it is? or do we need to do some devkit specific changes to the kernel before loading it. In that case where can I get those changes?
The link doesn’t seem to work…any idea?

Thanks
Nitin

10

Hi Everybody,

I am also running into some troubles with 2.6.38 kernel

Basically I cloned the git repos for u-boot and linux_devkit8000, than, in a straigthforward fashon I cross compiled them both usign the gcc toolchain that comes with an openembedded build using the standard kernel devki8000_defconfig.

U-boot works fine, console needs to changed to ttySO2 but my kernel stops at some point, most often afer the alsa.

Moreover the 7" LCD seems not to be working at all despite u-boot bootargs

omapdss.def_disp=lcd omapfb.mode=lcd:800x480

mmmm

Fabio