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.