Home News Features Examples Code FAQ License
AVR Webring
Prev Hub Join Rate Next
Source code, documentation binaries and scripts.

Last minute changes

This section has been moved to the Forum 'Releases' on Source Forge.

Source and documentation

Download the most recent release from sourceforce, using the 'download' button above. In the distribution you will find a toolchain builder (binutils, libc, gcc, avrdude), Femto OS source and examples, and binaries of all examples (for all devices) ready to flash! For further elaboration and the nightly see below. Comments are inside the code and i have run Doxygen over the most recent release and the result can be seen directly, without first downloading the code. You can also have a look at the online api and configuration documentation.

Bugs, contributions and communication.

I welcome contributions to the code, bugs found and improvements. Please note the source forge forum is the proper place for this. The email address below is only for contacting me for commercial support, or to get my attention if i do not respond to your posting (usually within a few days). Discussions about the code should not go by email since then nobody can benefit.

Quality assurance and testing.

Before releasing a new package i test the demos in several ways. There are, at the moment, 44 ports, 13 demos and two 'major' compiling settings (optimized and standard). This alone results in over 1100 different executables that must be tested. If we would extend this to different toolchain versions (gcc 4.2.x, gcc 4.3.x, Eclipse, WinAvr etc etc) different platforms (Windows, Linux, Mac) the numbers grow beyond anything reasonable. Therefore we have to draw the line somewhere. Before release i do the following:

  1. Toolchain is updated and tested for Linux (Gentoo, Ubuntu), Mac OS 10.5 and Windows XP/2000.
  2. With this toolchain, all examples are compiled for all ports, only new ports are tested.
  3. ATtiny861 and ATmega328P are tested more thoroughly.
Although the code is pure standard C, and therefore should run on other compilers (such as WinAVR) i did not test this. From experience however, i know that this can be cumbersome. The enclosed toolchain builder builds a local toolchain (no root access needed), and with the commandline compiler script uses this. This has been tested, use it first.

Hello World

The distribution now contains an 'Hello World' application. This is mean as a start for your applications, so modify it and test. The other examples are not meant to be modified, and if you try you might be in for a disappointment (or steep learning experience :-) The reason being that in the other examples cutting edge optimizations have been used, which will probably not work with your code. Play around with the Hello World first. Use the ' Getting Started Guide'.

Download source and binaries, nightly.

The download contains several sections:

  1. sources, settings
  2. script files
  3. binaries
  4. all examples in an eclipse project
  5. communication and trace program

Using only the sources requires you know how to setup a C project for your environment. Thus you must install your GCC, binutils, libc etc etc yourself: recommended for those with hands-on experience on Atmels embedded devices. You have the option to use the install scripts to setup your environment under Linux, Mac or Windows (with cygwin). For windows you can also directly use the AVR environment from Atmel with WinAVR. The binaries give you the possibility to first test the examples which can be flashed directly into your device using for example a STK500 board. They should run as in the videos.

The eclipse project files can be generated using the script and imported directly into eclipse (version Ganymede, Galileo) Eclipse with CDT) Note: i do not use the AVR plugin, and have no experience with it. One project (the shell) requires a terminal program to communicate with the device, which is delivered along. At the same time this program can be used to trace other applications you made. At the moment only available for Windows.

The nightly build can be downloaded here: MainCode.zip, but you still need the latest release to replace the directory called MainCode. Note that the nightly only contains changes to the source and not to scripts and other parts of the distribution. The nightly may be, an usually is, less stable as the latest release, it may not even compile at all. The nightly does not contain any binaries.

Contact: info@femtoos.org   CC-BY License: Ruud Vlaming.