Skip to contentSkip to conversation

Hello world application running problem

U-Boot-Users Jhavk 3 participants 5 messages Oct 29, 2004 – Nov 1, 2004

lore
Share & tools
lore

Jhavk

author
#0 lore raw
Quoted 29 lines

I have read README.standalone. My target board is
smdk2440(Arm 9).

So i transfer hello_world using tftp to address 0x0c100000 and then call "go 0x0c100000 hello world"

But after that the application seems to get stuck
and
nothing happens. Eventually i have to reset the
board.

I have some doubts:
1. Which file should i send. I think it should be hello_world and not the srec or bin format. I ran file
command on all 3 and found that hello_world is the
one meant for ARM.

2.Is the load and start address correct? May be its different for ARM9?

If all these are correct then what may be the
problem?

Quoted 6 lines

__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile
phone.
http://mobile.yahoo.com/maildemo

__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail

#1 lore raw

Hi Jhavk,

Quoted 11 lines
Quoted 11 lines

I have read README.standalone. My target board is
smdk2440(Arm 9).

So i transfer hello_world using tftp to address 0x0c100000 and then call "go 0x0c100000 hello world"

But after that the application seems to get stuck
and
nothing happens. Eventually i have to reset the
board.

Quoted 6 lines
Quoted 6 lines

I have some doubts:
1. Which file should i send. I think it should be hello_world and not the srec or bin format. I ran file
command on all 3 and found that hello_world is the
one meant for ARM.

You should use the .bin file as tftp does not interpret ELF files so you need a binary image. file cannot tell anything about binary images because there is no magic in there anymore - its a plain memory dump.

Quoted 2 lines
Quoted 2 lines

2.Is the load and start address correct? May be its different for ARM9?

This is just a theoretical answer as I don't have an ARM board ready - but judging by the makefile it looks ok. Apart from that on PPC we have to skip the first 4 bytes because of reasons explained on this list not long ago (search mailing list - I don't have a good keyword ready) - so try a "go 0x0c100004". This is also explained in the DULG.

Quoted 2 lines
Quoted 2 lines

If all these are correct then what may be the
problem?

I saw at least two problems.

Cheers
Detlev

Signature · 2 lines
A statistician can have his head in an oven and his feet in ice, and
he will say that on the average he feels fine.
#2 lore raw
In reply to Jhavk
Quoted 6 lines · In message <[email protected]> you wrote:
Quoted 6 lines

I have read README.standalone. My target board is
smdk2440(Arm 9).

So i transfer hello_world using tftp to address 0x0c100000 and then call "go 0x0c100000 hello world"

What makes you think that 0x0c100000 is the entry point of the standalone application?

Quoted 4 lines
Quoted 4 lines

But after that the application seems to get stuck
and
nothing happens. Eventually i have to reset the
board.

This is because you tried to run code where none is. Pay attention to the entry point address.

Quoted 2 lines
Quoted 2 lines

I have some doubts:
1. Which file should i send. I think it should be

This depends on which tool or protocol you use for the download.

Quoted 1 line
Quoted 1 line

hello_world and not the srec or bin format. I ran

This is wrong. hello_world is an ELF file, so it may only be used by tools / protocols that understand ELF files. The SREC file has to be used by tools / protocols that understand Motorola S-Record files. The BIN file has to be used by tools / protocols that understand raw binary images.

Quoted 2 lines
Quoted 2 lines

command on all 3 and found that hello_world is the
one meant for ARM.

Wrong again. All images (hello_world, hello_world.srec,
hello_world.bin etc) are all teh same images, just in different format, depnding on which protocols or tools you want to use.

Quoted 2 lines
Quoted 2 lines

2.Is the load and start address correct? May be its different for ARM9?

The load address ooks ok to me. The entry point is probably somewhere else.

Best regards,

Wolfgang Denk

Signature · 3 lines
See us @ Embedded/Electronica Munich, Nov 09 - 12, Hall A.6 Booth 513
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Neckties strangle clear thinking.                       -- Lin Yutang
author
#3 lore raw

Thanks for all the valuable info.

Actually i went thru the doc/README.standalone file and theres a table which tell abt load and entry point address of various architecture.

For arm load = 0x0c100000
entry pt = 0x0c100000.

I still have 2 doubts( hope it doesnt annoys u) 1.Cant i tftp my hello_world.bin to any valid address of RAM eg "tftp 0x30000000 hello_world.bin"

2.How do i find out the entry point of my binary image?

Regards,
Jhavk

Quoted 61 lines · --- Wolfgang Denk

In message <[email protected]>

Quoted 2 lines · you
Quoted 2 lines

I have read README.standalone. My target board

is

Quoted 4 lines
Quoted 4 lines

smdk2440(Arm 9).

So i transfer hello_world using tftp to address
0x0c100000 and then call "go 0x0c100000 hello

world"

What makes you think that 0x0c100000 is the
entry point of the
standalone application?

Quoted 1 line
Quoted 1 line

But after that the application seems to get

stuck

Quoted 3 lines
Quoted 3 lines

and
nothing happens. Eventually i have to reset the
board.

This is because you tried to run code where none is. Pay attention to
the entry point address.

Quoted 2 lines
Quoted 2 lines

I have some doubts:
1. Which file should i send. I think it should

be

This depends on which tool or protocol you use for the download.

Quoted 1 line
Quoted 1 line

hello_world and not the srec or bin format. I

ran

This is wrong. hello_world is an ELF file, so it may only be used by
tools / protocols that understand ELF files. The SREC file has to be
used by tools / protocols that understand Motorola S-Record files.
The BIN file has to be used by tools / protocols that understand raw
binary images.

Quoted 1 line
Quoted 1 line

command on all 3 and found that hello_world is

the

Quoted 1 line
Quoted 1 line

one meant for ARM.

Wrong again. All images (hello_world,
hello_world.srec,
hello_world.bin etc) are all teh same images, just in different
format, depnding on which protocols or tools you want to use.

Quoted 1 line
Quoted 1 line

2.Is the load and start address correct? May be

its

Quoted 1 line
Quoted 1 line

different for ARM9?

Quoted 17 lines

The load address ooks ok to me. The entry point is probably somewhere
else.

Best regards,

Wolfgang Denk

Signature · 6 lines
See us @ Embedded/Electronica Munich, Nov 09 - 12,
Hall A.6 Booth 513
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80
Email: wd at denx.de
Neckties strangle clear thinking.                   
   -- Lin Yutang

__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail

#4 lore raw
Quoted 7 lines · In message <[email protected]> you wrote:

Actually i went thru the doc/README.standalone file and theres a table which tell abt load and entry point address of various architecture.

For arm load = 0x0c100000
entry pt = 0x0c100000.

You are right.

Quoted 3 lines

I still have 2 doubts( hope it doesnt annoys u) 1.Cant i tftp my hello_world.bin to any valid address of RAM eg "tftp 0x30000000 hello_world.bin"

You, you can do this (but the code will not run if downloaded to a different address).

Quoted 2 lines

2.How do i find out the entry point of my binary image?

	-> nm hello_world
	0c108228 A __bss_end__
	0c108228 A __bss_start
	0c108228 A __bss_start__
	0c108228 D __data_start
	0c108228 A __end__
	0c108228 A _bss_end__
	0c108228 A _edata
	0c108228 A _end
	0c100158 T app_startup
	0c10013c T do_reset
	0c1000c8 t dummy
	0c10011c T free
	0c10010c T free_hdlr
	0c10012c T get_timer
	0c1000d4 T get_version
	0c1000dc T getc
====>>	0c100000 T hello_world
	0c10014c T i2c_read
	0c100144 T i2c_write
	0c100104 T install_hdlr
	0c100114 T malloc
	0c1000fc T printf
	0c1000ec T putc
	0c1000f4 T puts
	0c1000e4 T tstc
	0c100124 T udelay
	0c100134 T vprintf

Best regards,

Wolfgang Denk

Signature · 3 lines
See us @ Embedded/Electronica Munich, Nov 09 - 12, Hall A.6 Booth 513
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Is the glass half empty, half full, or twice as large as it needs to