>>This comment "something went wrong" seems to imply that the
>>current state, that leads to i2cErr has no meaning there and
>>in fact should never happen; it appears to be confirmed by the
>>pathetic attempt to have the watchdog reboot the PIC by
>>executing a goto $ instruction...
>>
>
>Out of interest what is pathetic about the attempt to deliberately fire a
>watchdog timeout by using an infinite loop?  Surely you agree that it is
>good practice to trap invalid states such as this?

It also pays to bear in mind that this code does nothing other than handle
the I2C. The received data goes nowhere, it is "just" example code that will
perform correctly on an I2C system.

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics