ChipKit is a Microprocessor platform produced by Digilent Inc. which provides an Arduino like environment and a physically compatible board, but runs the much quicker and more powerful PIC32 series of Processors.
There are two boards, the Uno32 which has 128k of Flash and 16k of RAM, and the Max32 which has 512k of Flash and 128k of RAM. Both boards run at 80Mhz. Prices are $27 and $50 respectively, so comparable with standard and advanced Arduinos.
This install was for a 64-bit machine and an Uno32. I do not have a Max32 or a 32-bit machine, but the process should be identical for the hardware change, and simpler for the software change. However, the 32 bit install has not been verified.
At the time of installation I was running Java 7 and Kernel 3.0.1
Requirements (all architectures)
Install rxtx from the AUR.
At the time of writing, it is necessary to edit the PKGBUILD which refers to kernel26-headers so it refers to linux-headers.
Install binutils-avr from the repositories.
This is required only because the ChipKit software needs the program avr-size. It comes with the rest of its own software. If you use Arduino on Arch you will know there is a nasty bug which means the current gcc-avr and binutils-avr do not work correctly. In that case do not install the new binutils-avr but use these PKGBUILDs here (untar them in /var/abs/local) which produce versions that do work correctly. You will need to add gcc-avr and binutils-avr to IgnorePkg = in /etc/pacman.conf to stop pacman upgrading them.
Requirements (32 bit versions)
libusb and libusb-compat are required, but may well be installed by default.
Requirements (64 bit versions)
The software expects 32 bit libraries, so some extra installations are required.
Install lib32-libusb and lib32-libusb-compat so the software can communicate with the USB ports.
Install lib32-elfutils from the AUR. If you just have the standard gcc package, this will require replacing it with gcc-multilib
Download the current Linux install from here. This was tested using file mpide-0022-chipkit-linux32-20110619.tgz
Untar the file in an appropriate location, I was using /aux. Note the use of the 'j' to preserve the flags for the file.
cd /aux tar xjvgp mpide-0022-chipkit-linux32-20110619.tgz
Running the IDE
You can run the ChipKit environment by changing to that directory and running mpide
cd /aux/mpide-0022-chipkit-linux32-20110619 ./mpide
This brings up the familiar Arduino IDE. You can set the Board Type to Uno32 or Max32 as you would when selecting a different Arduino board. The simplest way to test it is by using Example Blinky and changing the delay times so the LED is on for only 200ms (for example).