MPLAB-X CCS and PIC10F320

viki2000 · Joined: 08 May 2013 Posts: 233

MPLAB-X tested: ver. 1.7 and ver. 1.8
CCS C Compiler ver. 4.140

Here is not a question about the programming of PIC. It is a question about configuration of the MPLAB-X with CCS compiler when is invoked or maybe a bug in MPLAB-X.

I tried with 3 PICs: PIC10F200, PIC10F320 and PIC16F88.
I need to work with all of them, one PIC on different project.

For test purpose the program to be built is simple:
For PIC16F88:

viki2000 · Joined: 08 May 2013 Posts: 233

I found a workaround.

Instead of choosing PIC10F320 in the beginning, I choose any Mid Range PIC (as PIC1688 for instance) which requires PCM version compiler of CCS C Compiler. As result, MPLAB-X is set to invoke the CCS C Compiler with +FM.

Then in C source file I just write #include <10F320.h> in the beginning and the compiler gives no more errors when I build the project.
But I never tried to burn the compilation into the PIC to see if I get a mismatch between PIC10F320 and the other Mid range chosen in the beginning, in case some other hidden settings are automatically done by MPLAB-X. That has to be tested.

As conclusion, at least for now, I consider that there is a bug in MPLAB-X. The person who designed the MPLAB-X regarding the integration of CCS C Compiler was probably thinking that every PIC10F is treated by CCS Compiler in the same way forgetting that PIC10F200…PIC10F206 is 12 bit instruction and is treated by PCB version of CCS C Compiler and PIC10F320/322 is 14 bit instruction treated by PCM version of CCS C Compiler.

I also have written to Microchip, I have now a waiting ticket for the present problem.
When I receive an official answer I will post it here also for others.

viki2000 · Joined: 08 May 2013 Posts: 233

I posted the same question on Microchip website forum:
http://www.microchip.com/forums/tm.aspx?tree=true&high=&m=723672&mpage=1#723672

And from I somebody received next answer:

"
It looks like the output added to the generated command line is driven by the device you select when creating the project.
When selecting Mid-Range 8-bit MCUs and PIC10F320, it automatically generates a command line with the +FB output flag, instead of the +FM you believe it should have.

You can add output flags by going to the File > Project Properties > CCS Compiler > Compiler Options.
But, it doesn't look like you can edit the generated command line.

Out of curiosity, see if it builds with the +FM output flag:

1. From your output window, copy the failing generated command line and replace +FB with +FM: "
"C:\PROGRA~1\PICC\CCSCON.exe" out="build/default/production" File2.c +FM +DF +Y=9 +EA +DF +LN +T +A +M +J +EA +Z -P #__10F320=TRUE

2. Launch a command shell, change to your project source code directory, copy and paste the above command line and run it.

If it builds successfully, at least you know that you were right about the +FM flag. It may be a bug you can report to Microchip. Unfortunately, I don't know of any workaround for this issue.
"

Out of curiosity I tested the recommend command prompt approach proposed above and works without giving any error.

viki2000 · Joined: 08 May 2013 Posts: 233

After submitting the problem to Microchip using a ticket, they changed the CCS plugin in MPLAB-X, by making a new version which solved the problem.

"
Problem Resolution:

Please note that a new version of CCS C Compiler plug-in is available. Please try downloading it and the issue should be resolved.

In order to update the plug-in please go to MPLAB X -> Tools -> Plugins -> Updates -> Reload Catalog and a CCS update should appear in the window...
"