Electronic – MPLAB 8: Hotkey for “Program Target Device”

The PIC may have been told to 'raise its shields' or may have been programmed to not respond to the programmer clock or oscillator control network. These problems are usually recoverable by following a suitable path. A circuit diagram of your target application may be useful.

Without looking at your specific PIC:

You may have code protection set.
The device should be able to be erased with code protection set.

You may have selected a clock type that the programmer does not support.
Worst case if it is not seeing your programmer clock or crystal you may have to uses ICSP with the PIC in a breadboard and supply a clock source or crystal or resonator or RC network or whatever that allows the PIC to run so it can listen to the programmer well enough to find its way home.

There is a small chance that it has been damaged in the process and is irrecoverable. Be sure to use adequate anti-static precautions and correct operating voltages, insert and remove with power off, ensure that no signal levels exceed absolute maximum values.

In order to use the debugger the debugging signals must be configured to communicate on the correct PGEC / PGED pair of pins. It's hard to find in the chipKIT Uno32 manual which pins are used for the programmer header, but it is a little easier referring to the schematic.

From that schematic we can see that the programming header uses pins RB6 and RB7. Looking at the data sheet for the PIC32MX320F128H chip those pins are PGEC2 and PGED2.

However, in your configuration, you have:

# pragma config = ICESEL ICS_PGx1 / / ICE / ICD Comm Channel Select

That will be attempting to communicate on PGEC1 and PGED1, which are pins RB0 and RB1.

If you change that to:

# pragma config = ICESEL ICS_PGx2 / / ICE / ICD Comm Channel Select

then you should find that debugging works.