At 00.10 2012.02.10, you wrote:
>
>> In any case, that wasted 5 hours of my life.. and bughunting is not
>> really my favourite sport
>
>Sad to say, when something doesn't work as expected I more often
>these days suspect the silicon. And it unfortunately that turns out to
>be exactly the cause too many times. Point it out to Microchip, with
>proof, and they don't (or choose not to) believe you

Another thing that may happen (and it happened to me in the last months
3 times!) is that I damaged inadvertently the MPU, and then it didn't work
well (I had one misbehaving dsPIC2011 which I didn't even know how I broke
it, and two PIC32MX120F032B which both gave bad analog readings on a pin, I
strongly hypotize that was because at a certain time my code maybe was
turning that pin to output fighting electrons with a low impedance analog
circuit supposedly driving the same pin).

What I mean is that in any case, be it a silicon bug (after all Microchip
can't know them in advance: we users point the bugs out, and they (maybe,
as You say, not listening enough to single users.. but when they get many
reports they sure do) verify it and put it in the errata sheet), or a
possibly damaged IC, one of the first things I do when some code doesn't
behave as I think it should, and the frustration begins, is to swap the
physical chip with a fresh new unused one. Of course this works best with
socketed DIP parts, as sockets on SMD parts are rare, and soldering/desolde=
ring
them is very stressful at least on hand made PCB's.

Cheers,
Mario

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