Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.
|
Forum Index : Microcontroller and PC projects : Unknown CPUID=058ff053.
Author | Message | ||||
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9043 |
I've been trying to program a few MM+ chips(64-pin ones) via the 1455 chip and PIC32prog and the GUI, and it never works - all I get is this error. Rob - do you have any idea what this means? I've never seen this before, and I must have now programmed hundreds of MM chips with the same 1455 arrangement..... Tried THREE totally different boards, but this is all I get every time. Edited 2021-04-10 16:16 by Grogster Smoke makes things work. When the smoke gets out, it stops! |
||||
bigmik Guru Joined: 20/06/2011 Location: AustraliaPosts: 2867 |
Grogs, I migh5 be stating the obvious but do you have the VCap in and correct polarity? Mik Mick's uMite Stuff can be found >>> HERE (Kindly hosted by Dontronics) <<< |
||||
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9043 |
Good idea, but I ALWAYS use 10uF X5R MLC for Vcap. MLC don't care about polarity. X5R is more stable then X7R MLC, and it has ALWAYS worked before.... Smoke makes things work. When the smoke gets out, it stops! |
||||
bigmik Guru Joined: 20/06/2011 Location: AustraliaPosts: 2867 |
Grogs, Maybe there is something wrong with a new batch of caps (incorrect value for Instance)?? Mik Mick's uMite Stuff can be found >>> HERE (Kindly hosted by Dontronics) <<< |
||||
robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2285 |
i've looked up CPUID/IDCODE 0x58ff053 as best i could, but not found any match. are you able to post the full output from pic32prog. as i recall, you can also run pic32prog without any .hex file on the command line and it will list the information about the attached processor. generally in the past, when seeing pic32prog return an unexpected ID, it has always turned out to be an issue with (1) bad power, (2) not all power/ground pins connected, (3) a Vcap problem, or (4) other electronics sharing the ICSP pins. what is the exact part number printed on top of the problematic PIC32 devices, and does this number match other micromites that you've assembled before that work? cheers, rob :-) |
||||
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9043 |
@ Mick: Anything is possible I guess. I get my caps from element14, so they should be good quality genuine ones. @ Rob: EXACT part number is the 64-pin MM+ chip - PIC32MX470F512H. I've programmed probably hundreds of this part chip using pic32prog before. This is a totally new problem, but the fact it exists across multiple boards all giving the same error code, or simply failing to connect to the chip at all. I will now connect a faulty board and run pic32prog at command line without the HEX - great tip, thanks! EDIT: I've forgotten all the command-line switches. Can you remind me what they are? Edited 2021-04-11 10:28 by Grogster Smoke makes things work. When the smoke gets out, it stops! |
||||
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9043 |
This is the pic32prog output on the one that sort-of responds: Programmer for Microchip PIC32 microcontrollers, Version 2.0.193 Copyright: (C) 2011-2015 Serge Vakulenko (ascii ICSP coded by Robert Rozee) Adapter: . OK1 OK2 - ascii ICSP v1N total TDI/TMS pairs sent = 151 pairs total TDO bits received = 72 bits total ascii codes sent = 73 total ascii codes recv = 27 maximum continuous write = 24 chars O/S serial writes = 9 O/S serial reads (data) = 3 O/S serial reads (sync) = 0 XferFastData count = 0 10mS delays (E/X/R) = 0/0/0 elapsed programming time = 0m 00s Unknown CPUID=058ff053. Now, exactly same board, but switching to a PK3 and IPE: ***************************************************** Connecting to MPLAB PICkit 3... Currently loaded firmware on PICkit 3 Firmware Suite Version.....01.56.07 Firmware type..............PIC32MX Target voltage detected Unable to connect to the target device. Failed to get Device ID Six other boards flatly refuse to talk AT ALL to either pic32prog("No target found"), or IPE("Connection failed") I also have ONE unit that DID detect and program just fine, but then you can't talk to it via the console or CTRL+C. 1455 LED blinks OK as you type, but you get absolutely no response from the chip. That's odd too. If you are able to program in the HEX at all, it should then WORK. At least as far as the MMBASIC console, but no, not that unit..... Edited 2021-04-11 10:39 by Grogster Smoke makes things work. When the smoke gets out, it stops! |
||||
phil99 Guru Joined: 11/02/2018 Location: AustraliaPosts: 1769 |
May not be directly relevant but some issues I have had are:- Reset pin filtering. Some boards have a 100n cap from the reset pin to ground to prevent random resets due to noise on the power supply rail. This capacitor interferes with MCLR signals, Microchip recommend putting a 1k resistor in series with it. Changing the 10k pullup to 4k7 may also help. Power supply impedance. Extra caps close to the supply pins fixed one of mine. Same as you use for VCap. |
||||
robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2285 |
are all the PCBs from the same batch? i'd try buzzing out all the Vcc, ground, and the Vcap connection. if all the same batch of PCBs, i'd guess at this stage that the PCB manufacturer has left out a ground or Vcc via. cheers, rob :-) |
||||
Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9043 |
FIXED THE PROBLEM!!! Please see the BAD SILICON thread for the solution. Smoke makes things work. When the smoke gets out, it stops! |
||||
Print this page |