Problems linking object files - .cof and .hex not created

[Ed King]

Hi all,

I am hoping someone can help me with this problem, as support through CCS is slow in arriving and being in the UK doesn't help matters.

I have been wrestling with some object files that I received from Bolymin for use with an embedded display of theirs. The story is long, but I now believe I have the correct CCS compiler for the job - suffice to say, I fell into the legendary "multiple compilation unit" trap. What a pile of crap. Anywho, I have the following files that I want to compile and link:

ddu.c (provides main())
config.h (provides 24FJ64GA004.h for the Bolymin display I'm using)
uart.h (provides a list of UART function prototypes)
uart.o (the object file that provides the UART functions)
SSD3103.h (provides a list of display function prototypes)
SSD3103.o (the object file that provides the display functions)

Now, all I would like to do is compile and build this. I am using PCDIDE (which I think might just be the PCW IDE with the PCD compiler?) and MPLAB ICD-2 to debug.

Enabling "Multiple Compilation Units" and "Link Separately" in the project options means that I can compile the source without error. However, the .cof and .hex files are not being created in this process, which suggests a linking problem. If I remove the function calls in main() that invoke the library functions in uart.o or SSD3103.o and recompile, the project compiles and links properly - I can see all the output files. So I'm taking a semi-educated punt that the object files (which I know from Bolymin were compiled using PCD) are causing the problem.

I would be very grateful if someone could shed some light on this problem?

[jds-pic]

[Ed King]

I have version 4.114 of the IDE and PCD.

I have since been informed by Bolymin that version 4.104 has known problems with linking objects (and so I might assume that a later version may have this problem too), whereas version 4.093 is workable? Does anyone know if this is true?