WriteChip error PIC32MX460F512L

[Charles_Marloye]

Hello,

I m currently working on a project with a Mikromedia board (with chip PIC32MX460F512L).
Everything was fine until now.
When I program my board, i have the folowing issue :

WriteChip Burst
Chip write
Memory programming FAILED !
Physical address : 0x1D01_9A00
1 Instruction location(s) with error.
Executive response: PASS

I have looked over the forum and I tried every suggestions I ve seen. (update last version, check box VerChipBurstError, ...)

I can do an Erase cycle, blank check, read but i can't write.

When i remove some lines from my software it seems to work. I also tried cleaning my project by copying it and remove non essential parts but at some point the problem come back.
I m very far from the 100% memory allocation. I didn't find a correlation with the size of source files and the error occuring.

I'm out ouf idea that's why i come to you for help.

See in attachments screenshots of MikroProg Suites settings, MikroC for PIC32 project compilation results & project settings (note : im working with a mikromedia board with external ressources configure in FAT32).
You ll also find the Hex file causing the issue and files in the SDCard (FAT32)

If you need more informations plz ask me.

Best Regards

Charles

[filip]

Hi,

I apologize for the inconvenience caused by this.

Can you please attach your project that demonstrates this issue ?
Which programmer are you using exactly ?

Also, update the mikroProg Suite for PIC to the latest version, 2.90, from here :
http://download.mikroe.com/setups/progr ... p-v290.zip

Regards,
Filip.

[Charles_Marloye]

Hello Mr Filip,

Thanks for your reply.

The Mikromedia is soldered to an interface board on which I have some peripherals (wireless module, button with pull-up & filter, LEDs).
I use the following wire : 5V, 3V3, PGC, PGD and GND to program the mikromedia (cable between my board and the workstation V7 board).
I made a new project from start and I made a new cable this morning and it seems ok .

I updated the MikroProg software to be sure (i was thinking in the inital message about a firmware update of the programmer, not the software itself my bad).

Until now everything seems ok (but i dont know why - the joys of electronics).

I think the problem was software maybe a linking error with the files generate by VTFT ? And the result is a point at a wrong memory space ?
Sorry for the trouble.

Best Regards

Charles

[filip]

Hi,

I really have no idea why did this issue happen, I suppose that your interface board maybe interfered in some way (I don't have schematics and photos of connection so I cannot be sure).

Anyway, I'm glad that this is working now.

Regards,
Filip.