Comments for ElectricRock Blog

Comment on Using C30 with Piklab by Kemp

Kemp — Wed, 17 Feb 2010 16:56:57 +0000

Scratch that, I’m getting that default linker script error as posted by someone else above. v3.23 of everything with the Lite (academic) compiler. Also occurs with the the p24FJ64GA002.gld linker script selected instead of the default one. Did anyone find a consistently working resolution for this?

Comment on Using C30 with Piklab by Kemp

Kemp — Wed, 17 Feb 2010 16:49:47 +0000

Compiling for PIC24F seems to work fine with instructions as given and v3.23 of Microchip’s side of things. Will report back on programming soon.

Comment on Building Microchip’s C30 Compiler v3.20 on Ubuntu 9.10 by Kemp

Kemp — Wed, 17 Feb 2010 16:32:20 +0000

Build process confirmed to work for 3.23. The names for files on the Microchip website are slightly different now, but it’s fairly easy to spot what you need.

Comment 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

Comment on Installing Microchip’s C Compiler for PIC24 MCUs and dsPIC DSCs (C30) on Ubuntu 9.04 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.

Comment on Using C30 with Piklab by matt

matt — Mon, 25 Jan 2010 22:26:15 +0000

Hey, sorry about the delay replying, I am in the US attending a conference. Not sure about libgcc, I have never had issues with it. Do you need it to build the c30 compiler, or to build firmware with the c30 compiler?

Also, on a side node I found out how I solved previously solved the syntax error in the linker scripts. I was just looking through an old project, in which I had copied over the linker script and had just deleted the two CRT0_STARTUP and CRT1_STARTUP lines .

Comment on Using C30 with Piklab by Netfoot

Netfoot — Fri, 22 Jan 2010 23:13:55 +0000

Matt, I can’t seem to find the libgcc library. Any suggestions?

Comment on Using C30 with Piklab by matt

matt — Thu, 21 Jan 2010 19:39:57 +0000

Sweet, glad to hear you’ve made progress . When you say undefined references, do you mean within the PIC peripheral libraries? I found when I was trying to use I2C with the 30F4013, that support for it was missing from the library. If this is the case, they supply the sources so you can either recompile the library yourself (by running a two hundred thousand line DOS .BAT script — I was going to write a makefile but never got around to it), or just include the appropriate files into your project.

Anyway, good luck with your project. I’m gonna be away from the computer for a couple of days but keep us posted with your progress. Cheers

Comment on Using C30 with Piklab by Netfoot

Netfoot — Thu, 21 Jan 2010 16:31:05 +0000

Ok, Matt! With help from some friends (thanks Adam & Peter) I’ve made some progress by adding

find . -name “*.y” -o -name “*.l” -exec touch ‘{}’ ‘;’

just before making binutils. Still got some errors to deal with (undefined references due to a missing library, it looks like), but not script syntax related.

Comment on Using C30 with Piklab by Netfoot

Netfoot — Wed, 20 Jan 2010 02:49:03 +0000

Using “v3.20-Slackware” gets rid of the strange symbols (the word “Slackware” appears instead). Unfortunately, it doesn’t get rid of the syntax error in line 6…