This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Lost console and LCD after upgrading the OMAP35x-PSP-SDK-03.00.00.06 packages (x-loader, u-boot.bin, kernel)

Hi,

I am using the OMAP353x EVM board Rev G from Mistral with 256Mb Micron Nand chip. The package already installed coming with the board was OMAP35x-PSP-SDK-02.01.03.11. I followed the procedure for upgrading the x-loader, u-boot.bin and kernel by TFTP but after upgrading the kernel it uncompress and I lost the console, LCD as well the serial port like you can see below on the trace. However, if I plug the usb otg cable the PC react proving that kernel is running.


Texas Instruments X-Loader 1.46 (Jun 28 2010 - 17:47:19)
Starting OS Bootloader...


U-Boot 2009.11-svn479 (Jun 28 2010 - 15:01:37)

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

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-svn475
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2393408 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.

 

I suspect my bootargs are incorrect.

 


OMAP3_EVM # pri
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
bootargs_nfs=mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=/mnt/nfs,nolock
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
boot_nfs=run get_kernel; setenv bootargs $(bootargs_nfs); run addip; 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
bootdelay=6
bootargs_fs=mem=99M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y
ipaddr=192.168.0.5
dieid#=35a8002400000000040365fa15013021
ethact=smc911x-0
bootargs=$(bootargs_fs)
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
stdin=serial
stdout=serial
stderr=serial

Environment size: 1260/131068 bytes
OMAP3_EVM #

 

There is something wrong with my environment settings?

Thank you,

Daniel

 

 

  • If I replace the u-boot.bin for the older one coming with the  OMAP35x-PSP-SDK-02.01.03.11, the serial port is reestablished but the LCD still not working.

    Maybe the new u-boot coming with package OMAP35x-PSP-SDK-03.00.01.06 required a different setting  for supporting the OMAP35x EVM Mistral Board than just doing the following step?

    $ make distclean

    $ make  omap3_evm_config

    $ make

    Someone has ideas what I can check to get the last OMAP35x-PSP-SDK-03.00.01.06 working on the OMAP35x EVM Board rev G  from Mistral?

    Daniel

  • i got the same problem sometimes when i change the kernel code.

    sometimes i just add lines like printk, then i got the same problem

    it's very odd.

    regards, Mike