Intel IXP2400 User Manual page 55

You do not have to type the .uof extension—the Workbench adds it for you. Typing it does no
harm.
4. Click Select.
Microengine .list file selection
The project has one or more .list file(s) generated
using the Assembler or Compiler. On the Linker page
you can control which .list file is linked into the .uof
file and for which Microengine.
To do this:
1. Click the list box to the right of Microengine 0:0.
A scrollable list of list files is displayed.
2. Select either:
a. <none>, or
b. Any .list file from list.
3. Do the same for remaining Microengines.
This method allows you to select any combination of .list files or no .list file for any or all the
Microengines to be linked to the .uof file.
If you specify <none>, no microcode gets loaded into that Microengine. If you select <none> for
all the Microengines, you get an error.
Produce debug information
Select Produce debug info to add debug information to the
output file. If you do not select this option, you will not be
able to open a thread window in debug mode.
Note: The Produce debug info switch must be set for the necessary debug information to be present in
the uof file. Unchecking the Produce debug info check box causes the size of the uof file to be
smaller at the expense of the project not being debuggable (in any fashion) through the Workbench
Generate memory-map file
Select Generate memory-map file to have the
Workbench pass the -map option switch to the linker to
generate a .map file. The file contains the symbols and
their addresses. The edit control allows the user to
specify the filename or browse to it.
Hex ".c" files
Select Generate hex '.c' file to request the Linker to create a *.c file, with the same name as the
corresponding *.uof file. This file contains a microcode listing in a form that can be included in a
processor core application. This is usually done when deploying microcode into a final product.
Development Tools User's Manual
IXP2400/IXP2800 Network Processors
Developer Workbench
55