PIC32MX170F256D error with mikroProg

[mpavlica@gmail.com]

Hi
When I attach mikroprog to my board with PIC32MX170F256D it results as in... well, image below.
First, it shows that it is "Unknown", and yes, hardware connections are fine, since I can program chip with PICKIT2
Second, check for config bytes on board... this PIC chip does not have USB peripheral.
Any thoughts?

[IvanJeremic]

Hi,

Milan, we are talking about this topic in a ticket so lets continue our conversation there.

For everyone else that might be having a similar issue with this MCU, in Mialns case it seems the problem was due to his MikroProg being faulty.

Also i would like to add that the mlk file for this MCU is not well defined.

The error is in the MAXX_ADDR, basically instead of "0x1D03EFFF" write "0x1D03FFFF".

Untitled.png (6.02 KiB) Viewed 711 times

Regards,

Ivan.

[mpavlica@gmail.com]

Well, I am not sure that problem is with mikroProg as a faulty unit or maybe some firmware bug, because, it didnt work from the day one as it should. I tried to repair it today, replaced 4053 and error persists. Also tried to change pins on PIC from PGD3 to PGD1 pins, waveforms are correct but check with a scope shows that PIC doesnt reply to a mikroProg. Its a bare PCB with only a PIC on a board. That board can be perfectly programed with a PICKIT2. Also, on some other boards using other 32bit controller, I have found that mikroprog is really on the edge, while pickit2 is programming them with no problems.... On other boards with PIC18F and PIC18F-K it works in 99% cases while pickit2 is 100% OK.

[VCC]

Hi, I had similar problems with PIC32MX250F128D and PIC32MX270F256D. This happened 10 years ago and a month ago with two different mikroProgs and only with new, unprogrammed devices. It looks like they are blocked somehow (or maybe some protection bits are blocking the programming process). What is different between PICKit and mikroProg is that mikroProg keeps verifying (i.e. reading) the written data after every piece (I hope I'm not wrong), or it tries to get the device ID. That is were the error comes from. The "solution" was to erase the device 2-3 times with mikroProg, until it succeeds. Then, it can program it without any problem. Maybe we should have an option in mikroProg suite, to skip verifying or reading the ID.

[mpavlica@gmail.com]

So, its not only me... Funny thing, once again is that i tried pickit2 - original, pickit2 from aliexpress, pickit3, pickit 3.5, and i tested them also with a pic32prog, opensource software and it works every time, so it has something with software that runs mikroProg.... Now its all about mE, will they pursue this matter or they will keep it hanging... or simply say - buy a codegrip and thats it... to be honest, to buy a new programmer after this experience... hmmmm....