> Has your development environment been used for the 16F630/676 chips ? I
> have a project coming up where the 630 would be an ideal chip.

Nope, I've never used those chips, so they aren't known to the development
environment.

However, adding a new chip is easy.  If it's just a slightly different mix
of the same peripherals with the same instruction set, then it only takes
two steps:

1  -  Add the appropriate block for the chip to STD_DEF.INS.ASPIC.  It
should be fairly obvious what to do by looking at similar chips.

2  -  Create the .LINKPIC file for the chip.  Again, this is usually just
a cut and paste from a similar chip.

If the chip has a peripheral that needs different initialization at power
up (like the A/D in the 18F1320, very different from the 18Fxx2), then
appropriate code needs to be added to QQQ_PORT.ASPIC.  A different UART,
for example, may require different code in the UART_xxx macros.

In any case, the new code should be added in a way that is backward
compatible, and preferably not by checking the individual processor type
(whole processor families is fine when the feature is directly tied to the
family).  Microchip will probably use a new peripheral in additional
chips, and I don't want to the maintenence headache of trying to keep up
with them.  The best way is to do an IFDEF on a symbol that is unique to
that version of the peripheral.  You can see examples of this in the A/D
initialization section of QQQ_PORT.ASPIC.  The various IFDEFs
automatically select the code for the A/D type in use on that chip.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.