 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 : PIC32PROG error....
| Author | Message | ||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9754 |
Hi all.  This is an odd error, and I have no idea what it means. Can someone tell me what it is trying to tell me? 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 Processor: MX170F256D Flash memory: 256 kbytes Boot memory: 3 kbytes Data: 258392 bytes Erase: (20mS) done Loading PE: 1 2 3 4 (LDR) 5 6 7a (PE) 7b 8 v0301 Program flash: ................................................ total TDI/TMS pairs sent = 32569 pairs total TDO bits received = 3424 bits total ascii codes sent = 10756 total ascii codes recv = 1186 maximum continuous write = 452 chars O/S serial writes = 1104 O/S serial reads (data) = 110 O/S serial reads (sync) = 10 XferFastData count = 461 10mS delays (E/X/R) = 2/0/0 elapsed programming time = 0m 01s failed to program row at 1d000000, reply = 00000002 It obviously starts to program fine, then falls over. One would be thinking faulty PIC32, but it was a brand new one, so I don't think it could be that, could it? I wear full anti-static straps, grounded irons etc,so it can't have been statically damaged. Smoke makes things work. When the smoke gets out, it stops! |
||||
| JohnS Guru  Joined: 18/11/2011 Location: United KingdomPosts: 4133 |
Looks like it failed almost immediately. You may need to say what board etc the CPU is in and what else is involved. Those items are suspects. John |
||||
| robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2464 |
1d000000 is the very beginning of flash memory, while error 2 is simply "command unsuccessfully processed". the error is being generated by the PE that runs on the target processor while programming is happening. i've seen this exact same address/error before - quite a long time ago, and i remember it being because of something quite simple. it could have been Vcc not solid enough or too low, or a missing Vcap. essentially the mx170 having enough juice to run a program (the PE), but not enough oomph to complete a flash write. the 20ms erase time is also suspiciously low, from past experience i'd normally expect to see around 80ms or so. are you using a 1455 or a nano as the programmer? is there any other circuitry on the board containing the mx170 that is drawing power? are all Vcc and ground pins connected? cheers, rob :-) addendum: "ascii ICSP v1N", it must be a 1455. |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9754 |
It is a 1455. I've never run into this problem before, so I'm a little stumped. The 1455 always just works.  The board is a special board I did for a client - it is not a public design, but all the standard design requirements were met. The board failed(user error), and when I got it back, there were two burn-through holes in the PIC32, so I knew that was toast. I removed it and replaced it after first checking all the voltages etc. I have a feeling that whatever happened to the board has also damaged something else on the same board. I will remove this 'Suspect' processor, and build a brand-new board and put this processor on it and see if I can program it in that. I will let the thread know if that succeeds. Smoke makes things work. When the smoke gets out, it stops! |
||||
bigmik Guru Joined: 20/06/2011 Location: AustraliaPosts: 2971 |
Hi Grogs, OK the original Pic170 is obviously Popped. So it was hit by some spike... I would suspect the 1455 is dead as well. obviously, I assume , you have checked the voltage is correct and smooth. Kind Regards, Mick Mick's uMite Stuff can be found >>> HERE (Kindly hosted by Dontronics) <<< |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9754 |
1455 is seperate from the board, as a programmer, so it was not on the board when it was killed, so it is fine. All voltages checked out when I tested the board BEFORE I fitted the new PIC32 chip. 3v3 rail was 3.2v - slightly low, but I still think that is close enough. Another new board measures 3.2v on that regulator too. (1117-3.3) I don't think it is worth the effort of playing with this one anymore, as just about everything else on the board is an unknown at this point. I have started building a new one. Smoke makes things work. When the smoke gets out, it stops! |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
