OMAP-L138 LCDK Booting Issues

Ehsun

Other Parts Discussed in Thread: OMAP-L138

Hello all,

I just received an OMAP-L138 LCDK (http://www.ti.com/tool/tmdxlcdk138) and am trying to bring it up. I have been successful in some ways, and unsuccessful in others. I also have several questions pertaining to developing for this board.

Using the SD Card that the device shipped with, I am able to boot successfully into a linux prompt. I also followed instructions for the following SDK located here: http://software-dl.ti.com/dsps/dsps_public_sw/c6000/web/omapl138_lcdk_sdk/latest/index_FDS.html

Example of my success:

Welcome to minicom 2.4

OPTIONS: I18n
Compiled on Jan 25 2010, 06:49:09.
Port /dev/ttyUSB0

Press CTRL-A Z for help on special keys

NAND: 512 MiB
MMC: davinci: 0
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
In: serial
Out: serial
Err: serial
ARM Clock : 456000000 Hz
DDR Clock : 150000000 Hz
Net: Ethernet PHY: GENERIC @ 0x07
DaVinci-EMAC
Hit any key to stop autoboot: 0
U-Boot > printenv
autoload=no
baudrate=115200
bootargs=mem=32M console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait ip=off
bootcmd=mmc rescan 0;fatload mmc 0 0xc0700000 uImage; bootm c0700000;
bootdelay=4
bootfile=uImage-da850-omapl138-evm.bin
ethact=DaVinci-EMAC
ethaddr=00:00:a0:00:fb:c7
ipaddr=192.168.1.3
oldbootargs=mem=32M console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait ip=off
oldbootcmd=mmc rescan 0;fatload mmc 0 0xc0700000 uImage; bootm c0700000;
oldserverip=192.168.1.2
serverip=192.168.1.2
stderr=serial
stdin=serial
stdout=serial
ver=U-Boot 2010.12 (May 07 2012 - 16:09:45)

Environment size: 613/65532 bytes

U-Boot > boot
reading uImage

2040348 bytes read
## Booting kernel from Legacy Image at c0700000 ...
Image Name: Linux-3.1.10
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2040284 Bytes = 1.9 MiB
Load Address: c0008000
Entry Point: c0008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.1.10 (root@VPC-U1104) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #7 PREEMPT Fri May 11 2
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: AM18x/OMAP-L138 LCDK

...[and so on... eventually comes up with login]

However, I find a link that tells me to use the DVSDK:

http://processors.wiki.ti.com/index.php/Getting_Started_Guide_for_OMAP-L1,

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/latest/index_FDS.html

I follow those directions, boot over tftp, and my kernel suddenly does not boot at all.

Example of this failure:

U-Boot > printenv
autoload=no
baudrate=115200
bootargs=console=ttyS2,115200n8 noinitrd rw mem=32M@0xc0000000 mem=64M@0xc4000000 root=/dev/nfs nfsroot=192.168.1.2:/home/ehsun/targetfs,nolock ip=192.168.1.3
bootcmd=tftp;bootm
bootdelay=4
bootfile=uImage-da850-omapl138-evm.bin
ethact=DaVinci-EMAC
ethaddr=00:00:a0:00:fb:c7
ipaddr=192.168.1.3
oldbootargs=mem=32M console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait ip=off
oldbootcmd=mmc rescan 0;fatload mmc 0 0xc0700000 uImage; bootm c0700000;
oldserverip=192.168.1.2
serverip=192.168.1.2
stderr=serial
stdin=serial
stdout=serial
ver=U-Boot 2010.12 (May 07 2012 - 16:09:45)

Environment size: 642/65532 bytes
U-Boot > boot
Using DaVinci-EMAC device
TFTP from server 192.168.1.2; our IP address is 192.168.1.3
Filename 'uImage-da850-omapl138-evm.bin'.
Load address: 0xc0700000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###############################################################
done
Bytes transferred = 2315152 (235390 hex)
## Booting kernel from Legacy Image at c0700000 ...
Image Name: Arago/2.6.37-psp03.21.00.04.sdk/
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2315088 Bytes = 2.2 MiB
Load Address: c0008000
Entry Point: c0008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

[cursor keeps blinking....]

I have seen the following thread http://processors.wiki.ti.com/index.php/FAQ_for_DaVinci_Linux#No_kernel_output_after_U-Boot_load, and I have tried to modify the console to be "... console=uart,io,0xe1020000,115200n8 ...", but that did not change anything for me, no extra information. I would try to rebuild the kernel with the printascii function, but I don't know how to build a new kernel (any help in this area also appreciated, such links to tutorials on how to do this).

Is there any obvious reason why the DVSDK does not work for me?

over 13 years ago

0 Norman Wong over 13 years ago

Guru 26430 points

Maybe try ttyO2 ('O 'as in Omap) instead of ttyS2. Also try adding a earlyprintk to your bootargs. Your ip bootarg might need changing. If you have a dhcp server, it's easier to use ip=dhcp.

0 Ehsun over 13 years ago in reply to Norman Wong

Prodigy 180 points

I tried making it ttyO2 as well, that didn't work.

Where would I print earlyprintk in the bootargs? And what would that do for me?

Here is my current bootargs and bootcmd:

bootargs=console=ttyS2,115200n8 noinitrd rw mem=32M@0xc0000000 mem=64M@0xc4000000 root=/dev/nfs nfsroot=192.168.1.2:/home/ehsun/targetfs,nolock ip=192.168.1.3
bootcmd=tftp;bootm

How should I modify that to put in an earlyprintk?

As for the DHCP, why should that matter for booting the kernel? As far as I understand, the DHCP just makes things convenient. I have statically set the ip addr, and the image is retrieved successfully from the tftp server on the host.

For clarity, here are the env vars and boot result with the DVSDK image.

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

[...and hangs]

0 Loc Truong over 13 years ago in reply to Ehsun

TI__Intellectual 2620 points

The LCDK and LogicPD EVMs (both OMAP-L138 based) have different PHY IDs. So if you try to run uImage built for the other EVM it will hang at the EMAC init. Not sure why would you want to do this.

If you want to take advantage of the OMAP-L138 DVSDK (e.g. 4.03) file system on LCDK, you can just mount the filesystem once the LCDK root file system is mounted. You can use the DVSDK as root file system, you need to do a make install of the LCDK kernel build to it so that the Linux kernel v3.1.10 headers and lib modules are present on the file system...

0 Loc Truong over 13 years ago in reply to Loc Truong

TI__Intellectual 2620 points

Also forgot to add that the LCDK Getting Started Guide and Software Developers Guide are available on the processors.wiki.ti.com locations:

http://processors.wiki.ti.com/index.php/OMAP-L138_LCDK_Linux_SDK_Getting_Started_Guide

http://processors.wiki.ti.com/index.php/OMAP-L138_LCDK_Linux_Software_Developer%27s_Guide

0 Norman Wong over 13 years ago in reply to Ehsun

Guru 26430 points

The "ip" bootarg has a specific format. Last I looked, the parser for this string is not very robust. The long format is defined as:

ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>

I've seen the following used:

p=192.168.1.3:192.168.1.2::255.255.255.0:target_name:eth0:off
ip=192.168.1.3:::::eth0:off
ip=off
ip=dhcp

The earlyprintk is of the bootargs env var. Try this as a test

setenv bootargs console=ttyS2,115200n8 noinitrd rw mem=32M@0xc0000000 mem=64M@0xc4000000 root=/dev/nfs nfsroot=192.168.1.2:/home/ehsun/targetfs,nolock ip=192.168.1.3:192.168.1.2::255.255.255.0:target_name:eth0:off earlyprintk
bootm

0 Ehsun over 13 years ago in reply to Loc Truong

Prodigy 180 points

Loc said:

The LCDK and LogicPD EVMs (both OMAP-L138 based) have different PHY IDs. So if you try to run uImage built for the other EVM it will hang at the EMAC init. Not sure why would you want to do this.

If you want to take advantage of the OMAP-L138 DVSDK (e.g. 4.03) file system on LCDK, you can just mount the filesystem once the LCDK root file system is mounted. You can use the DVSDK as root file system, you need to do a make install of the LCDK kernel build to it so that the Linux kernel v3.1.10 headers and lib modules are present on the file system...

Okay, so I guess that's what I missed out on somehow. The DVSDK was not meant for the OMAP-L138 LCDK board. I'm not sure how but I had somehow ended up on the page for DVSDK.

Processors

Processors forum

OMAP-L138 LCDK Booting Issues