Search found 12 matches

Still trying to use the PKoB4.
Regarding the LVP, do you mean I need to just set the LVP fuse in the code where I set other fuses?
Had also seen something about using #device icd=true
Do I need t ...

I've been using a Curiosity High Pin Count dev. board (PKoB4) with MPLAB X, but wondered if anyone is successful using it with CCS C IDE? Pointers on getting started?
Thanks.

So, it seems to me that 0x080h to 0x0FF is in the GPR range of Bank 0 whereas 0xF80 to 0xFFF are in bank 15, i.e. the SFR. From the data sheet "The Access Bank is comprised of the upper 128 byte ...

Apologies, it's legacy code that I'm still trying to understand myself. It's running on a 18C252.

From what I understand so far, they were reserving a ram location for rx/tx buffers. They were us ...

Updated from 5.075 to 5.115 and what used to be a warning is now an error, i.e. on the line

#RESERVE 0x0C0, 0x0C1, ...

I get:
>>> Warning 228 "C:\Users\...\def_file.h" Line 1 ...

How do rom pointers relate to the passing of string literals, constants, and PASS_STRINGS?

i.e. something like...
void some_function(rom char* string) {}
and the call...
some_function( (rom ch ...

So, would I use PASS_STRINGS as a global setting, e.g. at the beginning of main, or should it be used in a more narrow scope?

Have seen some of the old posts regarding:
#device ANSI
#device PASS_STRINGS=IN_RAM
but not sure if that is the solution.

Compiler version 5.115, PIC18F46K22
Having the hardest time understanding how to pass string literal constants to functions in CCS C compiler.
Originally had a function like this:
FUNCT(const ch ...

Hmm, idk.

I get the same compile error no matter whether a second c file is in projectName\Source Files or projectName\Header Files

Apologies, I'm trying to use MPLAB X. v6.05

@Ttelmah I think I follow what you're saying up until...
"Instead drag them into the Header Files tab. This then tells MPLAB, not to try to directl ...

Looking into the possibility of using CCS within MPLAB. I understand CCS compiler users typically just #include extra C files as is the case with the legacy code that I'm using. In trying this code ...