> Thank you for your kind answer: I am not requesting help at
> that level, because I have had a full 26 years to debug
> microprocessor apps starting with things like 8080, 6800 and
> 6809.
>
> At the moment I am looking for something really elusive, and
> I am specifically searching for a source of inspiration that
> would help me discover whether it is me, the compiler and
> relevant interrupt routines, the litterature, or the stupid
> silicium that is the problem.
>
> So far and with help of an oscilloscope I have been unable
> to eliminate any of these four potential culprits (PIC
> silicium has had bugs in the MSSP for some revisions and
> chips, Microchip documentation has had flaws, Application
> notes code my Microchip have bugs etc),

hang on a minute. Are you really telling us that the code in Microchip
Application Note AN734 doesn't work? I used this code to make my interrupt
driven I2C slave module quite satisfactorily. If you have a look in the
PICList archive for messages with the subject line "I2C Troubles" you will
find all the info you need on this.

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu