Dear Forum Members,

I have been using Philips Chips for a long time now. The problems started the day started using P89LPC922 the first bad experience I had was the philips website saying the device has 2 ADC's I posted here and latter they removed these erronrneous specifications from there website.

The second problem I faced was with the reset of these LPC9xx the 0.2V problem if my customers turn off and then on too fast some times the micro doesnt get internal reset and equipment doesnt start.

The third problem I faced today....
I was trying to use NOTOUCH for LPC922 I wrote following code to change the status byte and make micro ready for ISP.

$NOMOD51
NAME NOTOUCH922
PGM_MTP EQU 0FF00H

?PR?no_touch922?NOTOUCH922	SEGMENT CODE
	PUBLIC no_touch922

	RSEG ?PR?no_touch922?NOTOUCH922

no_touch922:

MOV 0A8H,#00H			; Disable Interrupts
MOV R0,#0FFH			; IAP authorization key.
MOV @R0,#96H
MOV A,#02                       ; IAP Misc. Writing.
MOV R5,#01			; Write status byte with 01h
MOV R7,#03                      ; Status byte modification.
lcall PGM_MTP                   ; CALL IAP Routine
RET
END

I spent complete day changed 5 micros but this NOTOUCH didnt work. I have read LPC922 user manual several times http://www.standardics.philips.com/support/t...2_9221.pdf

It clearly says Making calls to PGM_MTP at FF00H. But it doesnt work. I have LPC924_925 user manual too I read that and found that PGM_MTP at FF03H. At first I thought may be this FF03H is only for LPC924 and not for LPC922 but I had tried everything else so decided to take a chace and changed PGM_MTP to FF03H from FF00H and guess what it worked. Thank god, I could make it work at the end of the day but what purpose do such misleading philips docs server???

Regards,
Prahlad Purohit