[HOWTO] Install AVR32 GNU Toolchain on Ubuntu 10.4

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

Hi all, I guess some of you keep up with Ubuntu releases a bit faster than new packages for the AVR32 GNU toolchain is available. The main issue is libboost dependencies, but they can be worked around. The following packages are needed to install avr32-gnu-toolchain libboost-date-time1.34.1 libboost-filesystem1.34.1 libboost-filesystem1.38.0 libboost-system1.38.0 libboost-thread1.34.1 libboost-thread1.38.0 Which means you need to download the packages manually and install them with dpkg. For 32-bit installations grab: http://no.archive.ubuntu.com/ubu... http://no.archive.ubuntu.com/ubu... http://no.archive.ubuntu.com/ubu... http://no.archive.ubuntu.com/ubu... http://no.archive.ubuntu.com/ubu... http://no.archive.ubuntu.com/ubu... For 64-bit installations grab: http://no.archive.ubuntu.com/ubu... http://no.archive.ubuntu.com/ubu... http://no.archive.ubuntu.com/ubu... http://no.archive.ubuntu.com/ubu... http://no.archive.ubuntu.com/ubu... http://no.archive.ubuntu.com/ubu... Place the files downloaded above in some common folder and install them by executing dpkg directly

sudo dpkg --install libboost*

Afterwards you can install the avr32-gnu-toolchain package in the normal way (apt-get, aptitude, synaptics). Just remember to add the following line in /etc/apt/sources.list

deb http://distribute.atmel.no/tools/avr32/release/ubuntu/ karmic main

Happy hacking with AVR32 :twisted:

Hans-Christian

Last Edited: Sat. Oct 11, 2014 - 11:39 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank You! :)
I had this problem on my Debian Squeeze.

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

Perfect, I just wanted to ask why my installation failed.

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

I seem to be having similar problems with Fedora. I am currently running FC13 and trying to install the various 2.4.2 toolchain RPMs. I've got some of them installed, but it appears that the rest are not finding the boost and xerces libraries.

All of the errors I am getting involve shared object dependencies. For example:

$ sudo yum install libavrtools-4.1.0-1.fc12.i686.rpm 
Loaded plugins: presto, refresh-packagekit
Setting up Install Process
Examining libavrtools-4.1.0-1.fc12.i686.rpm: libavrtools-4.1.0-1.fc12.i686
Marking libavrtools-4.1.0-1.fc12.i686.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package libavrtools.i686 0:4.1.0-1.fc12 set to be installed
--> Processing Dependency: libboost_filesystem-mt.so.5 for package: libavrtools-4.1.0-1.fc12.i686
--> Processing Dependency: libboost_thread-mt.so.5 for package: libavrtools-4.1.0-1.fc12.i686
--> Processing Dependency: libxerces-c.so.28 for package: libavrtools-4.1.0-1.fc12.i686
--> Finished Dependency Resolution
Error: Package: libavrtools-4.1.0-1.fc12.i686 (/libavrtools-4.1.0-1.fc12.i686)
           Requires: libxerces-c.so.28
Error: Package: libavrtools-4.1.0-1.fc12.i686 (/libavrtools-4.1.0-1.fc12.i686)
           Requires: libboost_filesystem-mt.so.5
Error: Package: libavrtools-4.1.0-1.fc12.i686 (/libavrtools-4.1.0-1.fc12.i686)
           Requires: libboost_thread-mt.so.5
 You could try using --skip-broken to work around the problem

Is it impossible to install the FC12 files on my newer version?

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

An option is to download AVR32 Studio v2.6 or v2.7, since it contains a static compiled toolchain.

Hans-Christian

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

The links are broken.

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

Commanderbob wrote:
The links are broken.
You don't need to do it the hard way anymore either. Just use the GNU toolchain for Linux available at http://www.atmel.com/dyn/product...

Hans-Christian

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

hce wrote:
Commanderbob wrote:
The links are broken.
You don't need to do it the hard way anymore either. Just use the GNU toolchain for Linux available at http://www.atmel.com/dyn/product...

Where do I install that toolchain?

The avr32 package was great, it was easy to install and it just worked.

The reason I have to install the toolchain is because I'm installing AVR32Studio 2.5 because AVR32 studio 2.6 doesn't work due to:

a) the "extension not found" error.

b) whenever I clicked on the serial terminal it crashed and AVR32Studio closed

UPDATE:
The toolchain appears to be incomplete, the following binaries are missing:

avr32program, avr32gdbproxy, avrfwupgrade

I can't copy these over from my previous install because of the missing boost libraries.

what a mess ...

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

Hi
Iàve writte a tutorial about diffferent ways of installing the latest GNU toolchain, including compiling it from source, which is sure to work everywhere. There are also the magic runes for hoisting the missing programs out of the old distro.

http://code.google.com/p/mizar32...

Yes, Atmel's Linux distro support is a barely functional crock. They should employ me :)

M

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

martinwguy wrote:
Hi
Iàve writte a tutorial about diffferent ways of installing the latest GNU toolchain, including compiling it from source, which is sure to work everywhere. There are also the magic runes for hoisting the missing programs out of the old distro.

http://code.google.com/p/mizar32...

Yes, Atmel's Linux distro support is a barely functional crock. They should employ me :)

M


Thanks, I'll take a look. If I had of known that I'd be spending a whole day trying to install broken software I would have just gone and built the toolchain from scratch - like I do for my ARM development work.

I tell you what would be useful, get newlib out of the toolchain! In comparison, AVR-glibc has better features than that thing (for smaller processors). e.g. tying the uart to stdio is really easy, no SRAM is wasted for a heap that never gets used.

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

martinwguy wrote:
Hi
Iàve writte a tutorial about diffferent ways of installing the latest GNU toolchain, including compiling it from source, which is sure to work everywhere. There are also the magic runes for hoisting the missing programs out of the old distro.

http://code.google.com/p/mizar32...

Yes, Atmel's Linux distro support is a barely functional crock. They should employ me :)

M


Thank you! I've now got a (mostly) working AVR32Studio 2.5 with the old toolchain 2.4.2. I can use existing project files.

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

Hi,

I tried installing the 2.4.2 Toolchain using martinwguy's instructions as I need the avr32program e.t.c to run avr32studio. Unfortunately it doesn't seem to work because I'm running Linux (Ubuntu 11.10) at 64bit.
To be honest if I can avoid using any IDE I'd be happy but at the moment I can't figure out anyway of uploading code onto my UC3C0512C on my STK600 on linux at all. Avrdude doesn't support avr32 right?

Any Ideas?

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

AVRDUDE is only for AVR (not AVR32).
FLIP should work but I don't know if FLIP on Linux was updated for UC3C.
An alternate for USB DFU is http://dfu-programmer.sourceforge.net/
and it has been updated for UC3C.
I hope you still have Atmel's USB DFU bootloader on-chip.
Edit: Else AVR32 Studio 2.6 Release Notes mentions avr32program.

"Dare to be naïve." - Buckminster Fuller

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

Atmel's USB DFU bootloader can be reprogrammed from avr32 studio. In case you have a connected JTAGICE MKII debugger, right-click on it (AVR Targets). -> Program bootloader

It's also possible to use the "internal" studio's avr32tools from the command line. You will find them in the sub folder of your avr32 studio installation.

$ find . -iname avr32program
./plugins/com.atmel.avr.utilities.linux.x86_3.0.0.201012011602/os/linux/x86/bin/avr32program

-sb

PS.: UC3C0512C is not supported by avr32 studio 2.6 - I'm using the beta 2.7 version and you can download a 64-Bit version here: http://www.atmel.no/beta_ware/
command line looks like:
$ avr32program -pjtagicemkii -c USB:${1} --part ${2} program -finternal@0x80000000,512Kb -cint -v -O0x80000000 -Felf ${3}
with: ${1} set to your debugger's 12-digit serial numer, ${2} set to UC3C0512C and your elf-binary ${3}

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

Thanks, I'll give it a go.