Visible to Intel only — GUID: mwh1391807008668
Ixiasoft
1. Intel® FPGA SDK for OpenCL™ Pro Edition Custom Platform Toolkit User Guide
2. Intel® FPGA SDK for OpenCL™ Pro Edition Custom Platform Toolkit Reference Material
3. Intel FPGA SDK for OpenCL Pro Edition Custom Platform Toolkit Archives
4. Document Revision History for Intel® FPGA SDK for OpenCL™ Pro Edition Custom Platform Toolkit User Guide
1.1. Prerequisites for the Intel® FPGA SDK for OpenCL™ Pro Edition Custom Platform Toolkit
1.2. Overview of the Intel® FPGA SDK for OpenCL™ Pro Edition Custom Platform
1.3. Custom Platform Automigration for Forward Compatibility
1.4. Creating an Intel® FPGA SDK for OpenCL™ Custom Platform
1.5. Applying for the Intel® FPGA SDK for OpenCL™ Pro Edition Preferred Board Status
1.6. Shipping Recommendations
2.3.1. aocl_mmd_get_offline_info
2.3.2. aocl_mmd_get_info
2.3.3. aocl_mmd_open
2.3.4. aocl_mmd_close
2.3.5. aocl_mmd_read
2.3.6. aocl_mmd_write
2.3.7. aocl_mmd_copy
2.3.8. aocl_mmd_set_interrupt_handler
2.3.9. aocl_mmd_set_device_interrupt_handler
2.3.10. aocl_mmd_set_status_handler
2.3.11. aocl_mmd_yield
2.3.12. aocl_mmd_shared_mem_alloc
2.3.13. aocl_mmd_shared_mem_free
2.3.14. aocl_mmd_program
2.3.15. aocl_mmd_reprogram
2.3.16. aocl_mmd_hostchannel_create
2.3.17. aocl_mmd_hostchannel_destroy
2.3.18. aocl_mmd_hostchannel_get_buffer
2.3.19. aocl_mmd_hostchannel_ack_buffer
2.3.20. aocl_mmd_host_alloc
2.3.21. aocl_mmd_free
2.3.22. aocl_mmd_device_alloc
2.3.23. aocl_mmd_shared_alloc
2.3.24. aocl_mmd_shared_migrate
Visible to Intel only — GUID: mwh1391807008668
Ixiasoft
1.4.2.1.1. Testing the board_env.xml File
After you generate the board_env.xml file, test the file within your board installation directory to ensure that the Intel® FPGA SDK for OpenCL™ Offline Compiler recognizes the board installation.
- At the command prompt, invoke the aocl board-xml-test command to verify that the Intel® FPGA SDK for OpenCL™ Pro Edition can locate the correct field values.
The SDK generates an output similar to the one below:
board-path = <path_to_customplatform> board-version = <SDK_version> board-name = <customplatform_name> board-default = <board_name> board-hw-path = <path_to_customplatform>/hardware/<customplatform_name> board-link-flags = /libpath:<path_to_customplatform/windows64/lib board-libs = altera_<customplatform_name>_mmd.lib board-util-bin = <path_to_customplatform>/windows64/libexec board-mmdlib = <path_to_customplatform>/windows64/bin/altera_<customplatform_name>_mmd.dll
- Invoke the aoc -list-boards command to verify that the offline compiler can identify and report the board variants in the Custom Platform.
For example, if your Custom Platform includes two FPGA boards, the SDK generates an output similar to the one below:
Board list: <board_name_1> <board_name_2>
The last board installation test takes place when you use the offline compiler to generate a design for your board.