>
> On parts that have multiple EMUD/EMUC pairs (labelled EMUD1/EMUC1,
> EMUD2/EMUC2, etc...) that is not the case.

Very true, that may be the reason they eliminated PGC/PGD on newer
parts. In one of my PIC24EP prototypes, I use EMUD3/EMUC3, I set
appropriate bits in FICD register and I can program and debug from the
same set of pins.


>
> The pair dedicated for programming is unchangable, and is shared by the
> base EMUD/EMUC pair.
>
> I can't believe nobody here has hit this issue before?
>
> I'm beginning to think this is yet another omission in MPLABX, and piece
> of software I'm quickly learning is REALLY crappy in the minds of many
> MPLAB customers.
>
> I might have to just do I2C by software and forgo using the hardware for
> that. It sucks, but MCHIP has been making little missteps like this alot
> lately, so I shouldn't be that surprised.

I'm also struggling with the i2c peripheral libraries provided by
MCHP. Their example is totally incorrect for the PIC24EP/dsPIC33
devices.

Some time ago I found a bug in C30 v3.30 compiler where I had to go
fix the header files for the parts I was using.
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.