Josh Green wrote:
> I'm having some issues in porting my project from a 16F84A to work with
> a 16F88.
>
> ...
>
> The only things on the 16F84A that I use are:
> PORTA/B
> Timer0

Then why not the cheaper 16F648A instead of the 16F88?

> Has anyone got any ideas of things that I may have missed in the
> differences between the 88 and 84A?

The usual suspects:

1 - Used CBLOCK and absolute mode to define variables.  Don't do that.  This
is one good reason why.

2 - Code doesn't check for existence of analog peripherals and initializes
them to disabled.  Always do this.  Since it's done with assembly time
checks, it results in no additional code on a PIC without an analog
peripheral.  If you do want to use an analog peripheral, you set it up and
enable it as desired later in the module that handles that peripheral.

3 - Bad banking, like manually setting RP0 and RP1 instead of letting the
assembler figure out the right bank.  Don't do that.  This is one good
reason why.

Unfortunately most free code out there exhibits all these bad programming
practises.  Remeber, any bozo can put up a web page, and too many do.


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist