Searching \ for '[PIC] ICD2 clone and MPLAB' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devprogs.htm?key=icd
Search entire site for: 'ICD2 clone and MPLAB'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] ICD2 clone and MPLAB'
2011\02\24@060444 by Manu Abraham

picon face
Hi,

I have been using an ICD2 clone quite successfully with MPLAB and an
18F452 over USB on Windows 7 host. The chip being used in it's ZIF
socket, rather than ICSP.

but that said, once in a while:

- get verify failed after a device Program, device verify

I thought it was an issue with the device, tried a newer device, still
the same issue persists

- After playing around a bit, Program->erase->program->erase cycles,
verify says it is okay
(In some of these such cases, the device works as expected, in some
cases, the programmed device looks dead)

- In some cases, MPLAB says it cannot open the USB port. Now whatever
I do, how many restarts of the computer, the error persists.
(With some trial, I found that removing the ICD2 driver and
reinstalling it again works)

- With this it looks like all is working again ... But after some days
or cycles of Flashing- Erasing - The issue is back again.

I thought it could be the cables, connectors... but that seems quite
unlikely as I have tried replacing them, still see this issue in some
cyclic manner.

Anybody else seeing such a weird behaviour ?

Thanks,
Man

2011\02\26@074623 by PicList

flavicon
face
Manu Abraham wrote:

> - get verify failed after a device Program, device verify

[...]

> I thought it could be the cables, connectors... but that seems quite
> unlikely as I have tried replacing them, still see this issue in some
> cyclic manner.
>
> Anybody else seeing such a weird behaviour ?


Identical symptoms with a PICkit2 - it was the cable - several in fact. Expensive "thick" cables caused the problem. Cheap "thin" cables worked fine

2011\02\28@102151 by Manu Abraham

picon face
Hi,

On Sat, Feb 26, 2011 at 6:16 PM, PicList <spam_OUTpiclistTakeThisOuTspamsentry.org> wrote:
> Manu Abraham wrote:
>
>> - get verify failed after a device Program, device verify
>
> [...]
>
>> I thought it could be the cables, connectors... but that seems quite
>> unlikely as I have tried replacing them, still see this issue in some
>> cyclic manner.
>>
>> Anybody else seeing such a weird behaviour ?
>
>
> Identical symptoms with a PICkit2 - it was the cable - several in fact.
> Expensive "thick" cables caused the problem. Cheap "thin" cables worked
> fine.


Today, I changed connectors again, but got identical behaviour.

verify nevertheless fails. Device doesn't seem to be programmed
correctly either.
The logs look thus:

Connecting to MPLAB ICD 2
....Connected
Setting Vdd source to MPLAB ICD 2
Target Device PIC18F452 found, revision = c0
....Reading ICD Product ID
Running ICD Self Test
....Passed
MPLAB ICD 2 ready for next operation
Erasing Target Device...
....Erase Succeeded
MPLAB ICD 2 ready for next operation
Blank Checking...
....Program Memory
... Config Memory
....EEPROM
....User ID Memory
....Blank Check Passed
MPLAB ICD 2 ready for next operation
Verifying...
....Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val
= 0xEF33, Val Read = 0xFFFF)
MPLAB ICD 2 ready for next operation


If the issue is with the cables, the device type and version detection
should also fail, right ?

Best Regards,
Man

2011\02\28@104155 by Dave Tweed

face
flavicon
face
Manu Abraham wrote:
{Quote hidden}

Am I missing something here? According to the log, you erased the device,
confirmed that it was blank, and then tried to verify, which failed. There
doesn't appear to be any attempt to program the device at all.

-- Dave Twee

2011\02\28@105250 by Manu Abraham

picon face
On Mon, Feb 28, 2011 at 9:11 PM, Dave Tweed <.....picKILLspamspam@spam@dtweed.com> wrote:
{Quote hidden}

uhmm, true .. That was quite dumb of me that I didn't think that
verify would be comparing against the flash image. Right now,
programming appears to work fine again. I will post again when verify
fails after a successful Program again.

Thanks,
Man

2011\02\28@105929 by Carl Denk

flavicon
face
That's what it looks like to me too. :)

In MPLAB the top menu: Programmer > Settings,

check the box "Program after successful build",

or

Programmer > Program.

:)

On 2/28/2011 10:41 AM, Dave Tweed wrote:
{Quote hidden}

>

More... (looser matching)
- Last day of these posts
- In 2011 , 2012 only
- Today
- New search...