I won't be able to do re-make and email the console log until just before the meeting, but:
-ADC code is in a separate folder under /Common/drivers/LPC/adc/ -there is something that I believe to be the "gcc BLA BLA BLA adc.c -o adc.o BLA BLA" you mention in the make output. -The .o file is being created with a timestamp concurrent with the makes that I have attempted. -My gut feeling at this point is that to get this error it must not be using the adc.o file, but I can't see why it wouldn't. On Tue, Jun 30, 2009 at 1:17 PM, Dave Camarillo <[email protected]>wrote: > Hi Jeremy, couple questions: > > -I'm assuming you have the ADC code in a separate source file, called > 'adc.c' > > -When doing a 'make', do you see something to the extent of "gcc BLA > BLA BLA adc.c -o adc.o BLA BLA" In particular, we want to make sure > that the corresponding ".o" file is being created. > > -When doing a 'make', toward the end, during linking (which is where > your error is coming from), do you see it referencing the "adc.o" > object file? If not, that would be the part of the problem. > > Can you send the full console output when running make? > > > thanks, > -dave > > > On Mon, Jun 29, 2009 at 4:59 PM, Jeremy Booth<[email protected]> wrote: > > When trying to compile some ADC bits and pieces, I get the following > error: > > > > main.o: In function `ADCtestTask': > > /home/user/freertos-5.1.2-lpc23xx/BlinkyLightSample/main.c:198: undefined > > reference to `configureADCPort' > > collect2: ld returned 1 exit status > > make: *** [BlinkyLightSample.elf] Error 1 > > > > I have a similar directory, include and makefile setup for the GPIO > stuff, > > and as far as I can tell they all match. The GPIO commands compile and > work > > just fine. > > This should show up in the latest commit to the 5.1.2Testing branch of > the > > LPC2368 code. > > > > > > Also, I could use a few pointers on getting that interworking thing set > up. > > If I read what Dave said earlier correctly, then I will have to recompile > > the GCC libs, but I could have that all munged up... > > > > -Jeremy > > > > _______________________________________________ > > psas-avionics mailing list > > [email protected] > > http://lists.psas.pdx.edu/mailman/listinfo/psas-avionics > > > > >
_______________________________________________ psas-avionics mailing list [email protected] http://lists.psas.pdx.edu/mailman/listinfo/psas-avionics
