Which release packages should I download?

I'm wanting to get the latest version of the toolchain binaries, but on the download page there's loads of different packages listed and in different file formats (.tar.bz2 & .rpm):


What are they all for and which one(s) should I download?

  • Which packages you should download depends on what you are wanting to do.

    For the remainder of this post I'll be using "2011R1" as the major release and "RC2" as the release candidate.  However you should substitute this for whatever release it is that you're looking for.

    If you're using Windows, it's an easy choice, you want the package:


    If you're using a Mac (OS X), then it's also straight forward:


    For Linux, it's a little more complicated.  First of all, choose whether you want to manually unpackage the binaries yourself using the .tar.bz2 files, or use RPM (originally "Red Hat Package Manager", latterly the recursive backronym "RPM Package Manager") to install the .rpm files.  If your distribution supports RPM, then you might as well use that.

    There are usually 4 primary packages:

    • blackfin-toolchain-2011R1-RC2.i386.rpm - This is the main package and contains the default bfin-uclinux/bfin-linux-uclibc toolchains.  you should always install this.
    • blackfin-toolchain-uclibc-default-2011R1-RC2.i386.rpm - This is the default libc library for the toolchain package above.  You usually want to download this.
    • blackfin-toolchain-uclibc-full-2011R1-RC2.i386.rpm - This is the same as above, but contains wchar, IPv6 and FTW support.  Download this instead of above if you think you need these features.
    • blackfin-toolchain-elf-gcc-4.3-2011R1-RC2.i386.rpm - This package contains the default version of the bfin-elf toolchain.  Download this if you plan to do any bare-metal development.

    As well as these default packages, there are usually "addon" packages.  These provide you with an alternative version of GCC.  If the version number in the addon packages is lower than the version in the main packages, then the addon compiler is a legacy compiler provided for backward compatibility with a previous release.  If the version number is higher, then it is an experimental compiler to let you try out newer features.  Using the experimental compiler can be risky however, as it hasn't yet had the same amount of testing as the default compiler.  The addon packages have the same name as the other packages, but with "gcc-4.5-addon".  e.g.

    • blackfin-toolchain-gcc-4.5-addon-2011R1-RC2.i386.rpm
    • blackfin-toolchain-uclibc-default-gcc-4.5-addon-2011R1-RC2.i386.rpm
    • blackfin-toolchain-uclibc-full-gcc-4.5-addon-2011R1-RC2.i386.rpm
    • blackfin-toolchain-elf-gcc-4.5-addon-2011R1-RC2.i386.rpm

    The addon compiler will be installed alongside the default compiler. e.g.:

    >which bfin-elf-gcc


    >ls /opt/uClinux/bfin-elf/bin/bfin-elf-gcc*

    /opt/uClinux/bfin-elf/bin/bfin-elf-gcc   // this is an exact copy of the default compiler.

    /opt/uClinux/bfin-elf/bin/bfin-elf-gcc-4.3.5 // this is the default compiler.
    /opt/uClinux/bfin-elf/bin/bfin-elf-gcc-4.5.3 // this is the experimental addon compiler.

    You may also notice some packages with "x86_64" instead of "i386".  These are the 64-bit versions of the packages above designed for 64-bit hosts.

    Finally, there's also the "src" packages:



    These are simply the source files used to build the binaries.  If you want to tweak the build in any way, feel free to download these.  However, it is a lot easier to just use our pre-built binaries.

    For further reading on installing packages:



  • 0
    •  Analog Employees 
    on Apr 29, 2019 10:36 AM
    This question has been closed by the EZ team and is assumed answered.