using/compiling multiple files

[cerr]

Hi There,

I would like to break up my huge source file into multiple files. I cut all the ISRs out of my main file (MCU2.c) and pasted them into a new file (interrupts.c). I added that to my MPLAB project as a source file. However, can't compile the project, am getting following errors:
Executing: "C:\Program files\Picc\CCSC.exe" +FH LINK="MCU2.hex=MCU2.o,interrupts.o" +DF +LN +T +A +M +Z +Y=9 +EA #__18F87K22=TRUE
*** Error 146 "MCU2.c" Line 1(0,1): Import error dyn mem mis-match true!=false
*** Error 146 "MCU2.c" Line 1(0,1): Import error
2 Errors, 0 Warnings.
Skipping link step. Not all sources built successfully.
BUILD FAILED: Mon Mar 28 10:52:24 2011
The first line in MCU2.c looks like this:

[cerr]

I thought I got it resolved with this http://www.ccsinfo.com/forum/viewtopic.php?t=34046 but it apparently still isn't working.
If I add another source file under Other files it's all good and it compiles until I declare the function(s) in it in my main header.
Imagine I created a file test.c:

[PCM programmer]

Here are some more threads on using multiple files in MPLAB:
http://www.ccsinfo.com/forum/viewtopic.php?t=18649&start=1
http://www.ccsinfo.com/forum/viewtopic.php?t=27115

[cerr]

[PCM programmer]

CCS does have something called "multiple compilation units".
See this FAQ:
http://www.ccsinfo.com/faq.php?page=multi_comp_units

But that feature only comes with the "full IDE" version of CCS.
I only buy the individual "command line" versions of the compiler.
So I can't help with multiple compilation units. I only know how to
do the "everything is an #include file" method.

[cerr]

[calvin]

In my case, the "Import error dyn mem mis-match true!=false" is when I use "malloc" in my code. if I comment the line with malloc instruction and comment #include <stdlibm.h> works fine.
On the other hand I get few errors when use Multiple complilation units as:
-.CCS shows "File can not be opened for write" with any reason. I have to close CCS, start CCS again and works.
-. The progress bars of RAM and ROM are crazy. shows 100% in ROM (sure, my memory really is not full)
-. Fews errors when I toogle a BookMark and edit the code. May be when a BookMark is located after may code when I delete some files.

Well, I try to help to improve the compiler.

On the other hand, My idea when I try the "Multiple compilation units",was try to locate a code allways in the same directions but Multiple compilation units no works, how can I do to do that? thanks a lot.

I have CCS 4.114

[PCM programmer]

[calvin]

Thanks for your answer.

Yes, the same address.

I'm trying to do the following:
-. My full code is divided in two parts. One part change frequently. The other part never changes. Like a BootLoader.
-. I locate the second part at bottom of program memory.
-. I use the second part in few microcontrollers
-. When I change the first part, the compilation of the second part is affected and the generated ASM code is no the same between compilations. Remember the second part of my code never changes.

I use the following code to trying to locate my second part of my code and his variables allways in the same address between compilations:
----
addressmod (loader_ram_block,,,START_RAM_ADDR,END_RAM);
#TYPE default=loader_ram_block
#ORG START_ADDR+3, END_ADDR auto=0 default
.
.
.
---

I think the solution of my problem may be possible if:
-. I will able to compile the second part of my code in an separate ".o" file
-. Import the ".o" file of my second part of code to the first part.
-. Compile the first and ".o" and generate the HEX file.
(but I have problems with "multiple units")

I think that in this way I allways have the same ASM of my second part.

An other alternative may be add some directive that allways compile the second part in the same way without changes.

but... I don't know how do that.

Thanks a lot for your advice.

Regards,

Carlos

[calvin]

And... how can I do to locate all the SCRATCH variables generated by the compiler in an specific location?

I can locate the variables declarated in my functions like: int XX; char FF[20], etc. using:

addressmod(ram_block,,,START_RAM_ADDR,END_RAM);
#TYPE default=ram_block

But how can I do the same thing with the SCRATCH variables?

Thanks again for your help.

[PCM programmer]

This thread talks about the issue:
http://www.ccsinfo.com/forum/viewtopic.php?t=27996

[calvin]

Thanks PCM, do you have some advice about my others situations? and some for "Import error dyn mem mis-match true!=false"?

Thanks

[PCM programmer]

I don't have the full IDE version of the CCS compiler, so I can't test
problems with Multiple Compilation Units. I have the command line
compilers that integrate with MPLAB. They don't support "MCUs".

[calvin]

Thanks a lot PCM!

[arnadan]

Very old post but still no solution! So I had to find a solution by myself and want to share it here:

Include the following line in all of your *.C files (respectively in the common project.h file that I include in every *.C file):

#USE DYNAMIC_MEMORY

After that you will get some "Variable never used: __DYNAMIC_HEAD" warnings but the code compiles, links and executes.