I am going to use the Philips P89C668 which has 64k flash and 8k ERAM. This allow me to use P0 and P2 for I/O since no external memory chip will be connected. However, if the compiler generates code using a MOV P2,# followed by a MOVX @R0 this scheme will be screwed up. Is there a way to "tell" the compiler to keep its little fingers off P2 for MOVX. Erik
That's right. "PDATA" could be defined as "memory accessed via MOVX @Ri" We had similar issues with PDATA on the Triscend E5.