EmbeddedRelated.com
Forums
Memfault Beyond the Launch

Newbie Qs: Buildroot and AT91SAM9261-EK

Started by Dan Lyke November 14, 2008
Two questions:

1. Where's a simple step-by-step document on installing the binaries
I've built with Buildroot on to a AT91SAM9261-EK (or
AT91SAM9(RL|XE)-EK, but the first is the target I really want)? I've
tried using the Angstrom demo loader, just replacing the binary names
in the TCL script, but that's apparently not it.

2. I've checked the "EABI" box on the compile, is that the problem?

Thanks.

Dan

On Fri, 14 Nov 2008 05:30:05 -0800
Dan Lyke wrote:
> 1. Where's a simple step-by-step document on installing the binaries
> I've built with Buildroot on to a AT91SAM9261-EK

Okay, perhaps an easier question, since I've now got my kernel loading
(although not mounting the root filesystem) with the boostrap and uBoot
from the demo Angstrom distribution, is: where are the load locations
for the default buildroot images documented?

Thanks!

Dan

locations for boot from dataflash
dataflashboot(bootstrap) 0x0
uboot 0x8400
older version of bootstrap expects uboot at 0x8000
it is defined somewhere in bootstrap source codes !
kernel image 0x40000
on startup uboot needs to copy kernel from dataflash into the ram and bootm from that position
for example 22200000
set the bootcmd env var in uboot to do these steps on startup automatically.
nand flash divided in partitions. each partitionin has an address and you can see them when kernel is booting. in tcl script you can see bootargs env var which uboot passes it to kernel. mtdblock0 means that file system image stored in partition 0 or address 0 in nandflash.because of small size of partition0 i simply used partition1.

if there was problem with nandflash check this out
http://www.at91.com/samphpbb/viewtopic.php?f&tI47&hilit+instead+8+no+nand+device+found+at91
--- On Fri, 11/14/08, Dan Lyke wrote:
From: Dan Lyke
Subject: [AT91SAM] Newbie Qs: Buildroot and AT91SAM9261-EK
To: A...
Date: Friday, November 14, 2008, 5:00 PM

Two questions:

1. Where's a simple step-by-step document on installing the binaries

I've built with Buildroot on to a AT91SAM9261- EK (or

AT91SAM9(RL| XE)-EK, but the first is the target I really want)? I've

tried using the Angstrom demo loader, just replacing the binary names

in the TCL script, but that's apparently not it.

2. I've checked the "EABI" box on the compile, is that the problem?

Thanks.

Dan
--- In A..., sajjad t wrote:
>You can refer the linux4sam.org.
In this you can see the tool SAM-BA, this is the utility can be used for flashing the image.
I have a question.
Does the image build by compiling the buildroot(present in buildroot/binaries/AT91)consists of the kernel image also along with the root file system?

Thanks, Regards
Mahendra.K

> locations for boot from dataflash
> dataflashboot(bootstrap) 0x0
> uboot 0x8400
> older version of bootstrap expects uboot at 0x8000
> it is defined somewhere in bootstrap source codes !
> kernel image 0x40000
> on startup uboot needs to copy kernel from dataflash into the ram and bootm from that position
> for example 22200000
> set the bootcmd env var in uboot to do these steps on startup automatically.
> nand flash divided in partitions. each partitionin has an address and you can see them when kernel is booting. in tcl script you can see bootargs env var which uboot passes it to kernel. mtdblock0 means that file system image stored in partition 0 or address 0 in nandflash.because of small size of partition0 i simply used partition1.
>
> if there was problem with nandflash check this out
> http://www.at91.com/samphpbb/viewtopic.php?f=12&t=4947&hilit=16+instead+8+no+nand+device+found+at91
>
>
> --- On Fri, 11/14/08, Dan Lyke wrote:
> From: Dan Lyke
> Subject: [AT91SAM] Newbie Qs: Buildroot and AT91SAM9261-EK
> To: A...
> Date: Friday, November 14, 2008, 5:00 PM
>
>
>
>
>
>
>
>
>
>
>
>
>
> Two questions:
>
>
>
> 1. Where's a simple step-by-step document on installing the binaries
>
> I've built with Buildroot on to a AT91SAM9261- EK (or
>
> AT91SAM9(RL| XE)-EK, but the first is the target I really want)? I've
>
> tried using the Angstrom demo loader, just replacing the binary names
>
> in the TCL script, but that's apparently not it.
>
>
>
> 2. I've checked the "EABI" box on the compile, is that the problem?
>
>
>
> Thanks.
>
>
>
> Dan
>

On Fri, 10 Jul 2009 09:09:22 -0000
"mahendra_413" wrote:
> I have a question.
> Does the image build by compiling the buildroot(present in
> buildroot/binaries/AT91)consists of the kernel image also along with
> the root file system?

The kernel image is a separate file from the root file system image.

Dan
Maybe a tip for anyone that might use buildroot the way I did :

I've been using buildroot to *only* generate the rootfs. It's running on an
Olimex SAM9-L9260.
I use the existing (Dataflash) Kernel generated by uClinux (I also tried
with the original Olimex supplied Kernel).

Now, the documentation states about the option to generate soft float code
:
"Most people don't use this".
Well, as I found out - you DO need it !
I spent 2 days trying to figure out why the initscript (inittab->rcS)
wouldn't work properly, or why the password
didn't work either. (once the root FS is on the Nand flash).
Turned out you HAVE to use soft float - your image file will have the
_nofpu suffix.
With the softfloat turned on everything works perfect.
(The regular menuconfig to build the kernel does point out there that you
need ONE of the float options)

Oh, another tip : Don't forget to replace the 'x' in the passwd file
(/etc/passwd) with either a "blank" (no password login) or your desired
password for every user that will login. I made that mistake. There was
nothing in the documentation about that ........
(I'm using V 2009.05).
example : root:x:.... etc => root::.... etc OR
root:mypassword:.....

I don't know if the soft float is a requirement when you use Buildroot's
kernel/bootstrap/U-boot tool + the root FS

Did you have this problem too Dan ?

Have fun !

On Fri, 10 Jul 2009 16:17:36 -0700, Dan Lyke wrote:
> On Fri, 10 Jul 2009 09:09:22 -0000
> "mahendra_413" wrote:
>> I have a question.
>> Does the image build by compiling the buildroot(present in
>> buildroot/binaries/AT91)consists of the kernel image also along with
>> the root file system?
>
> The kernel image is a separate file from the root file system image.
>
> Dan
>
On Sat, 11 Jul 2009 17:52:49 +1000
m...@virginbroadband.com.au wrote:
> I don't know if the soft float is a requirement when you use
> Buildroot's kernel/bootstrap/U-boot tool + the root FS

That one hasn't bitten me (or I figured it out fast and without pain),
but I did have some pain when trying to make EABI work, I went back to
OABI. Traffic on the Buildroot mailing list indicates EABI might work
now, but I'm not terribly excited about trying again.

Dan

Memfault Beyond the Launch