Yes, that is the concept. For example, I noticed that the 18Fxx60 line
and it's friends have an XINST bit in the config words, so the presence
of that bit in the config word definitions will probably be sufficient
for some things.

I don't use many different PIC families, so it isn't a huge deal to deal
with things based on the actual processor (e.g test for
18F252/452/2620/4620), but being able to test for FAMILIES rather than
processors would be useful.
--=20
Larry Bradley =20
Orleans (Ottawa) Canada=20

On Thu, 2013-11-14 at 02:02 +0000, Sergey Dryga wrote:

> Larry Bradley <larry.bradley <at> ncf.ca> writes:
>=20
> >=20
> > Or perhaps there is some way at compile time (given the various chip
> > definition fines) of determining the "family" of chip.
> > I can do this with the A/D converter, by seeing if ADCON2 is defined,
> > for example).
>=20
> The XC compiler include files define versions of, at least some, perifera=
ls. =20
> The XC8 has include file <flash.h> which defines FLASH_V1_1 through
> FLASH_V1_6 with corresponding sizes of write and erase blocks. =20
>=20
> Is this what you are looking for? =20
>=20
> Sergey Dryga
> http://beaglerobotics.com
>=20
>=20
>=20
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.