I would add that I had similar problems with the LPC932 a year ago on a project in Texas.

Our problems were similar to problem #2 but seemed to sporadically modify the contents of EEPROM where we had saved configuration data. It tooks us many, many development and debugging hours to figure out that the problem wasn't with my code but with the part itself. I actually had to write a rather complex checksum routine to checksum EEPROM every time we updated it so that when the chip was reset we could at least detect whether or not the EEPROM was corrupt. That was mostly just to prove the problem was with the part, not with my code.

We never got an adequate resolution from Philips.

Regards,
Craig Steiner