From: Vanalme Filip <F.Vanalme@TELEVIC.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: test app
Date: Mon, 14 Mar 2011 15:55:29 +0100 [thread overview]
Message-ID: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B01573@SRV-VS06.TELEVIC.COM> (raw)
In-Reply-To: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B012BB@SRV-VS06.TELEVIC.COM>
Hi,
Would I have to change a lot if I would like to use standard libraries (e.g. stdio for printf and sprint) in my test app ?
Filip
> -----Original Message-----
> From: barebox-bounces@lists.infradead.org [mailto:barebox-
> bounces@lists.infradead.org] On Behalf Of Vanalme Filip
> Sent: woensdag 9 maart 2011 9:29
> To: Baruch Siach
> Cc: barebox@lists.infradead.org
> Subject: RE: test app
>
> > -----Original Message-----
> > From: Baruch Siach [mailto:baruch@tkos.co.il]
> > Sent: dinsdag 8 maart 2011 19:09
> > To: Vanalme Filip
> > Cc: barebox@lists.infradead.org
> > Subject: Re: test app
> >
> > Hi Vanalme,
> >
> > On Tue, Mar 08, 2011 at 04:52:49PM +0100, Vanalme Filip wrote:
> > > Compiling and linking seems to work well now. When I dump the .elf, I see
> > > that the start address is 0xA7E00000. That's what I wanted.
> > > However, when loading the app in ram and executing it, I see that it tries to
> start
> > from 0xA0000000 (this is the base address of the RAM section) :
> > >
> > > barebox:/test tftp testapp.bin
> > > TFTP from server 10.0.48.80 ('testapp.bin' -> 'testapp.bin')
> > >
> > > barebox:/test cp testapp.bin /dev/ram0
> > > barebox:/test go /dev/ram0
> > > ## Starting application at 0xA0000000 ...
> > > ?¶/ÿ'.e¢Óøñ_
> > >
> > > _øýàõÒÿ ïO
> > > ÿOÿðzþðöàþ A'}®ÿ
> > > ùý"õÿ?O¿PP¼@Y
> > > }¸m
> > > ×´ï@ïðx`G-/
> > >
> > >
> > > Should I specify an address when executing 'go' or 'cp' ? Isn't it loading the
> app
> > always at the beginning of the RAM space, i.e. 0xA0000000 ?
> >
> > Is 0xA0000000 the beginning of you external RAM?
>
>
> [Filip] yes.
> I meanwhile adjusted Makefile and test app source code to start from address
> 0xA0000000. This seem to work well. My test app is running now.
> Because it's just a test app, I think it's OK to put it at the beginning of the external
> RAM (so at address 0xA0000000). No use in trying to move it to another region in
> the external RAM, is it ?
>
> >
> > Note that in my example I used /dev/sram0 (on-chip 128K SRAM), not /dev/ram0
> > (external DDR2 RAM).
> >
> > baruch
> >
>
> [Filip] If I'm right (have to verify though), i.MX27 does not have any SRAM on
> board. So, I guess external RAM will be the only option. Because the test app
> resides in the external RAM, it won't be possible to test the whole RAM. But I think
> we can live with that limitation.
>
> Thanks !
>
> Filip
> > --
> > ~. .~ Tk Open Systems
> > =}------------------------------------------------ooO--U--Ooo------------{=
> > - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-03-14 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 13:05 Vanalme Filip
2011-03-08 5:40 ` Baruch Siach
2011-03-08 8:13 ` Vanalme Filip
2011-03-08 10:09 ` Vanalme Filip
2011-03-08 11:22 ` Baruch Siach
2011-03-08 15:52 ` Vanalme Filip
2011-03-08 18:08 ` Baruch Siach
2011-03-09 8:28 ` Vanalme Filip
2011-03-14 14:55 ` Vanalme Filip [this message]
2011-03-14 17:31 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-14 18:03 ` Baruch Siach
2011-03-15 11:03 ` Vanalme Filip
2011-03-15 11:47 ` Zoltán Kócsi
2011-03-08 11:43 ` Sascha Hauer
2011-03-08 12:43 ` Vanalme Filip
2011-03-08 11:50 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B01573@SRV-VS06.TELEVIC.COM \
--to=f.vanalme@televic.com \
--cc=barebox@lists.infradead.org \
--cc=baruch@tkos.co.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox