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 support@ccsinfo.com

Verification Failure on CCS Development Kit using ICD-U64

 
Post new topic   Reply to topic    CCS Forum Index -> CCS ICD / Mach X / Load-n-Go
View previous topic :: View next topic  
Author Message
mikehagans



Joined: 20 Jun 2007
Posts: 7
Location: Texas, USA

View user's profile Send private message

Verification Failure on CCS Development Kit using ICD-U64
PostPosted: Sun Dec 13, 2009 9:12 am     Reply with quote

Greetings smart people.
I bought the CCS Capacitive Touch Development Kit and upgraded PCW (now running 4.103) recently. I'm getting a verification error on the fuse programming even when trying the simplest sample programs (blinky LED) supplied for the demo board in the kit. The demo board uses a 16LF727.

I get the same result if I try to run the blinky led program from debug in PCW or if I compile it with PCW (no warnings or errors) and burn the hex file into the target using ccsload directly.

I'm hoping this is some newbie setup mistake on my part... something that I don't even know I don't know...

Here's the ridiculously simple code:
Code:

#include <16lf727.h>
#device ICD=TRUE
#fuses HS,NOWDT
#use delay(INTERNAL=8mhz)

#define GREEN_LED PIN_A1

void main()  {
   while (TRUE)  {
      output_low (GREEN_LED);
      delay_ms (1000);
      output_high (GREEN_LED);
      delay_ms (1000);
   }
}

Here's the error:



It looks like the actual and expected don't match on the second config byte, but neither seems to match the fuses I specified in the code snippet.

Please help a newbie out.

Humbly submitted,

Mike
Guest








PostPosted: Mon Dec 14, 2009 12:57 am     Reply with quote

Change HS ti INTRC_IO.
mikehagans



Joined: 20 Jun 2007
Posts: 7
Location: Texas, USA

View user's profile Send private message

PostPosted: Mon Dec 14, 2009 9:50 am     Reply with quote

Anonymous wrote:
Change HS ti INTRC_IO.




Thanks for replying, but this makes no difference. I still get exactly the same verification results error screen as in the original post. Neither the actual nor the expected fuses listed in the results match what I expected for the fuse settings. (For example, NOWDT in #fuses shows up as WDT in the verification results)


Sad
Mike
PCM programmer



Joined: 06 Sep 2003
Posts: 20559

View user's profile Send private message

PostPosted: Mon Dec 14, 2009 12:21 pm     Reply with quote

Quote:
The demo board uses a 16LF727.

Your problem is with Config Word #2.

In the 16LF727 data sheet, most of the bits in Config Word #2
are not used and default to 1's. The only available bits are the
VCAP bits. But there is a note that says:
Quote:

bit 5-4 VCAPEN<1:0>: Voltage Regulator Capacitor Enable bits
For the PIC16LF72X:
These bits are ignored.
All VCAP pin functions are disabled.

For the PIC16F72X:
00 =VCAP functionality is enabled on RA0
01 =VCAP functionality is enabled on RA5
10 =VCAP functionality is enabled on RA6
11 = All VCAP functions are disabled (not recommended)

So the VCAP bits probably read as 1's with the 16LF727, but there's no
guarantee that they do. I don't have the hardware so I can't verify it.
Your programmer claims it's reading 0x3FCF, which I suppose is possible.
That means it's reading the VCAP bits as 0's.

The problem is in the "Expected" result column. It expects 0000 and this
is clearly wrong, according to the data sheet. What could cause this ?
I think one cause could be that CCS has incorrect fuse data in the
devices4.dat file for the 16LF727. If you have the full IDE (PCW), then
you can use the Device Editor to check this, and correct this if necessary.
I believe the fuses are shown in the upper right corner of the Device
Editor. (I don't have the full IDE).

However, that might not be the problem. There are at least 20 topics
in the Programmer forum on "Verification Errors". Many different
solutions are proposed. Here is one thread:
http://www.ccsinfo.com/forum/viewtopic.php?t=34168&highlight=verification

My personal solution is to use ICD2 and MPLAB. I've never had a
verification error.
mikehagans



Joined: 20 Jun 2007
Posts: 7
Location: Texas, USA

View user's profile Send private message

PostPosted: Fri Dec 18, 2009 2:39 pm     Reply with quote

Thanks for the thoughtful replies. I've sent in a tech support request with CCS and they sent me a new ccsload (ICD programming software) that was supposed to address my issue. It didn't make any difference.

This could be a simple something that I'm doing wrong, but I followed the CCS instructions, using the CCS IDE and the CCS development kit. Very frustrating - it's a miserable first impression for the quality of CCS products and tech support.

Hopefully they will figure out what's wrong yet...

Of course, I'm losing days of time...

Sorry to rant - your suggestions make more sense than CCS'. I'll check the devices file and see if I can find their mistake.

Happy Holidays!

Mike
hans_kurth
Guest







Re: Verification Failure on CCS Development Kit using ICD-U6
PostPosted: Sat Dec 26, 2009 11:49 am     Reply with quote

I have exactly the same problem with Capacitive Touch Development Kit. Compiler V4.103 CCSload V4.022. Now I have removed the file devices4.dat and file devices4p.dat renamed to devices4.dat. Apparently this is an older version, that does work better for the PICLF727. No verification error and no error message when you start the debugger.
Display posts from previous:   
Post new topic   Reply to topic    CCS Forum Index -> CCS ICD / Mach X / Load-n-Go 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