InterruptVectorLow error when we compile

Technical Programming
1

Anytime we try to compile our code, we get the following error:

MPLINK 3.90, Linker
Copyright © 2004 Microchip Technology Inc.
Error - section ‘InterruptVectorLow’ type is non-overlay and absolute but occurs in more than one input file.
Errors : 1

BUILD FAILED: Wed Feb 02 15:55:41 2005

What the devil does this mean, and how do we fix it?

2

I’m not exactly sure, but what did you change from the default code? I’m assuming you started from the default code v2.4 (the one that supports the camera). Try e-mailing Innovation First, becuase that sounds like a really low-level problem in one of those ugly header files.

3

Yeah, we started with the latest version of the default code. We’ve added accelerometer code (downloaded from Kevin Watson’s website), added relays, and modified the drive code a little. Taking out the accelerometer code didn’t help. Even taking out all our changes didn’t fix it. We’ll try e-mailing Innovation First, but in the mean time, does anyone else have any suggestions? Anyone else had the same problem?

4

You have somehow added two copies of the file user_routines_fast.c to your project. The error you’re getting means you’re attempting to define InterruptVectorLow twice.

In MPLAB look at the project file list (the window labeled “FrcCode.mcw”) to see if you have the “user_routines_fast.c” file listed twice.

You can also do a search (Project -> Find in Project Files…) for InterruptVectorLow to see all the places it’s getting declared.

5

I checked… only one copy of user_routines_fast.c
Also, after checking every file in the workspace, I only found InterruptVectorLow declared in ONE place, where it’s supposed to be in user_routines_fast.c

I re-downloaded the default code, copy/pasted all the changes we’d made into the new copy of the default EXACTLY as they were in our previous code, and it magically compiles now.

6

We get that error whenever we first compile a project in a new folder. I don’t know what the cause is, but the solution is to do a Ctrl-F10 “full build” of the project. Thereafter, a regular F10 “make” works fine.