Comments on: Using C30 with Piklab

By: Justin

Justin — Thu, 27 May 2010 21:01:08 +0000

For the ‘__reset’ error make sure you include the following libraries -lpic30-coff -lm-coff -lc-coff

By: Nicolas

Nicolas — Sun, 02 May 2010 16:43:45 +0000

Do you know how to resolve the problem of encoding in Piklab ? It always prints strange characters in the console of Piklab even though when I use directly pic30-coff-gcc it prints fine. I suspect a problem of encoding (UTF-8 …).

By: Kemp

Kemp — Wed, 17 Mar 2010 14:48:37 +0000

I’ve rebuilt using the new command before making binutils, but I’m now getting undefined references to PORTB and all of the I2C1* sort-of-variables. I have -I/home/kemp/pic30/pic30-nonfree/support/PIC24F/h/ in the GCC calls (that’s the PIC I’m targetting) but the error occurs when linking. It worked prior to the rebuild. I’m wondering if this is a similar issue to the one Netfoot had after rebuilding.

By: Chris

Chris — Wed, 10 Mar 2010 23:30:15 +0000

Kemp, I just got it to work using the above instructions. You need to rebuild binutils. You can just do a make clean, then run the command supplied by
netfoot above:

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

When I copied and pasted it, it messed up the quotes, so make sure it’s typed in correctly. Next, make and make install. Revert any changes you made to the linker script. It worked for me at this point:

pic30-coff-gcc -mcpu=24FJ128GA010 -mresource=./pic30/info/c30_device.info ./test.c

Chris

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?

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.

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 .

By: Netfoot

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

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

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

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.