Echelon FTXL - Manual (Page 122)

110 Working with the Nios II Development Environment
• The application itself, including implementations of the event handler
functions and callback handler functions of the FTXL LonTalk API.
• The FTXL non-volatile data driver. You can modify the driver from the
example applications.
• The FTXL operating system abstraction layer. You can modify the FTXL
OSAL from the example applications to provide support for an operating
system other than the Micrium μC/OS-II operating system or to change
the settings for the operating system.
• The FTXL hardware abstraction layer. If your FTXL device’s hardware
differs from the design recommendations in the FTXL Hardware Guide ,
you might need to modify the FTXL HAL. To debug the FTXL HAL, you
should run the FTXL Bring-Up application, which is described in the
FTXL Hardware Guide .
To debug the application from the Nios II IDE:
1. Ensure that the FPGA device board is powered on and that a device
programmer (such as a USB-Blaster download cable) is connected to the
board’s JTAG header connector.
2. Start the Nios II IDE.
3. Right-click the FTXL application project from the Nios II C/C++ Projects
pane and select Debug As → Nios II Hardware. The Nios II IDE
recompiles the project, and opens the Debug perspective.
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, follow the procedure listed
under step 5 on page 109, described in Running the Application on page
108.
6. The Nios II IDE halts the application at the first executable statement.
You can step into the code, step over functions, or run the application to a
breakpoint.
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.