Hello world on pic32MX220F32D

[Bart embrechts]

After a little prototyping I made a PCB with a PIC32MX220F32D. I try to write a empty project to the pic with a mikroProg and get every time the message : "WriteChip Burst. Verify error!" followed by : "WriteChip. BOOT code programming fail !" and "WriteChip. Configuration bits programming fail !"
Does anybody have an idea what this means.
I am able to blank end erase the chip, so a know that the mikroProg is able to talk to the pic.
I also tried to play a little with the oscillator settings as my I my PCB is SMD, miniature and tuff to solder.
thx in advance for the response,
Bart

[janko.kaljevic]

Hello,

Please can you check your inbox.
I have sent you possible solution for the issue.

Best regards.

[Bart embrechts]

thx for the good and quick support Janco,
My problem is solved!
That's why people like Mikroe products.

[RoyRad]

I am having a similar problem with the same chip. The programmer firmware is up to date. I am using the latest version 2.29. The programmer works with pic32mx795f512 and pic16f877 and pic16f876 just fine. I have read many posts with the same problem but none have the official solution posted from mikroe. I picked up from the posts that it might be necessary to use an exernally powered USB. Whatever the solution may be, please post or email me the solution.
Thanks,
Roy

[pwdixon]

Hello,

Please can you check your inbox.
I have sent you possible solution for the issue.

Best regards.

That's really informative to the rest of us, can ME please stop going off-forum with the replies it makes the forum completely useless, unless of course ME only want to support their products directly via email individually to all their customers.

[p.erasmus]

That's really informative to the rest of us, can ME please stop going off-forum with the replies it makes the forum completely useless, unless of course ME only want to support their products directly via email individually to all their customers.

Totally agree with this ,has mentioned this in the past as well

[janko.kaljevic]

Hello,

I apologize if my answer looked like i was hiding something from community.

Please let me explain this situation.

At the moment some silicon revisions of the small PIC32 controllers does not work with current version of mikroProg firmware.
Unfortunately, only solution at the moment is to use modified mikroprog firmware version. This is very limited behavior and does not affect much users, and we chosen to send solution via private correspondence.
But if anyone has similar problem, we will be glad to help.

Also this is only current solution for the problem, until we find best possible solution, and then we will offer it to all our users through official release.

Thanks for understanding.

Best regards.

[p.erasmus]

Janko

Thank you for your explenation to the issue

Regards