After you convert the floating-point data types in your design to fixed-point, move the design to the FPGA in SystemDesigner, call it from your FPGA application, test the system components and the overall system, and make any necessary adjustments to meet the specifications of your hardware device.
FPGA VIs serve as the container for all code that runs on an FPGA, so when you integrate the FPGA code, you integrate it into an FPGA VI or into a Clock-Driven Logic document called from an FPGA VI. Designate a top-level FPGA VI within an Application document (.gcomp) that represents a bitfile. The top-level FPGA VI serves as the container for your overall FPGA application. Place all of the code that makes up your FPGA application either directly on the diagram of the FPGA VI, or within subdocuments located on the diagram of the FPGA VI. This code can include Clock-Driven Logic and Optimized FPGA VIs. If you are using a project template, the FPGA VI that you add your design to may be one of the VIs in the project template.
The following resources provide information to help you integrate the pieces of your system.
Use a Project Template—Project templates provide common application architectures using well-established industry design patterns that you can modify to quickly build a working system. When you are ready to integrate your design into an FPGA application, consider adding your design to a project template.
Language Integration in LabVIEW—You can use multiple programming languages to develop your application. How you integrate pieces of code written in different languages into your overall application depends on the language and the target you are integrating the code into.
Optimized FPGA VIs in Other Document Types—When you integrate an optimized FPGA VI into your FPGA application, you can call the optimized FPGA VI from Clock-Driven Logic.
Clock-Driven Logic—Clock-Driven Logic is the primary language on the FPGA. Clock-Driven Logic allows you to integrate the pieces of your application, optimize your FPGA code, and communicate with system resources.
Using Handshaking to Ensure Valid Data in a Clock-Driven Loop—When you integrate code into Clock-Driven Logic, use a handshaking protocol to ensure valid data transfers to and from code that requires more than one clock cycle to return valid data.
Search within the programming environment to access the following lessons: Deploying an Application on an FPGA
System and Component Testing
Testing and adjusting your system components before integrating into your system saves you time and effort when you test your entire system.
Component testing allows you to ensure that each component, or complex portion of code that relies on the timing of the system, works as you expect and reduces the amount of troubleshooting your application requires at the system level. System testing helps you identify any necessary adjustments you need to make to ensure your system runs properly.
The following resources provide information to help you test your system and its components.
Strategies for Testing FPGA Applications—Use these strategies to identify and test your system and its components.
Optimized FPGA VIs and Resource Utilization on the FPGA—After you create an optimized FPGA VI, estimate the FPGA resources that the algorithm requires using the resource estimation tools. Estimating resources helps you determine whether your optimized FPGA VI will run successfully on the FPGA.
Testing a Clock-Driven Logic Document on the Host—To test that a Clock-Driven Logic (CDL) document processes data as you expect, use the Run FPGA Simulation node in a testbench to simulate running the CDL document on an FPGA. You can use the same procedure to test an optimized FPGA VI if you place the optimized FPGA VI in a CDL document and simulate that CDL document.
Testing Communication between the Host VI and an FPGA VI—To ensure your system application will run as you expect it to on an FPGA, use the FPGA Host Interface nodes in a testbench to simulate how your code will run on an FPGA.