Instructions and download here: http://www.electricrock.co.nz/blog/microchip-c30/.

Latest version of the script can be found here: http://www.electricrock.co.nz/blog/microchip-c30/

This an update to my previous tutorial for building Microchip’s C Compiler for PIC24 MCUs and dsPIC DSCs (herein referred to as C30). This update covers building v3.20 of the compiler (as opposed to v3.12) under Ubuntu 9.10.  Again, this is mostly gleaned from  http://embeddedfreak.wordpress.com/2008/10/10/compiling-mplab-c30-v311b-under-linux, but adapted for the latest version of C30.

These instructions also work for v3.22 and are reported to work with v3.23.

Installation

Install prerequisite software

• Install packages from the Ubuntu repositories:

  sudo aptitude install build-essential bison flex tofrodos

• Install wine (instructions available from the Wine website: http://www.winehq.org/download/deb). I used the following steps to install the latest version (you can just install the one in the Ubuntu repositories if you aren’t worried about being bleeding edge):

  sudo add-apt-repository ppa:ubuntu-wine/ppa
  sudo aptitude install wine

Setup paths

The exports below can be varied depending on where you prefer things to be put. At the risk of stating the obvious I’ll outline what each of the exports is for:

• C30BUILD is the temporary directory where the C30 tool suite is built.
• C30INSTALL is  where it will be installed to.
• DOWNLOADDIR is where you save files to when downloading.
• WINEPREFIX is where you want to install the proprietary tool suite.

export C30BUILD=$HOME/c30-build
export C30INSTALL=$HOME/Apps/pic30
export DOWNLOADDIR=$HOME/Downloads
export WINEPREFIX=$HOME/Apps/pic30-wine

Download sources, etc.

• From Microchip’s website download the sources for the compiler and binutils.  They can be found on this page: http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en023073. You will need to login to download.  You want to get:
  • GCC Code for MPLAB ASM30 for dsPIC/PIC24 v3.20
  • MPLAB C30 v3.20 GCC Source
• Download the academic or evaluation version of the proprietary compiler from the C30 website (http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010065)
• Download the patches. I have adapted these from those provided by John Steele Scott (see my previous post) to work with v3.20.
  • Binutils: http://www.electricrock.co.nz/c30/pic30-binutils-3.20.tar.bz2
  • GCC: http://www.electricrock.co.nz/c30/pic30-gcc-3.20.tar.bz2

Building Binutils

• Unzip the sources.

  mkdir -p $C30BUILD/binutils
  cd $C30BUILD/binutils
  tar -zxvf $DOWNLOADDIR/mplabalc30v3_20.tar.gz
  tar -jxvf $DOWNLOADDIR/pic30-binutils-3.20.tar.bz2
  

• The microchip sources have been edited on windows, so we need to convert files to unix line endings so that they can be patched.

  find . -type f -exec dos2unix '{}' ';'

• Apply the patches.  So far as I can tell, these fix a few compile issues with the microchip compiler and make it play nicer under Linux.

  for i in pic30-binutils-3.20/patches/*.diff; do echo "Applying patch $i..."; patch -p0 < $i; done

• Build it, the version number in DMHCP_VERSION needs to match the version of the non-free compiler you install.

   cd acme/
  CFLAGS=-DMCHP_VERSION="v3.20-Debian" ./configure --prefix=$C30INSTALL --target=pic30-coff
  

• Before we can make it we need to touch some files otherwise it doesn’t get built properly.

  find . -name "*.y" -o -name "*.l" -exec touch '{}' ';'

• Make it.

  make

• Install, if you install to a location that you don’t have write permission to (e.g. /usr/local) you will need to use sudo.

   make install 

Building GCC

• Similar process to binutils above for building GCC.

  mkdir -p $C30BUILD/gcc
  cd $C30BUILD/gcc
  tar -zxvf $DOWNLOADDIR/mplabc30v3_20.tar.gz
  tar -jxvf $DOWNLOADDIR/pic30-gcc-3.20.tar.bz2
  find . -type f -exec dos2unix '{}' ';'
  for i in pic30-gcc-3.20/patches/*.diff; do echo "Applying patch $i..."; patch -p0 < $i; done

• We take a slight deviation from binutils here as we create a separate directory for GCC to build in, apparently it likes it that way.

  mkdir build
  cd build
  CFLAGS=-DMCHP_VERSION="v3.20-Debian" ../gcc-4.0.2/gcc-4.0.2/configure --prefix=$C30INSTALL --target=pic30-coff --enable-languages=c

• Then we have to touch c-parse.y cause (according to embeddedfreak) it doesn’t get generated correctly, so we need it to be recreated. I just followed the instructions and it worked.

  touch ../gcc-4.0.2/gcc-4.0.2/gcc/c-parse.y

• Build it and install it (again, use sudo for make install if you have to).

  make
  make install

• Link the binutils into GCC’s tool path so it can find them, and create a link to GCC itself so we don’t have to type the version number every time:

  ln -s $C30INSTALL/bin/pic30-coff-as $C30INSTALL/libexec/gcc/pic30-coff/4.0.3/pic30-coff-as
  ln -s $C30INSTALL/bin/pic30-coff-ld $C30INSTALL/libexec/gcc/pic30-coff/4.0.3/pic30-coff-ld
  ln -s $C30INSTALL/bin/pic30-coff-gcc-4.0.3 $C30INSTALL/bin/pic30-coff-gcc

Next Steps

The rest of the steps are just the same as for building v3.12.  I won’t repeat myself here, just check out my previous tutorial and follow the steps from Setup the non-free part onward.

Setup

1. Add yourself to the lp group so that you can access the parallel port without needing to be superuser (you will need to log out and back in again after this command):
   sudo usermod -a -G lp <username>
   
2. Install uisp:
   sudo aptitude install uisp
3. Connect the JTAG cable to your target device as follows:
   

   JTAG	Target
   Vcc	Vcc
   GND	GND
   TDI	MOSI
   TDO	MISO
   TCK	SCK
   TMS	RST

Some useful UISP commands

These are given for AT89S52, but for other AVR series it should work if you just drop the -d89 flag and use the appropriate part number. The main thing to note here is that the dprog flag is set to xil to indicate we are using a DLC5 for programming.

If you have issues try adding -v=3 or -v=4 for more verbose output from UISP.

Configuring the Toolchain

NB: The following assumes <C30-base> is the directory where C30 was installed (if you followed my previous tutorial this will be whatever you set for the C30INSTALL environment variable).

• Open up Piklab and go to Settings->Configure Toolchains…
• In the Configure Toolchains window select PIC30 Toolchain from the sidebar.
• Fill out the fields as follows:
  • Executable directory – <C30-base>/bin
  • Header directory – <C30-base>/pic30-nonfree/support/dsPIC30F/h/ (assuming you are using C30 to compile for dsPIC30F series–I haven’t tried any other series, so YMMV).
  • Linker script directory – <C30-base>/pic30-nonfree/support/dsPIC30F/gld/
  • Library directory – <C30-base>/pic30-nonfree/lib/
    
• The other fields can be left as the default.

Configuring the Project

For each project you will also have to do some configuration. After creating a new project, bring up the Project Options window (Project->Project Options…), and fill in as follows:

• Toolchain tab
  • Make sure PIC30 Toolchain is the active toolchain.
• Compiler tab
  • In the Custom options field enter: -mresource=<C30-base>/info/c30_device.info
• Linker tab
  • In the Custom libraries field enter: -lpic30

That should be enough to build coff files in Piklab.  I have successfully programming the dsPIC30F4013 from Piklab using the above toolchain to build the firmware and an Microchip ICD2 to download it to the PIC.  If you have any issues, if this doesn’t work for you, or if you have had some luck using a different family of PICs with C30, then please leave a comment.

Microchip’s C Compiler for PIC24 MCUs and dsPIC DSCs (herein referred to as C30) is a GCC derivative and therefore the sources are freely available to build it on any platform.  However, the documentation for getting a working setup seems to be sparse.  This blog entry details the steps I followed to install it under Ubuntu 9.04, mostly gleaned from  http://embeddedfreak.wordpress.com/2008/10/10/compiling-mplab-c30-v311b-under-linux. There are some small changes from the embeddedfreak version, I am using v3.12 of the compiler (the most recent version at the time of writing) and I will provide details of how to setup the non-free part.

Code lines in blue are to be executed at the terminal, sorry that they look so ugly at the moment–I will pretty up the formatting at some point.

Disclaimer: These instructions are provided as a guide only, you use them at your own risk–I accept no responsibility if something goes wrong .

Installation

Install prerequisite software

• Install packages from the Ubuntu repositories:
  sudo aptitude install build-essential bison flex tofrodos
• Install wine (instructions available from the Wine website: http://www.winehq.org/download/deb).

Setup paths

The exports below can be varied depending on where you prefer things to be put. At the risk of stating the obvious I’ll outline what each of the exports is for:

• C30BUILD is the temporary directory where the C30 tool suite is built.
• C30INSTALL is  where it will be installed to.
• DOWNLOADDIR is where you save files to when downloading.
• WINEPREFIX is where you want to install the proprietary tool suite.

export C30BUILD=$HOME/c30-build
export C30INSTALL=$HOME/Apps/pic30
export DOWNLOADDIR=$HOME/Downloads
export WINEPREFIX=$HOME/Apps/pic30-wine

Download sources, etc.

• From Microchip’s website download the sources for the compiler and binutils.  They can be found on this page: http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en023073. You will need to login to download.  You want to get:
  • GCC Code for MPLAB ASM30 for dsPIC/PIC24 v3.12
  • MPLAB C30 v3.12 GCC Source
• Download the academic or evaluation version of the proprietary compiler from the C30 website (http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010065)
• Download John Steele Scott’s patches
  • Binutils: http://www.4shared.com/file/75582162/7a251aaf/pic30-binutils-311btar.html
  • GCC: http://www.4shared.com/file/76025702/9eb06aad/pic30-gcc-311btar.html

Building Binutils

• Unzip the sources.
  
mkdir -p $C30BUILD/binutils
cd $C30BUILD/binutils
tar -zxvf $DOWNLOADDIR/mplabalc30v3_12.tar.gz
tar -jxvf $DOWNLOADDIR/pic30-binutils-3.11b.tar.bz2
• The microchip sources have been edited on windows, so we need to convert files to unix line endings so that they can be patched.
  find . -type f -exec dos2unix '{}' ';'
• Apply John Steele Scott’s patches.  So far as I can tell, these fix a few compile issues with the microchip compiler and make it play nicer under Linux.
  for i in pic30-binutils-3.11b/patches/*.diff; do echo "Applying patch $i..."; patch -p0 < $i; done
• Build it, the version number in DMHCP_VERSION needs to match the version of the non-free compiler you install.
  cd acme/
CFLAGS=-DMCHP_VERSION="v3.12-Debian" ./configure --prefix=$C30INSTALL --target=pic30-coff
make
• Install, if you install to a location that you don’t have write permission to (e.g. /usr/local) you will need to use sudo.
  make install

Building GCC

• Similar process to binutils above for building GCC.
  mkdir -p $C30BUILD/gcc
cd $C30BUILD/gcc
tar -zxvf $DOWNLOADDIR/mplabc30v3_12.tar.gz
tar -jxvf $DOWNLOADDIR/pic30-gcc-3.11b.tar.bz2
find . -type f -exec dos2unix '{}' ';'
for i in pic30-gcc-3.11b/patches/*.diff; do echo "Applying patch $i..."; patch -p0 < $i; done
• We take a slight deviation from binutils here as we create a separate directory for GCC to build in, apparently it likes it that way.
  mkdir build
cd build
CFLAGS=-DMCHP_VERSION="v3.12-Debian" ../gcc-4.0.2/gcc-4.0.2/configure --prefix=$C30INSTALL --target=pic30-coff --enable-languages=c
• Then we have to touch c-parse.y cause (according to embeddedfreak) it doesn’t get generated correctly, so we need it to be recreated. I just followed the instructions and it worked.
  touch ../gcc-4.0.2/gcc-4.0.2/gcc/c-parse.y
• Build it and install it (again, use sudo for make install if you have to).
  make
make install
• Link the binutils into GCC’s tool path so it can find them, and create a link to GCC itself so we don’t have to type the version number every time:
  ln -s $C30INSTALL/bin/pic30-coff-as $C30INSTALL/libexec/gcc/pic30-coff/4.0.3/pic30-coff-as
ln -s $C30INSTALL/bin/pic30-coff-ld $C30INSTALL/libexec/gcc/pic30-coff/4.0.3/pic30-coff-ld
ln -s $C30INSTALL/bin/pic30-coff-gcc-4.0.3 $C30INSTALL/bin/pic30-coff-gcc

Setup the non-free part

• Install the downloaded non-free version of the compiler using WINE. Make sure you run this from the terminal after setting the WINEPREFIX environment variable (as opposed to e.g. double clicking the EXE icon).
  wine {path to installer.exe}
• Copy required directories and files, it would probably be tidier to fix the search path for the info files in the source, but instead I just make some links where necessary.
  cp $WINEPREFIX/drive_c/Program\ Files/Microchip/MPLAB\ C30/bin/c30_device.info $C30INSTALL/info
ln -s $C30INSTALL/info/c30_device.info $C30INSTALL/c30_device.info
ln -s $C30INSTALL/info/c30_device.info $C30INSTALL/libexec/gcc/pic30-coff/c30_device.info
mkdir $C30INSTALL/pic30-nonfree
cp -r $WINEPREFIX/drive_c/Program\ Files/Microchip/MPLAB\ C30/support $C30INSTALL/pic30-nonfree
cp -r $WINEPREFIX/drive_c/Program\ Files/Microchip/MPLAB\ C30/include $C30INSTALL/pic30-nonfree
cp -r $WINEPREFIX/drive_c/Program\ Files/Microchip/MPLAB\ C30/lib $C30INSTALL/pic30-nonfree

Troubleshooting

Provide Resource File

When running the compiler you may find that it baulks when running a command such as:
$C30INSTALL/bin/pic30-coff-gcc -mcpu=30F4013  -o test test.c
with the error
pic30-coff-cc1: warning: Provide a resource file
pic30-coff-cc1: error: Invalid -mcpu option.  CPU 30F4013 not recognized.

To solve this add -mresource=$C30INSTALL/info/c30_device.info to your GCC command line.

Unknown Processor

If you get the error:
Unknown processor 30F4013.
Then you haven’t created the links to the info file correctly. I found from running gcc with the -v (verbose) flag that this error is actually generated by the assembler, which is being called from under the libexec directory (hence the need for the info file to be linked there also.)

Next Step

Now that you have built a working toolchain, it’s time to setup an IDE to use with it (if you are that way inclined).  I recommend Piklab. You can find instructions for using the C30 toolchain with Piklab in this post.

References

You should now have a working C30 compiler installed in $C30INSTALL.  Thanks to KUNILKUDA Embedded Freaks for the tutorial which I followed  and from which these instructions are mostly derived.