From: Belisko Marek <marek.belisko@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: testing barebox on calao sbc35-a9260 board
Date: Wed, 30 Jun 2010 13:39:51 +0200 [thread overview]
Message-ID: <AANLkTimNUQvQohAOv2pyKsPXWgDg12AnIyrJr5A52js5@mail.gmail.com> (raw)
In-Reply-To: <20100630065757.GO12115@pengutronix.de>
On Wed, Jun 30, 2010 at 8:57 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Mon, Jun 28, 2010 at 12:37:06PM +0200, Belisko Marek wrote:
>> Hi,
>>
>> On Mon, Jun 28, 2010 at 11:36 AM, Juergen Beisert <jbe@pengutronix.de> wrote:
>> > Eric Bénard wrote:
>> >> Hi Marek,
>> >>
>> >> Le 28/06/2010 11:08, Belisko Marek a écrit :
>> >> > I disable autostart and download barebox image to 0x8000 with
>> >> > tftp 0x8000 barebox.bin and then jut go 0x8000 ended with:
>> >> > ## Starting application at 0x00008000 ...
>> >>
>> >> if I remember well, on AT91 SDRAM is at 0x20000000 so actually you don't
>> >> seem to load it in SDRAM.
>> >> For the binary to execute properly, you should load it at the right
>> >> target address in SDRAM.
>> >
>> > If barebox detects its current runtime address differs from the link address
>> > it copies itself to the link address first.
>> >
>> > So writing it anywhere into sdram should work. But only, if also the link
>> > address is in the sdram area...
>> Seems it's not working in my case. U-boot code just jump to address which
>> is taken as argument according code. If barebox is copied to correct link
>> address and started it should work. Is there any possibility to check
>> link address from binary
>> or it's not necessary to use mkimage tool from u-boot?
>
> Here are the necessary steps to run the barebox.bin file from U-Boot:
>
> tftp 0x20000000 barebox.bin
> go 0x20000000
Following steps give me the also only Starting application at
0x20000000 and nothing more.
>
> As Eric stated the 9260 has SDRAM at 0x20000000, so this would be an
> appropriate load address. barebox then relocates itself to 0x23f00000
> according to the link address which you can check by doing 'make
> barebox.S' and looking at barebox.S.
Yes it seems link address ( 0x23f00000) is correct according barebox.S file.
Strange.
Anyway thanks for support and advices.
>
> Sascha
>
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer
Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-06-30 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 9:31 Belisko Marek
2010-06-28 8:04 ` Sascha Hauer
2010-06-28 8:32 ` Baruch Siach
2010-06-30 7:02 ` Sascha Hauer
2010-06-28 9:08 ` Belisko Marek
2010-06-28 9:17 ` Eric Bénard
2010-06-28 9:36 ` Juergen Beisert
2010-06-28 10:37 ` Belisko Marek
2010-06-30 6:57 ` Sascha Hauer
2010-06-30 11:39 ` Belisko Marek [this message]
2010-06-30 7:03 ` 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=AANLkTimNUQvQohAOv2pyKsPXWgDg12AnIyrJr5A52js5@mail.gmail.com \
--to=marek.belisko@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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