evmk2h u-boot standalone application

xpt G

I have a EVMK2H rev 4.0 and I am trying to load a "hello wolrd" application through U-boot.

I did:

1) set ipaddr and serverip variables
2) created bin file using objcopy

3) transfer via tftp

4) run it using "go <address>"

It hangs on the message "starting application at <address>"

my questions:
- want is a valid address (or range of addresses) for this board ? I've tryed multiple among 0x80008000, 0x88000000 without result

- should I be using "bootcmd" instead of "go" ?

- do I need to set or modify any environment variable?

Regards

over 7 years ago

0 Yordan Kovachev over 7 years ago

TI__Guru**** 161600 points

Hi,

Which SDK version do you use?

Best Regards,
Yordan

0 xpt G over 7 years ago in reply to Yordan Kovachev

Prodigy 120 points

Hi,

By default, U-boot (version 2013-01-0004-...) is loading the images that come from mcsdk 3.01.
But I interrupt the loading process to gain access to the u-boot console. In this case, does the sdk version matter? why?

0 Titusrathinaraj Stalin over 7 years ago

TI__Guru** 116100 points

Please refer to this link.
www.denx.de/.../UBootStandalone
Try to build u-boot with standalone examples with "CONFIG_STANDALONE_LOAD_ADDR" (0x80000000") defined.

0 xpt G over 7 years ago in reply to Titusrathinaraj Stalin

Prodigy 120 points

Hi,

I have built as you suggested but the result is exactly the same: it hangs afetr the "go 0x80000000" command, with the message "starting application ate <address>".

0 Titusrathinaraj Stalin over 7 years ago in reply to xpt G

TI__Guru** 116100 points

I am also trying to run the example and got some undefined instruction error and data abort...
Working with DEV team, will let you know once I got something...

0 Rex Chang over 7 years ago in reply to Titusrathinaraj Stalin

TI__Guru 50170 points

Please read the document in u-boot/doc/README.standalone. The default load address for ARM is 0x0c100000. Try to use the .srec file first which will give you the following info after download:

## Ready for S-Record download ...

## First Load Addr = 0x0C100000
## Last Load Addr = 0x0C10020D
## Total Size = 0x0000020E = 526 Bytes
## Start Addr = 0x0C100001

The start address is 0x0c100001 as indicated.

Rex

0 xpt G over 7 years ago in reply to Rex Chang

Prodigy 120 points

Thanks Rex!
It works with the .srec file.

I am still wondering why doesn't it work with the .bin. Any idea?

0 Rex Chang over 7 years ago in reply to xpt G

TI__Guru 50170 points

It was working in MCSDK releases, but .bin fails in ProcSDK. We are looking into it.

0 xpt G over 7 years ago in reply to xpt G

Prodigy 120 points

Hi,
Just to let you know that it's working all fine now: using multiple addresses, transferring via tftp and over serial, compiled with different u-boot versions.
you just need to use the load address +1 for the go command

0 Rex Chang over 7 years ago in reply to xpt G

TI__Guru 50170 points

Could you elaborate more? which u-boot version are you using to get it working? ProcSDK or MCSDK and which version? In ProcSDK 3.0.0.4, the .bin file downloaded using tftp, even the load address +1, 0x0c100001, it does not work. However, in MCSDK release, I don't see any issue at all.

I appreciate if you can give more details.

0 xpt G over 7 years ago in reply to Rex Chang

Prodigy 120 points

Hi,

the u-boot version on the board is 2013-01-0004-(...) but it also works using a newer version from the git repository (release 2015- (...)) and compiling from source.
Keep in mind that I am loading a standalone application (hello world example) not u-boot itself.

Regards

0 Rex Chang over 7 years ago in reply to xpt G

TI__Guru 50170 points

Both of your u-boot versions are from MCSDK, not ProcSDK. TI has moved away from MCSDK to ProcSDK and the 2015 release is at least 3 versions older than the current ProcSDK release. U-boot had made changes between MCSDK and ProcSDK. Even though it is standalone application, but it matters. At least we are clear that the issue exists in ProcSDK. Thanks for the info.

0 Rex Chang over 7 years ago in reply to Rex Chang

TI__Guru 50170 points

Retest ProcSDK and realized that I was downloading .bin file from MCSDK which causes error. Using the .bin file build from ProcSDK, it works.

Processors

Processors forum

evmk2h u-boot standalone application