![Intel IXP2400 User Manual Download Page 113](http://html1.mh-extra.com/html/intel/ixp2400/ixp2400_user-manual_2071795113.webp)
Development Tools User’s Manual
113
IXP2400/IXP2800 Network Processors
Developer Workbench
2.13.4
Exporting the Startup Script
To create a text file containing all the commands that the Workbench sends to the Transactor during
simulation startup:
1. On the
Simulation
menu, click
Export Startup Script
.
The
Export Simulation Start Script
dialog box appears.
2. Browse to the folder to save the file.
3. Type the name of the script file in the
File name
box.
4. Click
Save
.
The default .ind file extension for script files is added to the name that you typed. See
to insert the script file into the project.
2.13.5
Changing Hardware Options
2.13.5.1
Specifying Hardware Startup Options
To specify whether or not the Workbench loads microcode when hardware debugging is started:
1. On the
Hardware
menu, click
Options
.
The
Hardware Options
dialog box appears.
2. Click the
Startup
tab (see
3. Select or clear the action that you want the Workbench to take when it connects to the
hardware:
— Reset the microengines and load the microcode
This option causes the Workbench to reset the Microengines and then load microcode into
all the assigned Microengines. The Microengines are left in a paused state from which you
can start or step them.
— Assume microcode is already loaded and microengines are running. (Don’t reset the
microengines and don’t load the microcode.)
This option causes the Workbench to connect only to the debug library on the Intel
XScale
®
core. The Microengines are not affected in any way. This would be useful if you
want to connect to a running system to examine its state.
4. Click
OK
.
If you choose not to have the Workbench load microcode automatically at startup, you can:
•
Load microcode manually by selecting
Load Microcode
on the
Debug
menu.
(You can also click the
button. This button is not on the default
Build
menu. To put this
button there, see