Shared_Memory - Analog Devices VisualDSP++ 3.5 Manual

Advanced LDF Commands
If you do not want the linker to redirect function calls in overlays, omit
the commands entirely.
PLIT{}
To help you write an overlay manager, the linker generates
constants for each symbol in an overlay.
The overlay manager can also:
• Be helped by manual intervention. Save the target's state on the
stack or in memory before loading and executing an overlay func-
tion, to ensure it continues correctly on return. However, you can
implement this feature within the PLIT section of your LDF.
Note: Your program may not need to save this information.
• Initiate (jump to) the routine that transfers the overlay code to
internal memory, given the previous information about its identity,
size and location:
check whether an overlay function is already in internal memory to
avoid reloading the function.

SHARED_MEMORY{}

The ADSP-2192 DSP is the only ADSP-21xx DSP that supports
SHARED_MEMORY{}
The linker can produce two types of executable output:
files. A file runs in a single-processor system's address space. Shared
.DXE
memory executable (
cessor system. The
files.
If you do not specify the type of link with a
SHARED_MEMORY{}
5-38
_OverlayManager
. All Blackfin processors support this function.
) files reside in the shared memory of a multipro-
.SM
SHARED_MEMORY{}
command, the linker cannot link your program.
VisualDSP++ 3.5 Linker and Utilities Manual
. "Smart" overlay managers first
command is used to produce
PROCESSOR{}
for 16-Bit Processors
PLIT_SYMBOL
files and
.DXE .SM
.SM
or