MPLAB-X PICkit3 DSPIC33EP512GP502 Debug error

[PaoloBi]

Hello,
Excuse me for my English, it is the first time that I make a request on this site, I am a retiree with the hobby of electronics.
I tested several dsPIC33FJ (64/128) (GP / MC) 802 on a test board and was able to debug correctly by getting the output pin state change.
The board has only the minimum connections for programming with 0.1uF capacitors on the power supply and tantalum capacitor on VCAP.
Then I tried 3 different dsPIC33EP512GP502 on the same board, if I program for production I get the message:

Code:

Device Erased ...
Programming ...
The following memory area (s) will be programmed:
program memory: start address = 0x0, end address = 0x3ff
configuration memory
Programming / Verify complete

But it doesn't run the program.
If I program it for debugging I get the message:

Code:

Device Erased ...
Programming ...
The following memory area (s) will be programmed:
program memory: start address = 0x0, end address = 0x3ff
configuration memory
Programming / Verify complete
The target device is not ready for debugging. Please check your configuration bit settings and program the device before proceeding. The most common causes for this failure are oscillator and / or PGC / PGD settings.

I have verified that the memory of the dsPIC33EP512GP502 is always written, deleted and read correctly.
Initially I tried the dsPIC33EP512GP502 in a project configured with MCC always getting the same results.
Is there anyone who has any suggestions for me?
I enclose an example with the two configurations.

Thanks in advance

Configuration used:
Windows 10 updated
Pickit3 both original and clone
MPLAB X 5.50 and 6.00
XC16 v1.70 and v2.00 free

[sam_des]

Hi,

I don't use MPLABX much. But AFAIK there is option for "Build for Debugging" as shown in attached image.
I have run into debugging issues, when not activated this option in some cases. I guess 0x0000 flash address is written with something that PICKit requires for debugging.
Also you've to uncheck this option & rebuild for production release.

IMHO, MPLAB  & PICKit are mess, but unavoidable if you want to use Microchip. 

sam_des

[PaoloBi]

Hi, I have tried the various compilation options for debugging but the problem remains, the other PICs work correctly. Thank you.

[kreutz]

Check the oscillator configuration settings, PGC and PGD,  as per the error message recommendations.

[Xwing]

Configuration used:
Windows 10 updated
Pickit3 both original and clone
MPLAB X 5.50 and 6.00
XC16 v1.70 and v2.00 free

check the fuse values, surely those for the clock and the one that enables debugging are wrong.

[PaoloBi]

I looked at the oscillator configuration in the source that I attached to the first post, it seems right to me.
The configuration for the PIckit3 is certainly correct because the PIC memory is programmed, erased and read.

[PaoloBi]

The fuse settings I used are in the source that I attached to the first post (main.c).
There is also the commented configuration for the DSPIC33FJ working correctly.
I don't know Proton, I have installed Proton IDE but I don't have MPLAB 8 to try it, it doesn't seem free to me.

[pickit2]

my post removed as it's of no use to someone who can't read.
.Do include the config bits in your source code. .Do include the config bits in your source code.

[PaoloBi]

I checked the voltage on the VCAP pin and found about 3.3V instead of 1.8V as described in the datasheet.
I find the same voltage on all 3 DSPIC33EPs I have.
Inserting a DSPIC33FJ the voltage is about 2.6V, 2.5V is written in the datasheet.
The DSPIC33EP i I have only used on this test board and I keep swapping the two sets of chips without having any problems on the DSPIC33FJs.

[vovchik02]

Check you conecton ISP pin on PCB. Dspic prorgramming by any PGCx/PGDx pair, for debug fuse set PGD3/PGC3 pair.
 

[PaoloBi]

The connection is fine, this is the first time something like this has happened to me.
Probably the DSPIC are defective, I communicated it to microchip but no answer.
I bought some STM32s, I will use these for the most demanding projects, ... when they arrive I hope everything goes well.