??? 03/25/04 14:34 Read: times |
#67417 - Multiple usage of (i.e.) xdata space? |
Hello,
I am currently working on a project that uses the LPC932. Additional to the internal EEPROM, we also have an external serial memory of higher capacity. Finally, we make use of the internal XRAM. I would like to use DS statements for symbol declarations, so the assembler will take care about the addresses. However, since there's only one XDATA space, this arises a few problems... I could define the starting address of each block absolute, i.e. "XDATA AT xxx". This way, the addresses inside of that block are determined by the assembler, but a) the linker reports many collisions, and b) if I want to use the same address space in another module, I would have to care about the starting addresses (and probably would overlook real collisions since the linker reports them anyway). I would have to collect each address space to a set of definitions in one block or file, and use public/extrn to make them accessible to the modules involved. However, this is not very comfortable, from the modular programming point of view. Even then, the linker would always report collisions. How is this problem handled by other developers? How do you deal with more than the existing address spaces supported by existing 8051 development tools? Any feedback is welcome. TIA, Tilmann |
Topic | Author | Date |
Multiple usage of (i.e.) xdata space? | 01/01/70 00:00 | |
RE: Multiple usage of (i.e.) xdata space? | 01/01/70 00:00 | |
OVERLAYABLE | 01/01/70 00:00 | |
RE: OVERLAYABLE | 01/01/70 00:00 | |
RE: OVERLAYABLE | 01/01/70 00:00 | |
RE: OVERLAYABLE | 01/01/70 00:00 | |
RE: OVERLAYABLE | 01/01/70 00:00 | |
RE: OVERLAYABLE | 01/01/70 00:00 | |
RE: OVERLAYABLE, a dirty trick | 01/01/70 00:00 | |
RE: OVERLAYABLE, a dirty trick | 01/01/70 00:00 | |
RE: OVERLAYABLE, a dirty trick![]() | 01/01/70 00:00 | |
RE: Multiple usage of (i.e.) xdata space | 01/01/70 00:00 | |
RE: Multiple usage of (i.e.) xdata space? | 01/01/70 00:00 |