* [U-Boot-Users] Problems with Hello_world example
@ 2004-02-17 16:51 Sonia Martinez Baro
2004-02-17 17:53 ` Stephan Linz
2004-02-17 21:03 ` Wolfgang Denk
0 siblings, 2 replies; 3+ messages in thread
From: Sonia Martinez Baro @ 2004-02-17 16:51 UTC (permalink / raw)
To: u-boot
Hi all,
we're using u-boot in a DBPXA250 based platform. We've burnt u-boot in Flash
memory and successed to communicate with it using hyperterminal or minicom.
Then we've loaded hello_world.bin in 0x00040004 and typed in u-boot's
prompt:
go 40004 Hello world
The result is:
## Starting application at 0x00040004 ...
03 3 3 ## Application terminated, rc = 0x0
(Note that "3 ## Application terminated, rc = 0x0" is printed when we hit
any key).
My doubts are:
When this example is compiled, we are using the binary file that is created
but, is this binary file created for our platform or does this example only
work with some specific architectures?? Should it work correctly in our
DBPXA250 bassed platform??
The u-boot's messages say that stdin, stdout and stderr are in the serial
port (because we aren't initializating the LCD). The hello_world example
program is printing messages using the printf() function and we suppose that
when we compile for our system, the printf() function is trying to print
those messages through the stdout of our system (that in this case is the
serial port, isn't it??). So why can't we see the messages that is printing
the Hello_world application thought serial line??? Why are we only seeing
those numbers (03 3 3)??? It can't be a baudrate problem, can it??
Thanks in advance for your help,
Sonia
_________________________________________________________________
?Est?s pensando en cambiar de coche? Todas los modelos de serie y extras en
MSN Motor. http://motor.msn.es/researchcentre/
^ permalink raw reply [flat|nested] 3+ messages in thread
* [U-Boot-Users] Problems with Hello_world example
2004-02-17 16:51 [U-Boot-Users] Problems with Hello_world example Sonia Martinez Baro
@ 2004-02-17 17:53 ` Stephan Linz
2004-02-17 21:03 ` Wolfgang Denk
1 sibling, 0 replies; 3+ messages in thread
From: Stephan Linz @ 2004-02-17 17:53 UTC (permalink / raw)
To: u-boot
Am Dienstag, 17. Februar 2004 17:51 schrieben Sie:
> Hi all,
>
> we're using u-boot in a DBPXA250 based platform. We've burnt u-boot in
> Flash memory and successed to communicate with it using hyperterminal or
> minicom. Then we've loaded hello_world.bin in 0x00040004 and typed in
Hi,
hellow_world can't run @ 0x00040004 correct -- have a look into
examples/Makefile. For ARCH=arm and that's the case for DBPXA250 based boards
there is a LOAD_ADDR=0xc100000. So the hello_world example will linked to
0xc100000 (not 0x00040004).
You should adapt LOAD_ADDR to your board specific environment or load and
start hello_world.bin to the given address.
Best Regards,
Stephan Linz
^ permalink raw reply [flat|nested] 3+ messages in thread
* [U-Boot-Users] Problems with Hello_world example
2004-02-17 16:51 [U-Boot-Users] Problems with Hello_world example Sonia Martinez Baro
2004-02-17 17:53 ` Stephan Linz
@ 2004-02-17 21:03 ` Wolfgang Denk
1 sibling, 0 replies; 3+ messages in thread
From: Wolfgang Denk @ 2004-02-17 21:03 UTC (permalink / raw)
To: u-boot
In message <LAW12-F23kjho31VINg0005f0dc@hotmail.com> you wrote:
>
> we're using u-boot in a DBPXA250 based platform. We've burnt u-boot in Flash
> memory and successed to communicate with it using hyperterminal or minicom.
> Then we've loaded hello_world.bin in 0x00040004 and typed in u-boot's
> prompt:
> go 40004 Hello world
This is wrong. Load at 0x00040000 and start at 0x00040004.
> When this example is compiled, we are using the binary file that is created
> but, is this binary file created for our platform or does this example only
> work with some specific architectures?? Should it work correctly in our
> DBPXA250 bassed platform??
It should work on all platforms. I never tested it on DBPXA250, though.
> The u-boot's messages say that stdin, stdout and stderr are in the serial
> port (because we aren't initializating the LCD). The hello_world example
> program is printing messages using the printf() function and we suppose that
> when we compile for our system, the printf() function is trying to print
> those messages through the stdout of our system (that in this case is the
> serial port, isn't it??). So why can't we see the messages that is printing
> the Hello_world application thought serial line??? Why are we only seeing
> those numbers (03 3 3)??? It can't be a baudrate problem, can it??
This is most probably a usage error. See above.
Best regards,
Wolfgang Denk
--
See us @ Embedded World, Nuremberg, Feb 17 - 19, Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
The only person who always got his work done by Friday
was Robinson Crusoe.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-02-17 21:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-17 16:51 [U-Boot-Users] Problems with Hello_world example Sonia Martinez Baro
2004-02-17 17:53 ` Stephan Linz
2004-02-17 21:03 ` Wolfgang Denk
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.