On May 26th 2011, new rules governing the use of cookies by websites came into force in Europe. This means that you are to be given the chance to actively agree (opt-in) to accept cookies on your device.

Some cookies are necessary for this site to work properly and will be stored temporarily on your computer and disappear when you close your browser. Cookies are also used so that you will have a better experience as a visitor to this website. Not allowing cookies may prevent you from using certain parts of this website.

Therefore we would like to place cookies on your device in order for this website to function in the way that we intended.

Public Software Repository - 2016-11-06

[Previous release 2016-09-06]


Manifest

  • Swiss Server v1.0.1 UPDATED
  • Swiss RS-485 Control v1.0.1 UPDATED
  • RS-485-SPI v1.0.0
  • RS-485-I2C v1.0.0
  • SwissClient-PHP v1.0.1 UPDATED
  • Swiss Python Examples NEW
  • AxiCat Server v1.3.2 UPDATED
  • AxiCat AVR ISP v1.1.0 UPDATED
  • AxiCat AL library v1.3.1
  • AxiCat Command Line Tool v1.3.1
  • AxiCat Main v1.3.2
  • AxiCat-164 Bootloader v1.0
  • AxiCat-324 Bootloader v1.0
  • AxiCat MicroVGA v1.0.0 NEW
  • Audio Visualizer Demo v1.1.0 NEW
  • Audio Visualizer Main v1.3 NEW
  • Audio Visualizer Bootloader v1.0 NEW
  • Audio Visualizer EM-800 P.C. v1.0 NEW
  • MCU Bootloader Tool v1.2.0 NEW
  • EEPROM 24C v1.0.1 UPDATED

Contents

Source code of the software. Makefiles and project files are included so you can build the software yourself. Binaries are provided as well.

You can find documentation in directories called "doc" that are scattered around the source code.

All packages were created from a single directory structure with "public" as the base directory. You're advised to extract sources and required binaries to the same directory to recreate a repository for the platform of your choice. Simply extract to a local directory. There's no installation procedure.

We're regularly improving software and adding new code and documentation, so check it out from time to time.


Picking the Right Packages

The packages are distributed as tar-gzip and zip files. Both formats are compression formats. Zip files are typically used in Windows. A tar-gzip file additionally contains file permissions and is mainly used in Linux.

If a package is available in both formats (e.g. src and avr8), the contents of both files are the same.

AVR-8

These packages contains firmware binaries for various boards and products that incorporate an Atmel AVR 8-bit microcontroller. The filename of the packages is structured as follows:

  • public-date-avr8.tar.gz
  • public-date-avr8.zip
date Release date of the package.
avr8 Indication for AVR 8-bit.

There's an ELF file (.elf) and an Intel HEX file (.hex) for each firmware binary. Most in-system programmers and bootloader tools support these file types, including AxiCat AVR ISP and MCU Bootloader Tool.

Linux

The Linux versions of the binaries are distributed as a tar-gzip archive files. The filename of the packages is structured as follows:

  • public-date-linux-architecture.tar.gz
date Release date of the package.
architecture A name that indicates the architecture for which the package is meant.

Linux is available on a variety of so-called architectures. The architecture is about the environment programs run in. It involves the instruction set architecture (ISA) of the processor, the Application Binary Interface (ABI) for calling the Linux kernel and libraries, use or emulation of floating point unit (FPU) instructions. An ISA can have many versions that are upwards compatible, like the Intel x86 family of processors for example.

The software runs on several architectures. There's a package for each supported architecture. The architecture portion of the filename marks the target architecture:

armel ARM processor, 32-bit, Little Endian, FPU emulated in software (soft-float).
armhf ARM processor, 32-bit, Little Endian, FPU present (hard-float).
i486 Intel 80486 or later processor, 32-bit.
amd64 AMD64 and Intel 64 instruction set, 64-bit.

This list may seem limited, nevertheless it covers a wide range of Linux-based systems including SBCs, PCs and embedded systems.

The armel and armhf architecture are very commonplace nowadays. Many single board computers (SBCs) and other Linux devices are equipped with an ARM-based application processor, like BeagleBone and RPi.

Probably the most difficult part is to determine whether the armel or armhf package must be used. This really depends on your Linux distribution. Your distribution may explicitly state the architecture. In many cases, architecture armel is advertised as “soft float”, while armhf is advertised as “hard float”. If this doesn't help, use the method using gcc as explained later.

The i486 and amd64 architectures are typically used on PCs. Some SBCs may also incorporate an x86 or compatible processor.

If you've difficulty determining the architecture of your particular Linux installation, you can run the following command:

$ gcc -dumpmachine

Note that gcc must have been installed for this to work.

The outcome of this command is the compiler's “target machine” a.k.a. “GNU triplet” which is key in determining the architecture of your Linux system. Here's a list of commonly produced results and the corresponding architecture name:

arm-linux-gnueabi armel
arm-linux-gnueabihf armhf
i486-linux-gnu
i586-linux-gnu
i686-linux-gnu
i486
x86_64-linux-gnu amd64

It may be possible that your particular architecture isn't supported. If so, you may contact us, we may be able to create a package for your Linux system.

Windows

This package contains executables for Windows 2000 and later. The filename of the package is structured as follows:

  • public-date-win32.zip
date Release date of the package.
win32 Indication for Win32 environment.

All binaries are 32-bit executables. The binaries run on 64-bit versions of Windows as well.