View previous topic :: View next topic |
Author |
Message |
sureshcbdazzler
Joined: 13 Feb 2012 Posts: 2
|
how use ccs compiler |
Posted: Fri Jan 18, 2013 10:28 pm |
|
|
How to use CCS compilers with mplabx? _________________ sureshkumar |
|
|
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
|
tinley
Joined: 09 May 2006 Posts: 67
|
Errors do not highlight in edit window? |
Posted: Wed Feb 12, 2014 6:26 am |
|
|
Is it true that the errors shown in a failed build in the output window of MPLABX (V2.0) cannot then be highlighted in the edit window like they can in the CCS IDE?
Sorry if this issue has been raised before as I can't understand why not!
I must be doing several things wrong as the only way I find the CCS compiler V5.017 workable with MPLABX is to use the CCS IDE and the MPLAB IPE (with PicKit3) for programming, but this is a bit 'clunky' and I don't have the option of debug using it this way. I have tried using the Debug within the CCS compiler and it crashes the IDE on almost every other build, so time wasting and not good at all. Similar bugs have prevented me using CCS/MPLABX as intended over various versions of each since install 6 months ago!
Please point out what I must be doing wrong??? |
|
|
jeremiah
Joined: 20 Jul 2010 Posts: 1354
|
|
Posted: Wed Feb 12, 2014 7:52 am |
|
|
I haven't used a more recent version of mplabx (I think I am 1.60 or 1.70) and when I did it was with a version 4.1xx compiler, but it showed errors that gave me url like links to jump to errors back then. I think there was an IDE setting that affected it.
Either way, it is easy to test out. MPLABX is free.
EDIT:
Here is an old screenshot from version 1.40 that I posted in another thread. For future reference, all I did was a forum search on mplabx and found a bunch of threads with lots of info on it.
http://i.imgur.com/cs1In.jpg |
|
|
tinley
Joined: 09 May 2006 Posts: 67
|
|
Posted: Thu Feb 13, 2014 8:34 am |
|
|
Thanks for that.
For some reason MPLABX V2.0 does not want to display the .err file that is being created. This is either a fault or an option in MPLABX, but I can't find reference of how to display the .err file. I would imagine this was the default action, whichever compiler is being used.
Maybe an entry in the MPLABX makefile??? |
|
|
alan
Joined: 12 Nov 2012 Posts: 357 Location: South Africa
|
|
Posted: Thu Feb 13, 2014 10:32 am |
|
|
Just installed 5.019 and errors are working in MPLAB X 2.0. Seems that CCS fixed it between 5.017 and 5.019.
Regards |
|
|
jeremiah
Joined: 20 Jul 2010 Posts: 1354
|
|
Posted: Thu Feb 13, 2014 11:29 am |
|
|
tinley wrote: | Thanks for that.
For some reason MPLABX V2.0 does not want to display the .err file that is being created. This is either a fault or an option in MPLABX, but I can't find reference of how to display the .err file. I would imagine this was the default action, whichever compiler is being used.
Maybe an entry in the MPLABX makefile??? |
I usually go to the "Files" pane and go down the directory path tree to the .err file. |
|
|
tinley
Joined: 09 May 2006 Posts: 67
|
|
Posted: Fri Feb 14, 2014 3:44 am |
|
|
alan wrote: | Just installed 5.019 and errors are working in MPLAB X 2.0. Seems that CCS fixed it between 5.017 and 5.019.
Regards |
Just updated to 5.019 and it works. I was blaming MPLABX. The .err files now have a full path to the warnings and errors. Maybe this was just corrected by re-installing CCS after updating MPLABX or maybe it was a bug in CCS 5.017.
Thank you to both of you for helping me sort this out. |
|
|
Ttelmah
Joined: 11 Mar 2010 Posts: 19538
|
|
Posted: Fri Feb 14, 2014 4:12 am |
|
|
Suspicion it may be 5.017. The way that CCS versions have a habit of making things go wrong is why the trend to their 'auto updater' has me 'squirming'. Fortunately you can still stick with manual updates....
MpLab-X has it's own problems though. If you don't need a chip that only it supports, 8.92, is still the more reliable emulator/IDE. I have both (separate machines, -X has a habit of breaking the older environment), and still wish they could get it to work as well as the older system...
I have 5.016, and 5.018, didn't bother with 5.017.
I wonder if the problem is:
"5.018 A problem with the encoding on an inline assembly MAC or MSC instruction is fixed", since MPLAB looks at the assembler generated. I've been having a problem with 'invalid instruction' errors on some processors importing debug info into MPLAB-X, so might be the same one....
Best Wishes |
|
|
ckielstra
Joined: 18 Mar 2004 Posts: 3680 Location: The Netherlands
|
|
Posted: Fri Feb 14, 2014 4:16 am |
|
|
From the CCS list of changes: Quote: | 5.018 Updates made for the latest MPLAB version |
|
|
|
|