By default, the .
select Single processor or Multiprocessor
• For a single-processor system, the Processors list shows only one
processor and the MP address columns do not appear.
• For a multiprocessor system, right-click in the Processor Proper-
ties box to add the desired number of processors to be included in
the .
LDF
which will determine each processor's MP memory address range.
Processor type identifies the DSP system's processor architecture. This
setting is derived from the processor target specified via the Project
Options dialog box in VisualDSP++.
If you select Set up system from debug session settings, the processor
information (number of processors and the processor names) will be filled
automatically from the current settings in the debug session. This field is
grayed out when the current debug session is not supported by the Expert
Linker.
You can also specify the Output file name and the Executables to link
against (object libraries, macros, and so on).
When you select a processor in the Processors list, the system displays the
output file name and the list of executable files to link against for that pro-
cessor appear. You can change these files by typing a new file name. The
file name may include a relative path, an LDF macro, or both. In addition,
if the processor's ID is detected, the processor is placed in the correct posi-
tion in the processor list.
For multiprocessor (MP) systems, the window
of processors in the project. The Expert Linker automatically displays MP
address range for each processor space providing specific MP addresses
and multiprocessor memory space (MMS) offsets which makes the use of
MP commands much easier. This is an automatic replacement for the
linker command used in the LDF source file.
MPMEMORY
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors
file is set for single processors. Under System type,
LDF
file, name each processor, and set the processor order,
Expert Linker
(Figure
4-5) shows the list
4-7
Need help?
Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?