Reference on how to config buildroot for ext Atmel toolset.

Go To Last Post
9 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What options do I need to change in buildroot configuration for it to use my toolset that is already installed and working perfectly? I know the obvious ones, but I also need to specify libraries and such?

I think I saw a guide on how to do this a while ago, any pointer would be helpful... :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just change toolchain type to "External Toolchain" and you should be right. I don't really know what you mean regarding libraries though: uClibc is a part of the toolchain and won't be built if you use an external toolchain. You don't need to tell buildroot where it is, if your toolchain works it's because the compiler _knows_ where the standard libraries are.

Other support libraries (eg zlib, libpng etc) are not part of the toolchain and will be built by buildroot. The paths to these will be passed to the compiler by buildroot for you.

-S.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well for example in the buildroot menuconfig if I set it to external toolchain, it references the C library as libc.so.6, should that not be uclibc? Do I also need to specify a suffix and compiler build architecture (default uclibc-linux or something like that, my toolset is avr32-linux-...)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I would really recommend to build the toolchain shipped in Buildroot, as this is usually is more updated than the one available on atmel.com.

It also has the nice feature that both Buildroot and the target root filesystem are in sync :)

Hans-Christian

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well in sync is my goal, but I tried building gcc 4.2.2 and it just won't build (some problem in the source tree, an instruction unrecognized by the assembler...)... So I downloaded and installed the Atmel toolchain in RPM form (I'm on Fedora...), setup AVR32 Studio, my toolchain is working perfect as it is now with gcc 4.2.2, binutils 2.17, etc...

It would be nice to have a configure script to locate the toolchain and setup these things automagically before configuring buildroot...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You should let Buildroot build the toolchain, if you do it by hand there is often easy to miss a step and get something wrong.

FWIW there is an atmel-2.2 branch in Buildroot for AVR32 GIT which might be worth trying out.

Using the Buildroot built toolchain is just a matter of setting buildroot/build_avr32/staging_dir/bin first in your path.

Hans-Christian

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

My toolchain is already built, I installed from the binaries distributed on atmel.com, intended to go along AVR32 Studio 2.0. It has both the native and the linux toolchains, and the packages are more recent than the Atmel buildroot. I tried building Voltz' fork, but it doesnt like me. My toolchain is working and tested, I just need some documentation as to what the hell is needed in the buildroot config in terms of libraries to include, which path it asks for, etc..

I understand that using buildroot's toolchain is the easiest way, but then it will break my dev environment, I will need to mess around AVR32studio to make both the native and linux different version toolchains work, etc... I really would like to compile buildroot using my already installed, working, tested and ready to go toolchain, but it seems I am the first one to try this, unfortunately, because I cannot find any docs about this on the net... Even the upstream buildroot docu only mentions the external toolchain in a couple of sentences, no details about configuring buildroot to use it properly.. I am stuck pressing '?' in an ncurses app and trying to figure out cryptic sentences like "Comma-separated list of other libraries to copy.". WHICH libraries does the AVR32 port of buildroot need?

Am I alone in my weird world to want to use a pre-built toolchain instead of using buildroot's one?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Usually the toolchain in Buildroot has more fixes than the toolchain on atmel.com, this is due to more releases (intended at least) with the Buildroot for AVR32.

You can clone the GIT repository and fetch the atmel-2.2 branch.

GIT repository is available at git://www.atmel.no/~hcegtvedt/buildroo...

I have not tested the new toolchain release as an external toolchain, seems to be a fun exercise :)

Hans-Christian

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well I will give you some news, I am attempting it right now... Hehe.. I figured I would just include all the damn libraries and let buildroot strip them...

Packages are downloading as we speak.. I am trying John Voltz' r379 first, if it botches down ill flip to the Atmel release and try it again...