Actually it was first noticed in the PIC16F627A/-28A. Indeed, part#3 of 
the document below
does describe the problem and Microchip's recommended workaround DOES 
work properly.
Thanks, Tamas!

--Bob A

Tamas Rudnai wrote:
> This issue was mentioned in the 16F627 Errata with a possible workaround:
>
> http://ww1.microchip.com/downloads/en/DeviceDoc/80151M.pdf
>
> Tamas
>
>
> On Fri, Mar 28, 2008 at 7:09 AM, Bob Axtell <engineer@cotse.net> wrote:
>
>   
>> Jinx wrote:
>>     
>>>> Interestingly, he told me that the problem is that the "done" flag
>>>> never gets set, so the code hangs. He doesn't see bad data.
>>>>
>>>>         
>>> I've had bad firmware (I2C for example) flags on some PICs under
>>> certain not unusual and not out-of-spec conditions. I reported this to
>>> Microchip and they confirmed it. Eventually
>>>
>>> Think Bob A has mentioned unreliable flags too
>>>
>>>
>>>
>>>
>>>       
>> Yes, I found some problems in the PIC12F675/629, but I got the
>> workaround from Microchip from
>> another PIC. But Microchip never announced the problem in the
>> PIC12F675/629. I still use the workaround
>> so I don't know if they fixed it or not.
>>
>> --Bob A
>> --
>> http://www.piclist.com PIC/SX FAQ & list archive
>> View/change your membership options at
>> http://mailman.mit.edu/mailman/listinfo/piclist
>>
>>     
>
>
>
>   

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist