Echelon FTXL - Manual (Page 121)

FTXL User’s Guide 109
4. If you have a valid Nios II development license, and have already loaded
the configuration data (the JTAG Indirect Configuration (*.jic) file or
SRAM object file (*.sof)) into the FPGA device, proceed to step 6.
5. If you do not have a valid Nios II development license, or have not loaded
the configuration data into the FPGA device:
a. The Nios II IDE displays the following text in the Console
window:
There are no Nios II CPUs with debug modules available which
match the values specified. Please check that your PLD is
correctly configured, downloading a new SOF file if necessary.
b. The Quartus II Programmer window opens.
c. In the Quartus II Programmer window, click Add File to open the
Select Programming File dialog.
d. In the Select Programming File dialog, select the appropriate
SRAM object file (*.sof) file for the project, and click Open.
e. Ensure that a device programmer (such as a USB-Blaster
download cable) is defined in the Chain Description File for the
project.
If you have not defined the USB-Blaster download cable in the
Chain Description File for the project, click Hardware Setup. See
Using a Device Programmer for the FPGA Device on page 103 for
more information about setting up the device programmer.
f. Select the Program/Configure checkbox for the *.sof file.
g. Click Start to load the selected *.sof file into the Nios II processor.
h. Do not close the Quartus II Programmer window. You must leave
this window open while you are running the application.
i. Return to the Nios II IDE, right-click the FTXL application
project from the Nios II C/C++ Projects pane, and select Run As
→ Nios II Hardware. The Nios II IDE recompiles the project.
6. Your application should run. It should include some visual indication
within the Nios II IDE that it is running, such as by displaying text in
the Console window or blinking an LED on the device board.
To verify that the application runs as expected, connect the FTXL device to a
L
ON W ORKS network, and commission it using a network management tool, such
as the LonMaker Integration tool.
Recommendation: Use the generated *.xif file when you commission your FTXL
device, rather than performing ad-hoc network installation. Ad-hoc network
installation for a device can require much more time to commission the device
than when you use a *.xif file.
Debugging the Application
You debug an FTXL application in the same way as any other C application for
the Nios II processor. There are four main areas to consider while debugging an
FTXL application: