??? 03/22/04 18:12 Read: times |
#67204 - RE: Begin at the beginning! Responding to: ???'s previous message |
thanks
actually it always allocates PDATA first, then followed by XDATA, but they are always grouped in sequence. it makes sense, since the initialization routine at startup.a51, required us to define the starting and the len of each memory types (must be in continuous sequence). you are right, i can fool the compiler that my xdata start at 0x2100. the solution would be fine if we always put pdata at the first page of ram. but the book says pdata page can be allocated anywhere in the 64k xram. as i mentioned before i think i took the concept of this pdata incorrectly. if i tell the the compiler my pdata start base, and the compiler knows that it's only 256 bytes, doesn't mean it will allocate the whole page for pdata type. just like data and idata, they share one memory class. well, it may be easy for an expert to have such a thought, but for me, i still don't have enough confidence to be sure that i have done all the necessary settings correctly. regards. ab |
Topic | Author | Date |
keil pdata | 01/01/70 00:00 | |
Begin at the beginning! | 01/01/70 00:00 | |
RE: Begin at the beginning! | 01/01/70 00:00 | |
RE: Begin at the beginning! | 01/01/70 00:00 | |
RE: Begin at the beginning! | 01/01/70 00:00 | |
RE: Begin at the beginning! | 01/01/70 00:00 | |
RE: Begin at the beginning! | 01/01/70 00:00 | |
RE: Begin at the beginning!![]() | 01/01/70 00:00 | |
RE: keil pdata | 01/01/70 00:00 | |
RE: keil pdata | 01/01/70 00:00 | |
RE: keil pdata | 01/01/70 00:00 | |
RE: keil pdata | 01/01/70 00:00 |