oasisgod wrote:
> Hi I'm fairly new to pics and I'm up against a wall here. When I
> program my
> pick (icprog) with the below code the verify will fail.

So that sounds like the first thing to chase down.  What does this have to
do with your source code?

> Yet I have no
> problem with a bunch of code i downloaded off the net and other
> projects
> that i did durring the summer. So I'm led to believe its my code that
> is
> causing the failure even though it is compiling in MPASWIN with out
> errors.

How about warnings?  You must have gotten a bunch with opcodes starting in
column 1 like that.

> The code is intended to

If you can't program the HEX file into the PIC, then I don't see how it
matters what the code is intended to do.

> Any help woul be very appreciated, thank you in advance

> LIST p=16F628 ;tell assembler what chip we are using
> include "P16F628.inc" ;include the defaults for the chip
>     ...

Yucc.  You should be ashamed to post such a mess.  Some opcodes start in
column 1, fields aren't lined up in columns to be easy to read, and there
are virtually no comments.  No thanks.

Note that none of these things has anything to do with the content of the
code, which would make them excusable for someone new to PICs.  Basic
neatness and proper formatting of work you want others to look at are
universal concepts that trancend PICs and even programming.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist