Recent changes to bugs

Configuration Type missing when using Indigo Eclipse.

2011-07-20T21:01:05Z

When using Indigo:
Create a new C Project.
Give it a name.
Select PIC Cross Target Application->Empty Project.
Select “PIC C32”
Click Next.
You get the error "At least one configuration should be available. Project cannot be created."

I don’t know if this is an Eclipse bug but the workaround for PIC C Builder is to remove the name attribute from the <projectType> tag in the plugin.xml.
Diff attached.

Heap doesn't work

2011-06-03T17:38:48Z

I need a heap to use the snprintf functions. Adding the heap in the MicroChip IDE works fine but I get an error in eclipse when I add a heap either through the box or manually adding it to the command line. It seems to error out on the pic30-elf-ld.exe not the pic30-gcc executable.

*** Build of configuration hex for project MotorControlBoard ****

mingw32-make all
Building target: MotorControlBoard.elf
Invoking: PIC C30 C Linker
pic30-gcc -T"D:\Workspaces\PU33\JEC\MotorControlWorkspace\MotorControlBoard\gld\p33FJ128GP802mod2.gld" --heap=256 -Wl,-Map,MotorControlBoard.map -omf=elf -mcpu=33FJ128GP802 -o "MotorControlBoard.elf" ./src/main.o ./src/traps.o
c:\program files (x86)\microchip\mplabc30\v3.25\bin\bin\..\bin/pic30-elf-ld.exe Error: A heap is required, but has not been specified
mingw32-make: *** [MotorControlBoard.elf] Error 255

Input line is too long for C30 C Linker

2010-08-05T07:25:48Z

Because my project includes many of files, located in several folders. So, C30 Compiler generated *.o files in subfolders (not at the project's dir). This cause when Linker operates, the parameters must include the subpath of *.o files. This cause the error: "input line is too long".

In MPLAB IDE, all *.o files were generated at project's dir. So the parameters are just filenames only.
Would you mind adding another options for solving this problem?

This is the message from Eclipse console:

"mingw32-make all
'Building target: GPS.elf'
'Invoking: PIC C30 C Linker'
"pic30-gcc -Wl,-Map,GPS.map -omf=elf -mcpu=33FJ128GP706 --defsym=__MPLAB_DEBUG=1 -o"GPS.elf" ./TnD\ Stack/Stack/tnd_24lc512.o ./TnD\ Stack/Stack/tnd_8583.o ./TnD\ Stack/Stack/tnd_adc.o ./TnD\ Stack/Stack/tnd_delay.o ./TnD\ Stack/Stack/tnd_ecan.o ./TnD\ Stack/Stack/tnd_glcd.o ./TnD\ Stack/Stack/tnd_lcd.o ./TnD\ Stack/Stack/tnd_led.o ./TnD\ Stack/Stack/tnd_math.o ./TnD\ Stack/Stack/tnd_modbus_can.o ./TnD\ Stack/Stack/tnd_string.o ./TnD\ Stack/Stack/tnd_timer1.o ./TnD\ Stack/Stack/tnd_uart.o ./TnD\ Stack/Stack/MDDFS/FSIO.o ./TnD\ Stack/Stack/MDDFS/SD-SPI.o ./GPS\ Tracker\ v2.0/src/GPS\ Tracker\ v2.0.o ./GPS\ Tracker\ v2.0/src/funcs.o ./GPS\ Tracker\ v2.0/src/gprs.o ./GPS\ Tracker\ v2.0/src/gps.o ./GPS\ Tracker\ v2.0/src/init.o ./GPS\ Tracker\ v2.0/src/Modbus\ CAN/MCAppFuncs.o ./GPS\ Tracker\ v2.0/src/Modbus\ CAN/MCFifoSys.o ./GPS\ Tracker\ v2.0/src/Modbus\ CAN/MCMain.o "
The input line is too long.
mingw32-make: *** [GPS.elf] Error 1"

Wrong RM command on GNU/Linux

2010-06-21T02:46:06Z

(Honestly, I don't know if this is a piccbuilder bug or an Eclipse bug, so please correct me if I'm wrong.)

Using piccbuilder under Debian Squeeze, Eclipse 3.5, CDT 6.0. Under builder settings, I set the builder type to "External" (make -k -j4). Looking in the generated makefiles, I see the line:

RM := del

...which is wrong for a GNU/Linux system, it should be "rm" (or "rm -f"). This makes it impossible to "clean" a project.

(Doesn't piccbuilder require a mingw or cygwin toolset on Windows anyway? If so "rm" by default would work in either case.)

Generated linker flags mixes Wl, verbatim options

2010-04-28T04:36:48Z

This is using Eclipse 3.5, and MPLAB C32 1.10B (lite) under Windows, with a custom linker script to place code in the boot flash memory. I noticed some differences between the linking results under MPLAB and Eclipse, and investigated the command lines used by each program.

Under Eclipse, the linking stage is called with

-Wl,--script="..\linkers\script.ld" -L"C:\Program Files\Microchip\MPLAB C32\lib" -L"C:\Program Files\Microchip\MPLAB C32\pic32mx\lib"

Under MPLAB, the linking stage is:

-Wl,--script="..\linkers\script.ld",-L"C:\Program Files\Microchip\MPLAB C32\lib",-L"C:\Program Files\Microchip\MPLAB C32\pic32mx\lib"

Note the commas in the second version. This seems to make a difference when using the "-mips16" option with the linker. I'm not sure why, to be honest. (In the lite version of C32, the "-mips16" option is ignored when compiling code, but I think it has some effect on linking...)

The major outcome of all of this was that under Eclipse, my code does not compile, since it doesn't fit in the boot flash. Under MPLAB, it does.

If I have time, I'll try to come up with an example.

Device type in compiler settings needs "-mcpu="

2008-08-08T17:24:32Z

Hello,
In the C/C++ Build Settings, under Tool Settings -> Compiler -> General, I need to add the string -mcpu=my_device for the pic30-gcc compiler to correctly understand my processor choice. Otherwise the pic30 compiler throws the error:

#error "Include file does not match processor setting" p24FJ128GA010.h

It would make sense for this string to be automatically added by the Eclipse C30make plugin.

The command line arguments executed without the -mcpu= option are:
> pic30-gcc.exe 24FJ128GA010 -g -c -Wall -O0 -I"C:\Program Files\Microchip\MPLAB C30\include"

With the -mcpu= added it becomes:
> pic30-gcc.exe -mcpu=24FJ128GA010 -g -c -Wall -O0 -I"C:\Program Files\Microchip\MPLAB C30\include"

I am using Eclipse v3.4.0 and C30make Plugin v0.1.0. Note, that I have only tested this with device 24FJ128GA010 but assume that other devices will have the same issue.

Regards,
dvase

HowTo use in Eclipse 3.3.1.1

2008-03-14T06:14:33Z

Can I use this PlugIn in the newes Eclipse 3.3.1.1?

In Project >> Properties >> C/C++ Build >> Setting

There is no Tab-Sheet "Tool-Settings" and the other are not avaiable, too.

Can you update this Eclipse-Plugin?

Build configuration settings issue

2007-06-19T22:59:58Z

Hello,
I think that the "Linker script" input field in the "Configuration Settings" portion of the "C/C++ Build" section of the Project properties should automatically encapsulate the input with parentheses. Currently, a user has to manually place parentheses into the field for the linker to accept folder locations with spaces.

Regards,
Dustin