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: Tue, 8 Mar 2011 09:13:10 +0100 [thread overview]
Message-ID: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B011E5@SRV-VS06.TELEVIC.COM> (raw)
In-Reply-To: <20110308054006.GA22012@jasper.tkos.co.il>
Thank you Baruch ! Good starting point for my test app.
> -----Original Message-----
> From: Baruch Siach [mailto:baruch@tkos.co.il]
> Sent: dinsdag 8 maart 2011 6:40
> To: Vanalme Filip
> Cc: barebox@lists.infradead.org
> Subject: Re: test app
>
> Hi Vanalme,
>
> On Mon, Mar 07, 2011 at 02:05:32PM +0100, Vanalme Filip wrote:
> > We would like to have a kind of small test application, that can be
> > started from the barebox prompt, to do some basic tests on some hardware
> components.
> > What's the best way to do that ? E.g. can I add that test application
> > to the environment and would this be good practice ? Or do I better
> > extend the barebox commands with my own command to start the tests ?
> > Maybe there's an example on how to do it ?
>
> I'm using the attached program to do a simple RAM read/write test on i.MX25.
> This program runs on bare hardware from the internal chip SRAM, and doesn't rely
> on the Barebox run-time code. I only use Barebox to start this program.
>
> The program is built with the following Makefile rules:
>
> all: ramtest.bin
>
> %.bin: %.elf
> ${OBJCOPY} -O binary $^ $@
>
> ramtest.elf: ramtest.c
> ${CC} -Wall -Os -nostdlib $^ -o $@ -Wl,-Ttext=0x78000000
>
> Running this program from the Barebox prompt:
>
> cp ramtest.bin /dev/sram0
> go /dev/sram0
>
> I hope this helps.
>
> baruch
>
> --
> ~. .~ 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
next prev parent reply other threads:[~2011-03-08 8:50 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 [this message]
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
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=6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B011E5@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