-
Hello!
I've been using up to PIC18, but I'm new using PIC32. I thought that it would be the same process, but I'm having a hard time making it work.
I'm developing a board for my graduation proyect with this PIC32MZ2048ECH100
PIC32MZ EC Processor Plug-In Module (PIM) - MA320012 | Microchip Technology Inc.
http://www.microchip.com/Developmenttools/ProductDetails.aspx?PartNO=MA320012
The thing is that I can't seem to make it work with the programmer.
This is what i get from MPLAB IPE
*****************************************************
Connecting to MPLAB PICkit 3...
Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.51.08
Firmware type..............PIC32MZ
Programmer to target power is enabled - VDD = 3,500000 volts.
Unable to connect to the target device.
Failed to get Device ID
2018-04-08 20:58:05 -0500 - Read failed
-
hi, besides checking to see if you got the clocks all set up correctly, did you do the ICESEL = ICS_PGx2 if you are on those pins for programming?
g -
Hi,
Watch out - Microchip is recommending the PIC32MZ2048EFH100 for new designs as a replacement.
basically there are a significant number of silicon errors on the EC series, some of them render the peripherals almost useless. Not that the EF series doesn't have its issues as well.. Check the device errata datasheets from Microchip to see if any of them will affect your project.
As for programming, as BRV64 mentioned, double check your ISCP programming pin selections. You may be using the wrong pair. If you have switched them using configuration bits, you may need to temporarily swap pairs to do an erase... Not sure, I've not needed to try that.
Ash. -
That's incorrect. every ICSP pair is always accessible for programming. with the configuration bits you select which pair you want to use with the debugger
Feel free to check the datasheetQuoteICESEL<1:0>: In-Circuit Emulator/Debugger Communication Channel Select bits
Failure to find the device could be
-Wrong PGD/PGC connections but the wiring seems correct at glance
-incorrect power applied, that's more probable. Why are you supplying power from both the PK3 and the demoboard?
it's best if you don't supply power from the PK3.
if you have access to a scope try to probe the MCLR,PGD and PGC pins during programmer connection and see for abnormalities (sags, clock not being a clock, mclr at incorrect levels..)
also try using the IPE to connect, i find it faster to use when i have connection problems
-
That's incorrect. every ICSP pair is always accessible for programming. with the configuration bits you select which pair you want to use with the debugger
I don't recall offhand if the MZ has a VCap pin, but lack of this on the MX devices will stop programming working.
Feel free to check the datasheetQuoteICESEL<1:0>: In-Circuit Emulator/Debugger Communication Channel Select bits
Failure to find the device could be
-Wrong PGD/PGC connections but the wiring seems correct at glance
-incorrect power applied, that's more probable. Why are you supplying power from both the PK3 and the demoboard?
it's best if you don't supply power from the PK3.
if you have access to a scope try to probe the MCLR,PGD and PGC pins during programmer connection and see for abnormalities (sags, clock not being a clock, mclr at incorrect levels..)
also try using the IPE to connect, i find it faster to use when i have connection problems
Also 3.5v sounds a little high for Vdd, and if you are trying to power the target from PicKit bear in mind it may not be able to supply enough current for a 32MZ
-
I checked and there isn't.. but he's using a Plugin-module anyway, which has all the necessary cap and oscillators on board, also all the VDD and VSS are connected together
@BRV64: Did you also connect ADVV/ADSS? AVDD is on a separate pin on the PIM and it is required to be within Vdd +/- something to ensure correct behaviour -
ICESEL has absolutely no effect on programming, only on debugging. Think about that. How the setting within the program you're only going to program on the device can affect the programming process?
It's most likely your connection - bad contact or wrong pins.
EC chips are obsolete. They had so many bugs that Microchip decided not to fix them and created new EF chips instead. -
maybe he has to use an EC because that's what his university lab has