testing barebox on calao sbc35-a9260 board

[Sascha Hauer]

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 at 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

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.

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 |