Linux/TMDSLCDK138: TFTP boot problem

Patrick McCloskey

Part Number: TMDSLCDK138
Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Tool/software: Linux

I have been struggling to get my OMAP-L138 to boot the Linux SDK v5.3 over NFS using TFTP. Nothing I have tried has worked. Has anyone else been successful using TFTP with an OMAP-L138 LCDK?

I was able to load the pre-built binary files onto an SD card.

When I configure the SDK for bootup from the SD card, it works.

I can log in as root.

I can connect to the instance of matrix using a web browser.

I will attach four Libre Office documents with notes:

workstation_setup.odt
boot_sdk_from_sdcard.odt
boot_sdk_over_nfs-first_attempt-FAILED.odt
boot_sdk_over_nfs-second_attempt-FAILED.odt

I am not an expert in Linux.

I am not an expert in uboot.

I figure I am missing something that someone experienced with Linux and uboot will spot and set me straight.

Thanks in advance for any guidance.

workstation_setup.docx boot_sdk_from_sdcard.docx boot_sdk_over_nfs-first_attempt-FAILED.docx boot_sdk_over_nfs-second_attempt-FAILED.docx

over 5 years ago

0 Yordan Kovachev over 5 years ago

TI__Guru**** 161600 points

Hi,

Sorry, I haven't tried this. Did it work with the previous Processor SDK Linux?

Best Regards,
Yordan

0 Patrick McCloskey over 5 years ago in reply to Yordan Kovachev

Intellectual 955 points

Thanks for the response, Yordan.
In the past few days, I also tried 5.02 and 5.01. I could not get TFTP to work with them either.

0 Yordan Kovachev over 5 years ago in reply to Patrick McCloskey

TI__Guru**** 161600 points

Ok, let me check this.

Best Regards,
Yordan

0 Yordan Kovachev over 5 years ago in reply to Yordan Kovachev

TI__Guru**** 161600 points

Hi,

I think you set up your network environment as it should be set up. Take a look at Processor SDK Linux User Guide:
software-dl.ti.com/.../Foundational_Components_U-Boot.html
"U-Boot # setenv autoload no
U-Boot # dhcp
U-Boot # setenv serverip correct.server.ip
U-Boot # tftp

Another alternative is to utilize the full syntax of the tftp command:

U-Boot # setenv autoload no
U-Boot # dhcp
U-Boot # tftp ${loadaddr} server.ip:fileName"

Or the Ethernet boot section from the same user guide: software-dl.ti.com/.../Foundational_Components_U-Boot.html
for the manual network configuration.

Best Regards,
Yordan

0 Patrick McCloskey over 5 years ago in reply to Yordan Kovachev

Intellectual 955 points

I had experimented with the tftpboot command, as shown in previously attached file boot_sdk_over_nfs-second_attempt-FAILED.docx.

I tried the first command sequence you suggested.

U-Boot # setenv autoload no

U-Boot # dhcp

U-Boot # setenv serverip correct.server.ip

U-Boot # tftp

It found the image file but it did not boot.

Here is the session log.

boot_sdk_over_nfs-third_attempt-FAILED.docx

Next, I tried the second command sequence you suggested.

U-Boot # setenv autoload no
U-Boot # dhcp
U-Boot # tftp ${loadaddr} server.ip:fileName"

It found the image file but it did not boot.

Here is the session log.

boot_sdk_over_nfs-fourth_attempt-FAILED.docx

I will study the uboot material you referenced.

Thanks for the help.

0 Yordan Kovachev over 5 years ago in reply to Patrick McCloskey

TI__Guru**** 161600 points

Also check this older wiki for u-boot configurations:
processors.wiki.ti.com/.../MCSDK_OMAPL138_User_Guide_Chapter_Tools

Best Regards,
Yordan

0 Patrick McCloskey over 5 years ago in reply to Yordan Kovachev

Intellectual 955 points

Thanks for the additional link.
I have not gotten it to work yet. I will continue studying the reference material.
I am curious about the uboot command "go". If I am successfully loading the kernel into memory, I should be able to start it from the entry point.
The TI ARM compiler provides the entry point in an xml file (used to be a .map file).
Does gcc do that?
Is there a way I can determine the entry point for the program?

0 Patrick McCloskey over 5 years ago in reply to Patrick McCloskey

Intellectual 955 points

I got farther along in the process.

I connected my workstation and the LCDK into a different network router.

However, it does not boot the kernel.

boot_sdk_over_nfs-fifth_attempt-FAILED.docx

0 RonB over 5 years ago in reply to Patrick McCloskey

TI__Mastermind 30276 points

Patrick,

Could you please attach the output of the printenv command from U-Boot so I can see the environment you are trying to use and what it is trying to do?

Thank you.

0 Patrick McCloskey over 5 years ago in reply to RonB

Intellectual 955 points

Thanks for the response RonB.

I have not been able to get past "Starting kernel ..." with my tftpboot/nfs configuration.

Here are my latest notes, including the printenv output from u-boot.

boot_sdk_over_nfs-sixth_attempt-FAILED.docx

0 Krunal Bhargav34 over 5 years ago in reply to Patrick McCloskey

TI__Mastermind 33125 points

Hi Patrick,

Based on the logs, you do not have the variable netargs defined. Based on the setup, please try one of the following options:

Option-1: Define netargs as following: "netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcp"

Option-2: When you run the command "setenv bootcmd .....", please do not include the command "run netargs". Instead, define the following command: " setenv bootargs 'console=ttyS2,115200n8 root=/dev/nfs nfsroot=<type_your_ip>:<type_your_directory_path>,nolock rw earlyprintk ip=dhcp' "

Regards,
Krunal

0 Patrick McCloskey over 5 years ago in reply to Krunal Bhargav34

Intellectual 955 points

Hi Krunal:

Thank you for the suggestions.

I chose option 1 and it worked! I get the kernel to start.

Here are my session notes.

boot_sdk_over_nfs-seventh_attempt-SUCCESS.docx

boot_sdk_over_nfs-eighth_attempt-SUCCESS.docx

I do not find any place in the setup scripts in ti-processor-sdk-linux-omapl138-lcdk-05.03.00.07/bin/ where netargs gets set. Is it supposed to be set in there somewhere?

Can this be updated in a future SDK release, like 5.04?

0 Krunal Bhargav34 over 5 years ago in reply to Patrick McCloskey

TI__Mastermind 33125 points

Hello,

The u-boot environment variables vary based on the board and the release year. For example, netargs is defined in <u-boot>/include/configs/ti_armv7_common.h. AM57xx, AM43xx and AM335x are making references to ti_armv7_common.h but omapl138_lcdk.h is not.

Based on my discussion with our developers, option 2 is preferred because it is sets the basic uboot variable that is used across all platforms.

Regards,
Krunal

Processors

Processors forum

Linux/TMDSLCDK138: TFTP boot problem