AT91SAM9263ek with OE a la linux4sam (SOLVED)

limpens · **Joined:** Sun Sep 02, 2007 1:39 pm **Posts:** 77

Quote:

Hi,

I've followed the steps from linux4sam.org to build a 'angstrom-minimalist-image'.
The build steps are completed succesfully and I've now got a root filesystem and a Kernel.

However, searching the forum and re-reading the linux4sam site, it doesn't become quite clear, where to upload what file.

The supplied CD has a several files which are uploaded using the tcl script and SAM-BA. Is it expected behaviour, to change the tcl script with the appropriate names and use this to upload the files?

In that case, I'm still a bit confused, as the CD has a .bin file for the dataflash, U-Boot, a Linux kernel and a jffs2 filesystem.
After my build process, I've only got a jffs2 filesystem and a 'uImage*bin' file.

Anyone got some pointers (besides the obvious 'google is your friend') ?

TIA. Eric

Jan 2008:

I've started from scratch and followed the steps on Linux4Sam. Don't know
for sure, but it might have something to do with my version of Bitbake (I WAS using 1.8.8 ).

When someone is interested, I've documented the steps.

When I build the 2.6.22 kernel (standalone build, using the compilers from OE), everything works (alsa/video/touchscreen), but I do think it is slower (using mplayer to show the building..avi file) than the demo image from the linux4sam site. Anyone who can confirm this?

When using 2.6.23, there is a problem with Alsa, with make menuconfig it doesn't show up (after applying the 2.6.22 patch) and isn't available when using the kernel. Or should I apply the 2.6.22-exp patch also?

limpens · **Joined:** Sun Sep 02, 2007 1:39 pm **Posts:** 77

limpens wrote:

I've followed the steps from linux4sam.org to build a 'angstrom-minimalist-image'.
The build steps are completed succesfully and I've now got a root filesystem and a Kernel.

So, although replying to my own post is stupid, some progress:

I've used the (by OE) generated crosscompilers to compile the dataflash bootstrap
and u-boot (with appropriate patches).

Changed the .bat and .tcl files, to use the proper names and flashed the board with the newly compiled code.

U-Boot boots the kernel, but the kernel panics on an 'cannot open root device 'mtdblock0'..

Should the 'bitbake angstrom-minimal-image' produce working code, with the local.conf from linux4sam?

Thanks, Eric

limpens · **Joined:** Sun Sep 02, 2007 1:39 pm **Posts:** 77

Using the supplied batchfile / tcl script, I do get things running with the 'original' Angstrom kernel and my own rebuild filesystem, uboot and flash bootstrap.

It appears that the supplied local.conf for OE doesn't produce a kernel like the original one.

Do I need to configure the kernel properly before running bitbake?

aron · **Joined:** Fri Sep 28, 2007 1:07 pm **Posts:** 29

I've been messing around with buildroot and OE now for a while and I've found it to be easier to do the kernel on the side, following the instructions on the linux4sam site.

limpens · **Joined:** Sun Sep 02, 2007 1:39 pm **Posts:** 77

aron wrote:

I've been messing around with buildroot and OE now for a while and I've found it to be easier to do the kernel on the side, following the instructions on the linux4sam site.

The kernel is the one thing, I succeed in building over and over. I'll give the 'kernel outside the other buildroot' a go.

My current problem is building every X based image. I can rebuild the angstrom-minimal-image, but the angstrom-x11-image-demo image fails (as does something like xfce.

It looks like a version problem with gcc (gcc 4.1.2 too old).

aron · **Joined:** Fri Sep 28, 2007 1:07 pm **Posts:** 29

That's my experience too. It seems it's alot of work getting an x11-ish image working.
My latest track is to put together som arm binaries debian provides.

limpens · **Joined:** Sun Sep 02, 2007 1:39 pm **Posts:** 77

aron wrote:

That's my experience too. It seems it's alot of work getting an x11-ish image working.
My latest track is to put together som arm binaries debian provides.

And that's too bad. Reading the build section on Linux4Sam.org, I thought this would be a nice start.

However, only the 'anstrom-minimal-image' gets build cleanly.

I'm now trying to build a X image using the compilers from CodeSourcery but the documentation op OpenEmbedded.org aren't very helpful.

aron · **Joined:** Fri Sep 28, 2007 1:07 pm **Posts:** 29

Also, I'm thinking in terms of mouting the angstrom x11 image on a ramdisk and extracting the contents to a chroot and put whatever I need in there and create anew image from the resulting rootfs. Think that would be a feasible way to go about it?

limpens · **Joined:** Sun Sep 02, 2007 1:39 pm **Posts:** 77

aron wrote:

Also, I'm thinking in terms of mouting the angstrom x11 image on a ramdisk and extracting the contents to a chroot and put whatever I need in there and create anew image from the resulting rootfs. Think that would be a feasible way to go about it?

Mount it on your build host or on your arm hardware? mounting the X11 image on your build host can be done using a loopback device. But, afaik, the rootfs is also build as a tar ball.

I prefer to have a repository with all the sources and scripts which everyone can (re)use to reproduce an exact image.

Adding and removing applications etc would just mean to run make on the sources.

aron · **Joined:** Fri Sep 28, 2007 1:07 pm **Posts:** 29

Mount it on the host, modify it and then put onto the hardware.
No I think you can''t loopbackmount the jffs2 image because it's not a block device. Create an mtddevice like you create a ramdisk and the mount it would be what I was thinking about.
The "run make on the sources" part is what keeps blocking my way forward due to compilation errors on just about anything I try other than the minimal image. If this wasn't the case I too would prefer a repository which could be used to create images from ofcourse.
I have to check out the tarball you're mentioning.

limpens · **Joined:** Sun Sep 02, 2007 1:39 pm **Posts:** 77

aron wrote:

Mount it on the host, modify it and then put onto the hardware.
No I think you can''t loopbackmount the jffs2 image because it's not a block device. Create an mtddevice like you create a ramdisk and the mount it would be what I was thinking about.

I wasn't aware of that (yet), but it appears jffs2 can be mounted locally with some tricks

aron wrote:

The "run make on the sources" part is what keeps blocking my way forward due to compilation errors on just about anything I try other than the minimal image. If this wasn't the case I too would prefer a repository which could be used to create images from ofcourse.
I have to check out the tarball you're mentioning.

I've given the 'buildroot' variant a go, but I can't even get that to produce a complete working kernel/filesystem.. sigh..

aron · **Joined:** Fri Sep 28, 2007 1:07 pm **Posts:** 29

PERFECT limpens! Exactly what I was looking for. Thanks!

With buildroot I managed to create the minimum rootfs and bash on top (just to try something more), but anything above that was all trouble =/

I found some interesting precompiled stuff here:
http://www.debian.org/ports/arm/

limpens · **Joined:** Sun Sep 02, 2007 1:39 pm **Posts:** 77

aron wrote:

PERFECT limpens! Exactly what I was looking for. Thanks!

With buildroot I managed to create the minimum rootfs and bash on top (just to try something more), but anything above that was all trouble =/

I found some interesting precompiled stuff here:
http://www.debian.org/ports/arm/

I'm using the arm compilers from CodeSourcery and the pointers from linux4sam to build the kernel. Building the rootfs will probably be done using buildroot.

fly232323 · **Joined:** Tue Jan 22, 2008 11:48 pm **Posts:** 3

Greetings,

I am currently working on building a minimal Angstrom release containing kernel, root FS and X11 only. My goal is to have the device boot and load my custom X11 application immediately after the kernel boots. Can anyone point in the right direction to edit the Angstrom boot scripts? Also, I assume I will be creating a .bb package once my application is done, which should be easy to include it with distribution.

Thanks in advance,
Brandon[/i]

fly232323 · **Joined:** Tue Jan 22, 2008 11:48 pm **Posts:** 3

Greetings,

I am currently working on building a minimal Angstrom release containing kernel, root FS and X11 only. My goal is to have the device boot and load my custom X11 application immediately after the kernel boots. Can anyone point in the right direction to edit the Angstrom boot scripts? Also, I assume I will be creating a .bb package once my application is done, which should be easy to include it with distribution.

Thanks in advance,
Brandon[/i]

AT91SAM9263ek with OE a la linux4sam (SOLVED)

Who is online