Uncompressing linux...done, booting the kernel...

Alexey Protsenko

Prodigy 110 points

Hello.

OMAP35x Zoom Development kit.

The subject is the last that system show.

It happens after i changed u-boot from version 1.1.4 to u-boot-2009.08-rc2.

Linux kernel changed to.

What may be the reason?

over 15 years ago

0 Bernie Thompson TI over 15 years ago

TI__Mastermind 41665 points

Usually when the last thing you see is 'Uncompressing Linux... done, booting the kernel...' it means you have something bad in your boot arguments, in particular I have seen this a lot when there is a typo on the console=ttyS0,115200n8 portion of the bootargs environment variable in U-Boot, such as if you have a lower case s instead of a capital S. If this value is not right, the kernel may still be booting underneath, but since you don't have the console directed to the ttyS0 UART interface you cannot see it booting.

The other alternative would be if your kernel image is corrupted or not built for your particular platform, though in these cases you often get other various error messages.

0 Steve Kipisz over 15 years ago

TI__Genius 15510 points

Can you build your kernel with low-level debugging? From make menuconfig select Kernel Hacking and scroll down and select Kernel low-level debugging functions and select Early printk. This might help.

Steve K.

0 Alexey Protsenko over 15 years ago in reply to Bernie Thompson TI

Prodigy 110 points

Thanks for your help.

In new version u-boot environment variable bootargs wos undefined, so it wos the reason.

The problem is solved.

0 Anu Kannan over 15 years ago in reply to Alexey Protsenko

Prodigy 10 points

Alexey,

Could you please share the bootargs that worked for you ? I am facing the same issue after updating to kernel 2.6.35

Version 2.6.32 worked alright.

Thanks

0 Alexey Protsenko over 14 years ago in reply to Anu Kannan

Prodigy 110 points

Hello, Anu

My current bootargs is

bootargs=display=15 console=ttyS0,115200 root=/dev/ram ramdisk_size=65536

argument "console=ttyS0,115200" must be in bootargs to work with debug terminal

0 Randy Seedle over 14 years ago in reply to Alexey Protsenko

Prodigy 20 points

I seem to have the same issue with linux booting and then hanging. I have added the early_printk to the kernel .config with no results. The interesting item is that I can go backwards to a previous linux kernel (2.6.28.10) with no problems. Very recently though the serial port terminal seems to be having issues with squiggly character though. Somethings not right.

Randy Seedle

Applied Rigaku

Here is my u-boot environment:

U-Boot # printenv
ethact=smc911x-0
distro=poky
project=poky-image-sato
ethaddr=ac:de:48:00:02:54
netmask=255.255.255.0
videomode=312
dieid=20aa00040000000004036abc0801a010
dieid#=20aa00040000000004036abc0801a010
ipaddr=192.168.50.217
machine=igep0020b
serverip=192.168.50.216
gatewayip=192.168.50.1
addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::eth0:
onenand-bootargs=setenv bootargs ${bootargs-base} root=/dev/mtdblock4 rootfstype=jffs2 ; run addip
onenand-boot=run onenand-bootargs; onenand read 0x80000000 0x280000 0x300000 ; bootm 0x80000000
nfs-bootargs=setenv bootargs ${bootargs-base} root=/dev/nfs nfsroot=${serverip}:/srv/nfs/${distro}/${project}/${machine} ; run addip
bootcmd=run mmc-boot; run nfs-boot; run onenand-boot
nfs-boot=if ping ${serverip}; then run nfs-bootargs; tftp 0x80000000 ${distro}/${project}/${machine}/uImage; bootm; fi;
bootargs-base=mem 512M console=tty2 omapfb.mode=dvi:800x480MR-24@60
bootargs=console=ttyS0, 115200n8 earlyprintk
stdin=serial
stdout=serial
stderr=serial

0 Miguel A. Salas N. over 13 years ago in reply to Bernie Thompson TI

Prodigy 10 points

In my case, the solution when using my board was to load the last version of the loader: Loader 2.3.0-2 (Feb 7 2012 - 12:26:40). After that, I have no more problems.

Processors

Processors forum

Uncompressing linux...done, booting the kernel...