26-11-2005 12:46

coastertux

Re: White Paper Discuss: Eclipse for Robotics

I followed your instructuons but when I went to start a new project, the Microchip option was not on the dropdown for Project Type.

26-11-2005 18:02

Rickertsen2

Re: White Paper Discuss: Eclipse for Robotics

Props. now if only i could get eclipse to open without crashing my system. I'm using Fedora 4 x86_64. Any ideas?

27-11-2005 16:32

prograid

Re: White Paper Discuss: Eclipse for Robotics

Please read this!

The plugin posted with the whitepaper will not work. It' the wrong version.

Use the attached jar file instead. (Just change the zip extension to jar.)

Sorry.

Does anyone know if there is a way for me to edit the whitepaper?
Thanks

30-11-2005 17:56

Astronouth7303

Re: White Paper Discuss: Eclipse for Robotics

Even after I downloaded the updated file, it still doesn't work for me.

I look at the "Plug-in Details" dialog from the About dialog, and the Plug-in IDs go straight from "org.eclipse.cdt.managedbuilder.ui" to "org.eclipse.cdt.refactoring".

Extracting it into a folder doesn't help. (The dir has since been removed.)

Eclipse:
Version: 3.1.0
Build id: I20050627-1435

The only error in the error log I can find is this:

!ENTRY org.eclipse.update.configurator 2005-11-30 17:45:06.320
!MESSAGE Could not install bundle plugins/org.eclipse.cdt.mcc18.toolchain_1.2.0/   Bundle "org.eclipse.cdt.mcc18.toolchain" version "1.2.0" has already been installed from: update@plugins/org.eclipse.cdt.mcc18.toolchain_1.2.0.jar

org.eclipse.cdt.mcc18.toolchain (1.2.0) "Microchip C18 Compiler Tool Suite Managed Make Extension" [Installed]

  file:/d:/Program Files/Eclipse/plugins/org.eclipse.cdt.mcc18.toolchain_1.2.0.jar

01-12-2005 19:11

prograid

Re: White Paper Discuss: Eclipse for Robotics

Quote:

Originally Posted by Astronouth7303 Even after I downloaded the updated file, it still doesn't work for me. I look at the "Plug-in Details" dialog from the About dialog, and the Plug-in IDs go straight from "org.eclipse.cdt.managedbuilder.ui" to "org.eclipse.cdt.refactoring". Extracting it into a folder doesn't help. (The dir has since been removed.) Eclipse: Version: 3.1.0 Build id: I20050627-1435 The only error in the error log I can find is this: Code: !ENTRY org.eclipse.update.configurator 2005-11-30 17:45:06.320 !MESSAGE Could not install bundle plugins/org.eclipse.cdt.mcc18.toolchain_1.2.0/ Bundle "org.eclipse.cdt.mcc18.toolchain" version "1.2.0" has already been installed from: update@plugins/org.eclipse.cdt.mcc18.toolchain_1.2.0.jar In the configuration details, I see: Code: org.eclipse.cdt.mcc18.toolchain (1.2.0) "Microchip C18 Compiler Tool Suite Managed Make Extension" [Installed] Code: file:/d:/Program Files/Eclipse/plugins/org.eclipse.cdt.mcc18.toolchain_1.2.0.jar What the heck is going on?

01-12-2005 19:16

Astronouth7303

Re: White Paper Discuss: Eclipse for Robotics

01-12-2005 19:22

Astronouth7303

Bug: Include paths wrong

Ok, new bug.

You don't use the enviroment variable MCC_INCLUDE. You appear to hard-code C:/mcc18/h. (A false assumption; I have mine installed to D:mcc18h)

I also can't find an option to change it.

01-12-2005 22:55

prograid

Re: Bug: Include paths wrong

03-12-2005 17:00

Astronouth7303

Re: White Paper Discuss: Eclipse for Robotics

I've now discovered something else.

If you use the MinGW make, it will mung the command, so that it calls:

mplink ..18F8520user.lkr w:/ m:/ FRCMapfile.map D:/msys/1.0/odefault_2005.hex ./ifi_startup.o ./ifi_utilities.o ./main.o ./printf_lib.o ./user_SerialDrv.o ./user_routines.o ./user_routines_fast.o /lD:/mcc18/lib ..FRC_Library.lib

06-12-2005 21:50

prograid

Re: White Paper Discuss: Eclipse for Robotics

mplink ..18F8520user.lkr w:/ m:/ FRCMapfile.map D:/msys/1.0/odefault_2005.hex ./ifi_startup.o ./ifi_utilities.o ./main.o ./printf_lib.o ./user_SerialDrv.o ./user_routines.o ./user_routines_fast.o /lD:/mcc18/lib ..FRC_Library.lib

mplink "..18F8520user.lkr" /a INHX32 /w /m FRCMapfile.map /oRoboticsCode.hex  ./254_arm.o ./254_drive.o ./254_encoder.o ./254_gyro.o ./254_interrupts.o ./254_timers.o ./254_utilities.o ./eeprom.o ./ifi_startup.o ./ifi_utilities.o ./main.o ./user_SerialDrv.o ./user_camera.o ./user_routines.o ./user_routines_fast.o   /l"C:mcc18lib" "..FRC_Library.lib"

06-12-2005 22:06

Astronouth7303

Re: White Paper Discuss: Eclipse for Robotics

mplink "..18F8520user.lkr" /a INHX32 /w /m FRCMapfile.map /oRoboticsCode.hex  ./254_arm.o ./254_drive.o ./254_encoder.o ./254_gyro.o ./254_interrupts.o ./254_timers.o ./254_utilities.o ./eeprom.o ./ifi_startup.o ./ifi_utilities.o ./main.o ./user_SerialDrv.o ./user_camera.o ./user_routines.o ./user_routines_fast.o   /l"C:mcc18lib" "..FRC_Library.lib"

31-12-2005 14:34

EricS-Team180

Re: White Paper Discuss: Eclipse for Robotics

31-12-2005 14:56

Astronouth7303

Re: White Paper Discuss: Eclipse for Robotics

02-01-2006 17:00

EricS-Team180

Re: White Paper Discuss: Eclipse for Robotics

05-01-2006 22:14

EricS-Team180

Re: White Paper Discuss: Eclipse for Robotics

10-01-2006 10:29

MikeN

Re: White Paper Discuss: Eclipse for Robotics

Hello all

I have been using MPLAB for a while, and was already using eclipse, so the chance to junk MPLAB was eagerly taken!

I have Windows XP, with eclipse 3.1.1 with CDT_SDK 3.0.1. I installed minGW (via the MSYS install), set up my paths and off we went.

I have had a number of problems, some soleved, some went away, one remaining, as below

1. Flags for error level is incorrect -nw=x - should be -w=x. Sorted by editing the .xml file (after unzipping from .jar file)
2. I wanted to specify the large memory model, so again modified the xml.
3. The del /f command doesn't work - it is built in in win32 not a stand alone command. The cleanCommand doesn't seem to be acted upon, so (temporarily) I copied minGW rm.exe to del.exe and that works. Makes no difference, as eclipse clears the build directory prior to doing a make clean (via project/clean), but it works.
4. The minGW make seems to do something odd - the linker tries to read the a:/ drive and can't, giving an error. Again temporarily I tried a make from gnuWIN, and that seems to do what is expected.
5. The default library FRC_Library.lib which I don't use would not go away when deleted from the project properties so I removed that from the xml file as well. Also the unneeded -D_FRC_BOARD flag for the compiler.

I had some problems which have gone away - principally the linker looking in the wrong place for the object files. The compiler was putting them in the build directory, the linker looked in the source directory. This has gone away - I didn't do anything obvious.

6. Finally the one thats left (may be a feature!). There is no dependency checking done. If I modify a header file, the relevant object are not rebuild. Is this expected?

I will post my modified xml file if its of interest, when I have had a bit longer to go over it.

I welcome any comments on any aspect of the above

Regards Mike Newsome

10-01-2006 15:38

Astronouth7303

Re: White Paper Discuss: Eclipse for Robotics

Most of the mods you've described I've also done. (The only thing missing is ASM compilation.) Basically, I've added complete compilation options. (Within limits of the system.) (I've also made a generic makefile. It compiles all your c & asm files and links them together. Not quite ready to release it, though.)

As far as Make goes, that's the nature of the MinGW make. It interprets /w et al as w:. I'm pretty sure that the linker will accept -w style flags, but I know for sure mpasm won't. Cygwin won't do this, but interprets as an escape character.

I wasn't able to fine Make on the gnuWin website; maybe you could link us?

11-01-2006 08:06

MikeN

Re: White Paper Discuss: Eclipse for Robotics