MPLab color selections define red as "bad."


When I enter a list directive as 16lf1783, it is tagged as "bad."


There is no error, warning, or other related message when the Assembly code is compiled. The color code is not sensitive to case. If I change the processor to 16f1783, the color returns to normal, but the assembler gives a warning about processor mismatch. The 16lf1783 is supported by MPLab 8.92.

Why is the processor tagged as "bad" in the list directive? Is there a way around that? What does MPLabX do when using Assembly?

John

 

As long as the code compiles without error don't worry about it. The IDE does do some strange things sometimes. Try using MPLAB-X instead.

 

Hola John,

I recall a maybe similar problem long time ago. Doing copy-paste in a new project, made those errors to vanish.

In the past, a missing EOF, created havoc in some versions.

 

I hadn't tried cut and paste. That does make the red disappear, as do deleting the el, putting a space, and a lot of other things. But on assembling, you get warning #215 about processor superseded by the command line.

Then I tried with the "whole" name, PIC16LF1783 (no parentheses). It assembled, and there were no errors or warnings. It is surprising to me that for regular processors, the list directive "p=16fxxx "or "p=16f1xxx" work just fine, but for the low-voltage varieties, it appears one must enter "p=pic16lf1xxx" etc. Case does not make a difference, and one can enter "p=pic16fxxx" for the other processors too. As we know, the include has to have a "p" as in #include <p16lf1783.inc>, so I tried just "p" instead of "pic" for the list directive. That gave the same warning #215.

Now I can sleep.

John