Hi Fabien,
After a bit more research I have found that the following appears to work:
__code __at __CONFIG1L _C1L = 0x20;
__code __at __CONFIG1H _C1H = 0x04;
__code __at __CONFIG2L _C2L = 0x04 & 0x01;
__code __at __CONFIG2H _C2H = 0x0C;
__code __at __CONFIG3L _C3L = 0x30 & 0x40;
__code __at __CON
Fabien,
It seems that the 18f4550 has the CONFIG_1L, CONFIG_1H .. etc.
address macros defined, but in the pic18fxxJxx series, they are not
defined in the processor include file. These can be added by hand, not a
problem, but I've tried a manual approach using the datasheet address
without r
Hi,
Here is how I do the job for a pic18f4550 using the
device specs to know the hex values of the config
bits:
#ifndef CONFIG_H_INCLUDED
# define CONFIG_H_INCLUDED
# define CONFIG(k, n) code static char at __ ## k _ ## k = n
/* bits value meaning
5 0 clock comes from the primary osc block, no
Hi, I've also been unable to find where these constants are defined, but
I think this issue is related to gputils, it seems they are only defined
for previous pic18 devices, I've use to program a 18F8722 that way and
worked, the macros where defined in the .h file of the processor, but
now, usi
