Installing PCM and PCH in separate directories

[guest]

tried it ... still no luck. :-(

Do I perhaps need to have a linker (*.lkr) script?

I am not very familiar with linkers.

[Mark]

No linker script. Did you restart MPLAB after you made the changes?

[guest]

Yepp, every time.

No need to reboot though or is there?

[Mark]

You probably didn't get a unique GUID for one of the tools and it is using the wrong INI or mtc file. Delete the registry entries that you made and then make the following into "addtool.reg" file

[guest]

1. I backed up and then removed my two registry keys (the ones I had added originally with incremental key names similar but not the same as the orginal tlccs.in). All other names (tools, etc) had incremental names as well so I am pretty sure there were no duplicates. I had duplicates originally when I played with it which messed things up in MPLAB ;-)

2. I then added your new keys as per your latest post

3. rebooted and restarted MPLAB.

==> Unfortunately still no joy, exactly the same 'result' as before

what setup do you have to make it work?
btw I am really appreciating the time you put in to help.

[Mark]

I made a goof in one thing I told you

[guest]

Hi Mark,

I tried out COF instead of COFF: no change

I then created the new files test.mtc and test.ini and put them in the C:\Program Files\Microchip\Third Party\MTC Suites directory.

Next I added yor new 'test' keys to the registry.

Now I only have 2 CCS tool suites:

- the original 'CCS C Compiler for PIC12/14/16/18'
- the latest new 'Test for CCS C Compiler'

(the 'other' CCS compiler key was overwritten earlier and is now absent. I don't think this matters though - correct me if I am wrong.)

I rebooted to make the registry entries active and then restarted MPLAB, set the new language suite to 'Test for CCS C Compiler' and chose the correct exe/bat files for the 'Test for CCS C' and 'MPLINK' respectivily.

Tried a compile and ... still the same results as before. :-(

1. Is it worth reinstalling MPLAB, or downgrade to 7.00 from 7.01?

2. Do I need to clean the registry if MPLAB leaves anything behind after an uninstall?

3. Do I need to tick any boxes within the Build option, Project, MPLINK tab e.g. map file etc. ?

[drolleman]

i have installed and working 2 diffrent versions of ccs pch 3.221 and pcm 2.184. this is how i set it up

installed pcm into d:\pic16

installed pch into d:\pic18

installed the latest mplab 7.01

ccs's mplab plugin

when i compile a project with pcm (the previos build was with pch) it will notice a previous change and will ask witch compiler i would like to use pcm or pch

[guest]

Hi drolleman,

Thanks for your input.

I am trying to run two different versions of PCH from within MPLAB, one production version and one up-to-date version.

That's why Mark's approach is a great and neat way of achieving this. I just wish I knew why it is not working on my machine.

Maybe you and/or someone else can give Mark's method a try and report back to this thread.

Thanks

[Mark]

[Mark]

I guess one other thing comes to mind. Does it create the main.hex, main.cod or main.cof files?

[guest]

Mark, from your post: "Don't know why your other ones are gone." (referring to the CCS registy key)

Sorry, they weren't actually gone, just not loaded as I had changed the DoNotLoad value from 0 to 1 (in the registry) to stop them appear in the toolsuite select box in MPLAB.

After playing with it a bit more I have now done a clean reinstall of MPLAB 7.01. As per your post I have then added test.ini, test.mtc and added the corresponding key to the registry.

However still no luck...

On the posiive side it does generate main.hex plus either the main.cos (default) or main.cof (using the +DF command line paramter) .

I can then import the hex file into MPLAB and program the chip with my ICD2 from within MPLAB.

To summarise, it compiles fine, just isn't telling MPLAB about the newly generated hex file. Soooo close ;-)

In the test .ini file I have played with various settings like debug=COD;COF, debug=COD, debug=COF or debug=<empty>

This does not appear to make any difference...

[Mark]

Try and watch the Popup compile window and the Build Tab at the same time. The Popup should disappear before the dummy.bat file is called. See if you can determine if this is correct. I had a problem with really old (version2.7XX) versions that immediately return after calling them. Since the compiling was still continuing the process would fail since there was no output. So I am thinking that if MPLAB thinks the compile process is complete but the COF or COD file is not written yet, you might get what you are seeing.

[guest]

Your explanation makes sense, though I don't think it is the problem I am seeing:

I removed the command line parameter +p so that the compile popup window would close straight away and it looks to me as if this compile window closes followed by dummy.bat starting. It's fast changing but that's my impression.

Which version of pch do you use?

[Mark]

The latest I have is 3.217.