Using Overlay Symbols
The loader utility, when running, searches for the
symbols. If the loader cannot resolve the two symbols, it sets
OvlMgrTbl
both values to zero. You must declare one or both symbols in the assembly
source file to make the run-time loader handle the overlay properly.
The
OvlPciAdrTbl
address table. The loader gets this symbol's value from the input
and places it in the "offset" of the first
of the "offset" of the second
the first
relocation_type
Consequently, each subsequent "offset" gets a value equal to the previous
"offset" plus 2. The run-time loader determines the exact the overlay live
address of each overlay according to the provided "offset" value.
Instead of defining
source code. This symbol should contain the start address of the overlay
table, and the overlay table can be declared and defined in your assembly
source code. The loader gets this symbol's value and makes the
statement along with the other
#define CORE0_OVL_MGR_TBL
#define CORE0_OVL_COUNT
The first
#define
This is zero when the loader fails to find the symbol in the input
Correct the value by manually changing the value or by defining it in the
assembly source code and re-building the loader file.
The second
#define
The run-time loader later uses the provided overlay table start address to
find the entry for the live start address each overlay and changes it before
loading the overlay table into DSP memory.
VisualDSP++ Loader Manual
for 16-Bit Processors
symbol holds the start address of the overlay live
relocation_type
"offset" plus 2.
, define
OvlPciAdrTbl
#define
0
3
statement provides the start address of the overlay table.
statement provides the number of overlay for core 0.
ADSP-2192-12 DSP Loader
OvlPciAdrTbl
array. The value
relocation_type
array is then the value of
in the assembly
OvlMgrTbl
statement; for example:
and
file
.DXE
#define
file.
.DXE
4-9
Need help?
Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?