View previous topic :: View next topic |
Author |
Message |
Andreas
Joined: 25 Oct 2004 Posts: 136
|
Using MPLABX with CCS compiler |
Posted: Sat Apr 09, 2016 2:38 am |
|
|
Hello Friends
I am working now since about 2 years with the MPLABX so far not so bad.....
But i still have one annoying problem.
On some statements I always get the warning in the Editor that it can't resolve this identifier.
I tried several ways with defines but it didn't work out.
No as example:
OldCounterVal = ccp_1; whats wrong with ccp_1 ????
After compiling no Errors !!!!
Any idea or solution ??
best regards
Andreas |
|
|
temtronic
Joined: 01 Jul 2010 Posts: 9221 Location: Greensville,Ontario
|
|
Posted: Sat Apr 09, 2016 4:59 am |
|
|
Warnings, as you've found out will not stop a good compiling rather they are 'something' that 'looks' odd to the compiler.
In CCS C compilers you can disable/not display any warnings or ignore individual warnings. I don't know if X can do that being a dinosaur I'm still using PCM4vxxx through MPLAB 8v86! Heck they work, no need to upgrade as I have ODS (Old Dog Syndrome).
Jay |
|
|
jeremiah
Joined: 20 Jul 2010 Posts: 1345
|
|
Posted: Sat Apr 09, 2016 1:43 pm |
|
|
mplabx's editor has gotten better, but it still has this problem in some scenarios.
How are you defining CCP_1? Can you post that line or lines? |
|
|
Ttelmah
Joined: 11 Mar 2010 Posts: 19496
|
|
Posted: Sat Apr 09, 2016 1:58 pm |
|
|
CCP_1 is defined for you on the current compilers.
In the header file. It's a #word definition placed at the location of the low byte register, which is itself defined using getenv.
I do remember having a problem on the odd occasions that I have had to use MPLAB-X, with it not wanting to resolve CCS #word declarations. I'd try explicitly generating an int16 variable (perhaps CCP1), and explicitly locating this at the same location. So:
Code: |
int16 CCP1;
#byte CCP1=CCP_1
|
Then try talking to CCP1 instead. |
|
|
|