• AVR Freaks

Helpful ReplyHot!Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053]

Author
Jason Watton
Starting Member
  • Total Posts : 31
  • Reward points : 0
  • Joined: 2015/02/24 04:52:41
  • Location: 0
  • Status: offline
2020/06/30 04:10:38 (permalink)
0

Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053]

Attempting to program 2 boards (of the same design 'A') gives error:
Target Device ID (0x7200053) is an Invalid Device ID.
This ID is - indeed - invalid (from Errata).
The chip in use is a PIC32MZ2048EFH144, valid ID 0x7227053. The ID is 'partially formed'.
- We have previous designs - same chip, different I/O usage - which program fine.
- We have two other board designs ('B' and 'C') manufactured within days of these others - same chip, different I/O usage - which program fine.
- We have tried replacing the PIC32. No change.
- We have tried the latest MPLAB IDE and IPE v5.40.
- We have checked all the connections in section 2.1 of the datasheet, physically buzzed them out, and cannot find any faults.
 
Can anyone provide an insight into the area we should concentrate our search for a fault based on 0x7200053 rather than 0x7227053?

Attached Image(s)

#1
ric
Super Member
  • Total Posts : 28024
  • Reward points : 0
  • Joined: 2003/11/07 12:41:26
  • Location: Australia, Melbourne
  • Status: online
Re: Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053] 2020/06/30 04:34:44 (permalink) ☄ Helpfulby Jason Watton 2020/07/27 05:32:21
0
I have seen some reports that on some devices, ALL the PGEDx pins toggle when you are programming the device, not just the one being used.
Could there be some congestion on your board from circuitry driving the unused PGEDx pins?
 

I also post at: PicForum
Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
NEW USERS: Posting images, links and code - workaround for restrictions.
To get a useful answer, always state which PIC you are using!
#2
Jason Watton
Starting Member
  • Total Posts : 31
  • Reward points : 0
  • Joined: 2015/02/24 04:52:41
  • Location: 0
  • Status: offline
Re: Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053] 2020/06/30 05:23:22 (permalink)
0
@ric...
Thanks for replying.
What you say makes sense...
but...
https://www.microchip.com/forums/m1145851.aspx?tree=true#
From this post we have almost dismissed the idea of disconnecting PGEC1 and PGED1 (used for I/O - we use PGEC2 and PGED2 for programming)... have you any links to the reports you mention...?
Thanks!
#3
NorthGuy
Super Member
  • Total Posts : 6230
  • Reward points : 0
  • Joined: 2014/02/23 14:23:23
  • Location: Northern Canada
  • Status: offline
Re: Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053] 2020/06/30 05:50:08 (permalink) ☄ Helpfulby Jason Watton 2020/06/30 09:55:21
4 (1)
I've seen similar things with PIC32. Looks like that part of the ID is hard-coded, while the other is loaded from somewhere when the PIC boots. I had to insert a delay between reset and ID probing and this cured this problem. You cannot do this. However, there are two considerations:
 
1. The programming may still work even though the Id is reported bad.
 
2. There might be something on your board which delays PIC boot - perhaps something connected to MCLR, such as capacitors, extra series resistors on the line between MCLR pin and a programmer etc.
#4
wdy
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2016/10/05 06:32:30
  • Location: 0
  • Status: offline
Re: Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053] 2020/06/30 07:12:27 (permalink)
0
NorthGuy
I've seen similar things with PIC32. Looks like that part of the ID is hard-coded, while the other is loaded from somewhere when the PIC boots.

The latter - perhaps Flash fuses? Could be plain metal layer connections, too, since mask revision is included in the ID.
 
In any way, the suggestion to wait a bit after reset is worth trying.
#5
Jason Watton
Starting Member
  • Total Posts : 31
  • Reward points : 0
  • Joined: 2015/02/24 04:52:41
  • Location: 0
  • Status: offline
Re: Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053] 2020/06/30 07:31:14 (permalink)
0
wdy
In any way, the suggestion to wait a bit after reset is worth trying.

Thanks for the comments, guys.
We are currently musing over "Waiting a bit after reset" as we are using Microchip's ICD3 programmer, which doesn't offer us this option [unless you know of one].
The circuit on MCLR is simpler than that shown by @NorthGuy:
https://www.northernsoftware.com/dev/pic32mz/pic32mz1024efh144.htm
insofar as we only use R2; there is no R1 nor C3.
 
In response to @NorthGuy item (1), if we continue to attempt to program anyway, it tragically "fails to program".

Attached Image(s)

#6
NorthGuy
Super Member
  • Total Posts : 6230
  • Reward points : 0
  • Joined: 2014/02/23 14:23:23
  • Location: Northern Canada
  • Status: offline
Re: Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053] 2020/06/30 08:02:27 (permalink)
0
Jason Watton
In response to @NorthGuy item (1), if we continue to attempt to program anyway, it tragically "fails to program".



Then there must be something else. Your connection is obviously correct, otherwise you wouldn't get any id. Since you can program other PICs of the same kind with the same tool, you can rule out bugs in the tool and other things alike. But there's something on your board which prevents PIC from running. Have you tried to solder a pre-programmed PIC onto the board and see if it runs?
#7
Jason Watton
Starting Member
  • Total Posts : 31
  • Reward points : 0
  • Joined: 2015/02/24 04:52:41
  • Location: 0
  • Status: offline
Re: Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053] 2020/06/30 09:51:23 (permalink)
0
NorthGuyThen there must be something else. Your connection is obviously correct, otherwise you wouldn't get any id. Since you can program other PICs of the same kind with the same tool, you can rule out bugs in the tool and other things alike.

We were hoping one of you gurus may have seen this before...
NorthGuyBut there's something on your board which prevents PIC from running. Have you tried to solder a pre-programmed PIC onto the board and see if it runs?

Not yet. Point taken.
Swapping PICs has taken its toll. A disastrous PIC removal on one board has rendered it unusable and pictures of it would get me banned from the Forum for distributing disturbing content. The screwball from that board is that - with a PIC lashed up to what remains of its pads - it now programs (and debugs) but almost every I/O function on it has been destroyed.
We are treasuring our second (last) board and contemplating our next step.
#8
wdy
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2016/10/05 06:32:30
  • Location: 0
  • Status: offline
Re: Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053] 2020/06/30 14:01:35 (permalink) ☄ Helpfulby Jason Watton 2020/07/27 05:31:56
4 (1)
Jason WattonWe were hoping one of you gurus may have seen this before...

Unfortunately, no. I have my own programmer and tools and found plethora of other problems, but this particular one - nope.
#9
Jason Watton
Starting Member
  • Total Posts : 31
  • Reward points : 0
  • Joined: 2015/02/24 04:52:41
  • Location: 0
  • Status: offline
Re: Invalid Device ID: 0x7200053 for PIC32MZ2048EFH144 [0x7227053] 2020/07/27 05:26:58 (permalink)
0
NorthGuy
But there's something on your board which prevents PIC from running.

wdy
I have my own programmer and tools and found plethora of other problems, but this particular one - nope.

Okay gurus...

Big thank you for all your input and suggestions. I'd like to try to repay you with the results of our testing...

This was by systematically connecting only the essential pins, testing for success, then gradually working round the chip pins reconnecting them:

Min config fitted (VSS/VDD/AVSS/AVDD/MCLR/CLK/PGC/PGD) = Device ID ok, silicon rev B2.
Fitted pins 138-144 = Device ID ok, silicon rev B2.
Fitted pins 124-137 = Device ID ok, silicon rev B2.
Fitted pins 109-123 = Device ID ok, silicon rev B2.
Fitted pins 101-106 = Device ID ok, silicon rev B2.
Fitted pins 97-100 = Device ID ok, silicon rev B2.
Fitted pins 87-96 = Device ID ok, silicon rev B2.
Fitted pins 81-86 = Device ID ok, silicon rev B2.
Fitted pins 73-80 = Device ID ok, silicon rev B2.
Fitted pins 63-72 = Device ID ok, silicon rev B2.
Fitted pins 59-62 = Device ID ok, silicon rev B2.
Fitted pins 56-58 = Device ID ok, silicon rev B2.
Fitted pins 48-53 = Device ID ok, silicon rev B2.
Fitted pins 42-47 = Device ID ok, silicon rev B2.
Fitted pins 37-41 = Device ID ok, silicon rev B2.
Fitted pins 34-36 = Device ID ok, silicon rev B2.
Fitted pins 28-33 = Device ID ok, silicon rev B2.
Fitted pins 17-27 = Device ID ok, silicon rev B2.
Fitted pins 14-16 = Device ID ok, silicon rev B2.
Fitted pins 11-13 = Device ID ok, silicon rev B2.
Fitted pins 9-10 = Device ID ok, silicon rev B2.
Fitted pins 7-8 = Device ID ok, silicon rev B2.
Fitted pins 5-6 = Device ID ok, silicon rev B2.
Fitted pin 4 = Device ID ok, silicon rev B2.
Fitted pin 3 = Device ID ok, silicon rev B2.
Fitted pin 2 = Device ID ok, silicon rev B2.
Fitted pin 1 = Device ID 0x7200053
Lifted pin 1 = Device ID ok, silicon rev B2.
Fit pin 1, lift pin 2 = Device ID ok, silicon rev B2.

On our second board:

Lifting pin 1 on this board didn't solve the problem but lifting pins 1 and 2 did and it programs fine; we then found that the problem is not due to any transient effect at power-up: in fact the outputs from IC14 go immediately to -12V and stay there.
[IC14 feeds pins 1 and 2 of the PIC; pins 1 and 2 are used as ADCs and do differ from the common design with the other boards].

CONCLUSION: The Invalid ID is due to an errant (constant, invalid) voltage on pins 1 and 2. The errant -12V appears to 'quash' the middle section of the ID.

I hope this helps if you gurus ever hear of this again...

Again, thank you.

Jason.
#10
Jump to:
© 2020 APG vNext Commercial Version 4.5