CCS C Software and Maintenance Offers
FAQFAQ   FAQForum Help   FAQOfficial CCS Support   SearchSearch  RegisterRegister 

ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

CCS does not monitor this forum on a regular basis.

Please do not post bug reports on this forum. Send them to CCS Technical Support

PIC16F77 Strange Verification Error

 
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion
View previous topic :: View next topic  
Author Message
jkeggi



Joined: 28 Apr 2009
Posts: 2

View user's profile Send private message

PIC16F77 Strange Verification Error
PostPosted: Tue Apr 28, 2009 5:04 pm     Reply with quote

Hi,
I compiled code with MPASM tools, and loaded it to a PIC16F77 chip with ccsloader, and it ran perfectly.
I changed 1 constant and recompiled, loaded it, and get a "Verification Error" when I change the constant back to the original value, and recompile, it still gives the error when I attempt to load it.

I thought I might have gone through all the write life cycles of the Flash but when I switch chips, or load a different program I get the same error.

Basically wherever there should be an instruction, the memory shows '3FFF'.

Any help would be great, thanks.
PCM programmer



Joined: 06 Sep 2003
Posts: 21708

View user's profile Send private message

PostPosted: Tue Apr 28, 2009 10:02 pm     Reply with quote

Do you know for a fact that HEX files generated by MPASM will work with
CCSLOAD ? CCS compiler HEX files have a suffix on the end, which
MPASM hex files do not have. Example:
Quote:

;PIC16F877
;CRC=2357 CREATED="20-Apr-09 00:01"

Try adding the comment line for the PIC to the end of your HEX file.
The CRC line may not be needed.
jkeggi



Joined: 28 Apr 2009
Posts: 2

View user's profile Send private message

PostPosted: Wed Apr 29, 2009 8:19 am     Reply with quote

Quote:
Posted: Tue Apr 28, 2009 10:02 pm Post subject:
Do you know for a fact that HEX files generated by MPASM will work with
CCSLOAD ? CCS compiler HEX files have a suffix on the end, which
MPASM hex files do not have.


I've used a couple dozen different MPASM files on CCSLOADER before...

The issue turned out to be with a corrupt object file in the same directory as my hex file, building into a clean directory fixed everything.

Thanks for the help
Display posts from previous:   
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group