In a separate Thread [1], Steve Knapp wrote:
PDATA: A way to access XDATA and 256 pages of 256 bytes each. I'm not going into much detail on purpose.

Aha! Someone from Triscend who understands PDATA!?

Can you explain the references in Triscend Application Note AN07, Using Keil Development Tools with Triscend FastChip and the E5 CSoC Family which say,

"This memory type [PDATA] is not recommended on the Triscend E5."

and,

"This model [Compact] is not recommend for E5 CSoC applications. Use the large memory model instead."

and,

"the compact model is awkward on the E5 CSoC."

Why is PDATA deprecated on the E5?

I presume that the deprecation of the Compact Memory Model is a direct result of this deprectaion of PDATA - but, again, why?

Why is the Compact Memory Model particularly awkward on the E5?
I can see why one might say that PDATA - or at least Keil's implementation of it - is awkward on any 8052, but why should this be particularly so on the E5?

[1] http://www.8052.com/forum/read.phtml?id=16089&top=