ERROR MESSAGE IN MPLAB

63 views
Skip to first unread message

SIDDHARTH

unread,
Apr 14, 2010, 12:20:59 PM4/14/10
to uavde...@googlegroups.com

Dear All,

                        Any idea on below error I am getting.. This error appears only when it verifies , till that point all is well.

 

...Program Memory

ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x404A6, Val Read = 0xFFFFFF)

ICD0275:  Programming failed.

MPLAB ICD 2 ready for next operation

 

Regards

Sid

 

William Premerlani

unread,
Apr 14, 2010, 3:27:33 PM4/14/10
to uavde...@googlegroups.com
Sid,
 
Well, that is not good. The last time I saw that error message it was when I had a failed ICD2 and sent it back to SparkFun.
 
What the message means, basically, is that when the ICD2 tried to verify the program, nothing came back from the UDB. The value FFFFFF is not a random value, it means there was no data transfer.
 
It is not clear whether there was an undetected problem during programming, or whether it programmed ok, and then failed to verify.
 
So, this is a tough one. Possibilities include the usual suspects:
 
1. ICD2 problem.
2. UDB problem.
3. Loose connection.
4. MPLAB problem.
 
Did the UDB work ok after you programmed it?
 
Did the problem repeat itself the next time you programmed the UDB?
 
Best regards,
Bill

 

Adam Barrow

unread,
Apr 14, 2010, 3:38:22 PM4/14/10
to uavde...@googlegroups.com

Sid,
Do you have any other way of programming the UDB? If this is a repeatable problem, it would help to troubleshoot the ICD. You can program the UDB using your other programmer, and try to verify with your ICD.

Hopefully it's just a loose wire, which is what happened with my PicKit2 when i got the same error.

Regards,
Adam Barrow
Sent from my mobile phone.

On Apr 14, 2010 2:27 PM, "William Premerlani" <wprem...@gmail.com> wrote:

Sid,
 
Well, that is not good. The last time I saw that error message it was when I had a failed ICD2 and sent it back to SparkFun.
 
What the message means, basically, is that when the ICD2 tried to verify the program, nothing came back from the UDB. The value FFFFFF is not a random value, it means there was no data transfer.
 
It is not clear whether there was an undetected problem during programming, or whether it programmed ok, and then failed to verify.
 
So, this is a tough one. Possibilities include the usual suspects:
 
1. ICD2 problem.
2. UDB problem.
3. Loose connection.
4. MPLAB problem.
 
Did the UDB work ok after you programmed it?
 
Did the problem repeat itself the next time you programmed the UDB?
 
Best regards,
Bill

 


On 4/14/10, SIDDHARTH <sysn...@sify.com> wrote:
>
> Dear All,
>

>                         Any ide...

Murali- VU3MUV

unread,
Apr 14, 2010, 4:33:34 PM4/14/10
to uavde...@googlegroups.com
Hi Sid ,
is this error out of the new pickit2 clone you mentioned earlier ? which programmer did you use when you got this error? It will help others to determine the cause probably, in any case both Bill and Adam have answered you , hope this issue is resolved now and you have successfull flight :) , cheers & and good luck

SIDDHARTH

unread,
Apr 14, 2010, 10:41:05 PM4/14/10
to uavde...@googlegroups.com

Bill,

            Thanks for your reply.  According to your suggestions  below  the first thing I am going to do is to  try to programme with my clone PICKIT to rule out MPLAB issues if any.. If that works then I will hunt further.. I hope and wish my ICD2 is ok, since it is my favorite and most reliable programmer.

 

            I haven’t checked that UDB worked after programmed with that error message ..Will do that today.

 

            The exactly same message appears every time when I try to programme UDB with ICD2.

 

@ Adam B..  I hope and wish it’s just a loose wire but I will try to programme with clone PICKIT2 and see what happens , then I will look further.

 

@ Murali , This message I got while I used ICD2 not the PICLONE2..

 

Regards

SID

 


Reply all
Reply to author
Forward
0 new messages