Table of Contents
Advertisement
Configuring the Emulator
To map memory ranges that use function codes
When you do this, be sure that all address ranges not mapped (that is, the
"other" memory mapper term) are mapped as target RAM. When "other" is
mapped as guarded, guarded memory access errors (from the attempt to load
the absolute file sections that are outside the specified function code range)
can prevent the absolute file sections that are inside the specified function
range from being loaded.
Attributes include:
•
Interlock to target DSACK—locking emulation memory timing to target
system memory timing.
•
Emulate 8 bit wide memory—setting the memory to 8 bits for processors
that cannot handle the 16-bit emulation memory width.
•
Combined—combining both attributes listed above.
Examples
Suppose you're developing a system with the following characteristics:
•
Input port at 100 hex.
•
Output port at 400 hex.
•
Supervisor program from 1000 through 1fff hex.
•
Supervisor data from 2000 through 2fff hex.
•
User program from 3000 through 3fff hex.
•
User data from 3000 through 3fff hex.
The last two terms have address ranges that overlap. You can use function
codes to cause these terms to be mapped to different blocks of memory.
Suppose also that the only things that exist in your target system at this time
are the input and output ports and some control logic; no memory is
available. You can reflect this by mapping the I/O ports to target system
memory space and the rest of memory to emulation memory space by
entering the following mapper commands using the command line
(Settings→Command Line):
0h thru 0fffh target ram
1000h thru 1fffh supervisor program emulation rom
2000h thru 2fffh supervisor data emulation ram
3000h thru 3fffh user program emulation ram
3000h thru 3fffh user data emulation ram
118
Advertisement
Table of Contents
