No console after Linux uncompress on the Mistral OMAP3530 EVM

Can you please first double check if "console=ttyS0" in bootargs, not "ttyS2"?

Hi Bin,

Thank you for your reply.

Yes my console was already set to ttyS0. This is my current environement setup:

OMAP3_EVM # print
baudrate=115200
bootfile="uImage"
get_kernel=run nand_kernel
get_initrd=run nand_initrd
tftp_kernel=tftpboot 0x80000000 uImage
tftp_initrd=tftpboot 0x81600000 ramdisk.gz
addip=setenv bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:on
boot_rd=run get_kernel; run get_initrd; setenv bootargs $(bootargs_rd); run addip; bootm 0x80000000
boot_fs=run get_kernel; setenv bootargs $(bootargs_fs); bootm 0x80000000
ethaddr=00:50:c2:7E:90:1F
netmask=255.255.255.0
serverip=192.168.0.1
filesize=207904
bootcmd=run boot_fs
ipaddr=192.168.0.5
dieid#=35a8002400000000040365fa15013021
ethact=smc911x-0
nand_initrd=nand read.i 0x82000000 780000 2000000
bootargs_rd=mem=128M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x82000000,40M ramdisk_size=32768
nand_kernel=nand read.i 0x80000000 280000 500000
bootdelay=6
nfshost=192.168.0.6
bootargs_fs=mem=99M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 mpurate=720 omapfb.rotate=1 omapfb.vrfb=y vram=10M omapfb.vram=0:10M omap_vout.vid1_static_vrfb_alloc=y
bootargs=mem=99M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=192.168.0.6:/home/danielc/workdir/filesys,nolock mpurate=720 omapfb.rotate=1 omapfb.vrfb=y vram=10M omapfb.vram=0:10M omap_vout.vid1_static_vrfb_alloc=y ip=192.168.0.5:192.168.0.1::255.255.255.0::eth0:on
boot_nfs=run get_kernel; setenv bootargs $(bootargs_nfs); run addip; bootm 0x80000000
bootargs_nfs=mem=99M@0x80000000 mem=128M@0x88000000 console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=192.168.0.6:/home/danielc/workdir/filesys,nolock mpurate=720 omapfb.rotate=1 omapfb.vrfb=y vram=10M omapfb.vram=0:10M omap_vout.vid1_static_vrfb_alloc=y
stdin=serial
stdout=serial
stderr=serial

Environment size: 2046/131068 bytes
OMAP3_EVM #

If I replace the newest uBoot my my older one I am able to run kernel and applications from NFS by the following command:

OMAP3_EVM # run boot_nfs

However, the older uBoot have less functionality and it doesn't set the ARM clock  to 720 Mhz. Maybe it is other things that doesn't work with the older uBoot. This is why I would like get the newer working. There is something else wrong in my environment setup?

Daniel

I tried your bootargs_nfs, it works for me. I dont know what could be wrong. Let's see if anyone else can help on this.

Hi Bin,

This is the traces I got about the uBoot version and when I lunch the kernel. The LCD flashing and stay black after that, the application never popup. My uBoot size is 212,992 bytes recompiled with Sourcery arm-2009q1. Can you see something wrong on the following if you compare with your? The EVM board you are using is it rev G?

OMAP3_EVM # version

U-Boot 2009.11-svn479 (Jul 13 2010 - 10:30:04)

OMAP3_EVM # run boot_nfs

NAND read: device 0 offset 0x280000, size 0x500000
5242880 bytes read: OK
## Booting kernel from Legacy Image at 80000000 ...
Image Name: Linux-2.6.32
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2393404 Bytes = 2.3 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux....................................................................................................................................................... done, booting the kernel.

Daniel

Daniel Chasse said:

U-Boot 2009.11-svn479 (Jul 13 2010 - 10:30:04)

'-svn479' is strange, I dont have this suffix. Can you please change back to the original u-boot image from the PSP package, and post the log from power on until you stop uboot to load uImage?

Did you re-build the uImage? the original one is 2393484 bytes, but yours is 2393404.

Yes, I use rev G omap3530.

Hi Bin,

Yes I recompiled all packages because I tested unsuccessful the prebuild packages coming with AM35x-OMAP35x-PSP-SDK-03.00.01.06.tgz.

Now I re-flahed again the prebuild images for giving you this log. Yes the prebuild uImage is now (2,393,484 bytes):

Texas Instruments X-Loader 1.46 (May 6 2010 - 23:45:50)
Starting OS Bootloader...


U-Boot 2009.11 (May 06 2010 - 23:47:47)

OMAP3430/3530-GP ES3.1, CPU-OPP2 L3-165MHz
OMAP3 EVM board + LPDDR/NAND
I2C: ready
DRAM: 128 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Read back SMSC id 0x92200000
Die ID #35a8002400000000040365fa15013021
Net: smc911x-0
Hit any key to stop autoboot: 0
OMAP3_EVM #
OMAP3_EVM #
OMAP3_EVM #
OMAP3_EVM # run boot_nfs

NAND read: device 0 offset 0x280000, size 0x500000
5242880 bytes read: OK
## Booting kernel from Legacy Image at 80000000 ...
Image Name: Linux-2.6.32
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2393420 Bytes = 2.3 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux....................................................................................................................................................... done, booting the kernel.

Also SW1 = 00000000, SW4 = 01010000 and J8 = UART1. I don't know if other setting on the board can be the cause of this bug?

Daniel

I have the same problem.

I have trouble booting the kernel v 2.6.32 from the omap sdk (AM35x-OMAP35x-PSP-SDK-03.00.01.06 ).
 The kernel booting process is stuck after uncompressing the kernel. 
The board used is OMAP3530EVM-REV-G.

I have tried the following steps to get the board up, but the booting
end result is the same.

1) I copied the readymade images of xloader, uboot, uImage and ramdisk
from the omap3530 PSP 03.00.01.06 release into a formatted  mmc card
(formated using the hpdiskformatter tool as required).

2) Now the board was set to boot in mmc card boot mode. It booted till
uboot prompt.

3) Then kernel was loaded from uboot using the following cmds
OMAP3_EVM # mmcinit
OMAP3_EVM # fatload mmc 0 0x80000000  uImage
OMAP3_EVM # fatload mmc 0 0x81600000 ramdisk.gz
OMAP3_EVM # setenv bootargs_rd mem=128M console=ttyS0,115200n8
root=/dev/ram0 initrd=0x81600000,40M ramdisk_size=40960
OMAP3_EVM # setenv bootargs $(bootargs_rd)
OMAP3_EVM # bootm 0x80000000

## Booting kernel from Legacy Image at 80000000 ...
   Image Name:   Linux-2.6.32
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2393360 Bytes =  2.3 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing
Linux..........................................................................................................................................
............. done, booting the kernel.

(kernel is stuck here)


So, I tried the same process using the ready made images from an older
PSPv02.01.03.11 and it booted fine (with kernel 2.6.29). So I persume
there is no problem with the board hardware.

Also I tried to build the uboot and kernel from the OMAP3-PSPv03.00.01.06,
and used the uboot.bin and uImage (rest of the things like xloader and
ramdisk from the omap3530SDKv03.00.01.06 itself).The result is simalar like in the boot seq above.

Today, I tried loading the kerenl uboot using the prebuilt images from OMAP3530_PSP_03.00.00.03.
 The result is similar. It is Linux-2.6.32-rc5 kernel.

Meanwhile, I am going to try with the old uboot (the one with 2.6.29 kernel)  with the new 2.6.32 kernels.
 I will tell the result after testing. 


Regards,
Ajit Vincent

These kind of probs are caused by incorrect bootparams.