Comments on: Installing Microchip’s C Compiler for PIC24 MCUs and dsPIC DSCs (C30) on Ubuntu 9.04

By: matt

matt — Wed, 27 Jan 2010 14:31:51 +0000

Hi Marc. I think you can solve this by creating a link to c30_device.info in your $C30INSTALL/bin directory. If this doesn’t work for you, then you can try adding the -mresource argument on the commandline. If you were running gcc directly from the commandline (e.g. running $C30INSTALL/bin/pic30-coff-gcc -mcpu=30F4013 -o test test.c) you would just add in the -mresource argument, giving you ‘$C30INSTALL/bin/pic30-coff-gcc -mcpu=30F4013 -mresource=$C30INSTALL/info/c30_device.info -o test test.c’.

If you are using a GUI, how you add this is dependent on the application you’re using. If you’re using Piklab look here: http://www.electricrock.co.nz/blog/2009/08/using-c30-with-piklab

By: Marc Michels

Marc Michels — Tue, 26 Jan 2010 21:56:45 +0000

Followed your guide and succesfully installed V3.22 on Gentoo. Great write-up!!

Ran into the “Provide a recource file” error and now I’m puzzled. What do you mean by:

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

How do you add to a GCC command line, especially in a GUI?

I’m quite sure I linked everything correctly so I doubt it’s that.

By: Building Microchip’s C30 Compiler v3.20 on Ubuntu 9.10 - ElectricRock Blog

Building Microchip’s C30 Compiler v3.20 on Ubuntu 9.10 - ElectricRock Blog — Sun, 03 Jan 2010 06:06:10 +0000

[...] matt on Jan.03, 2010, under How To This an update to my previous tutorial for building Microchip’s C Compiler for PIC24 MCUs and dsPIC DSCs (herein referred to as C30). [...]

By: László Meskó

László Meskó — Mon, 02 Nov 2009 07:36:34 +0000

Thank you the install guide!
To make it better, in the troubleshooting, it worth to mention the following:
If you create a test2.c sample code with the following:
int main(){ while(1); }
you can get an error.
Because this empty loop contains a negative jump, you can get an error message on 64 bit systems:
Link Error: PC Relative branch to ‘.L4′ is out of range. Suggest large-code model.
The problem is the negative integer size on 64 bit. The solution is to modify 2 lines in the binutils ource, in acme/bfd/elf32-pic30.c and acme/bfd/coff-pic30.c:
(source is:
http://old.nabble.com/dsPIC-toolchain-%28GNU-Linux%29-td23349948.html
)
I’ve modified the source code manually, it seems to work for me. (The website doesn’t mention the modification of coff-pic30.c, but is is required also)

–

— acme/bfd/elf32-pic30.c.orig 2009-05-04 15:39:05.000000000 +0100
+++ acme/bfd/elf32-pic30.c 2009-05-04 15:35:43.000000000 +0100
@@ -1973,7 +1973,7 @@
case R_PIC30_PCREL_BRANCH:
case R_PIC30_BRANCH_ABSOLUTE:
/* valid range is [-32768..32767] and not [-2, -1, 0] */
- if ((relocation > 0×7FFF) && ~(relocation | 0xC0007FFF))
+ if ((relocation > 0×7FFF) && ~(relocation | 0xFFFFFFFFC0007FFFull))
{
*error_msg = (char *) malloc(BUFSIZ);
sprintf(*error_msg,
@@ -1986,7 +1986,7 @@
case R_PIC30_PCREL_DO:
case R_PIC30_DO_ABSOLUTE:
/* valid range is [-32768..32767] and not [-2, -1, 0] */
- if ((relocation > 0×7FFF) && ~(relocation | 0xC0007FFF))
+ if ((relocation > 0×7FFF) && ~(relocation | 0xFFFFFFFFC0007FFFull))
{
*error_msg = (char *) malloc(BUFSIZ);
sprintf(*error_msg,

–

By: Using C30 with Piklab - ElectricRock Blog

Using C30 with Piklab - ElectricRock Blog — Sun, 30 Aug 2009 21:12:29 +0000

[...] matt on Aug.31, 2009, under How To This post follows on from my previous post on building Microchip’s C compiler for PIC24 and dsPIC (C30) onUbuntu. Piklab is a great IDE for PIC development, and IMHO much nicer to use than MPLAB. Piklab has [...]