- Newest
- Most votes
- Most comments
Hello, by any chance have you tried clearing/resetting the FPGA with the 'fpga-clear-local-image' command, then rerunning the executable to reload it?
https://github.com/aws/aws-fpga/blob/master/sdk/userspace/fpga_mgmt_tools/README.md
The tutorial mentioned just runs the host executable, so there shouldn't be a need to add the *.awsxclbin as an argument as it should be pulled in by the host code.
Another thing to note while clearing the slot is that you will have to restart the mpd service after doing that.
sudo systemctl restart mpd
This lets XRT load the default AFI to be able to bind the XOCL driver to the correct device ID.
-Deep
We use Amazon FPGA Image (AFI) for the binary that is loaded on the FPGA.
It is the compiled FPGA code that is loaded into an FPGA in AWS for performing the Custom Logic (CL) function created by the developer. AFIs are maintained by AWS according and associated with the AWS account that created them. The AFI includes the CL and AWS FPGA Shell. An AFI ID is used to reference a particular AFI from an F1 instance.
An awsxclbin includes the AFI which makes it different from xclbin. Here is the step where it is created documented in our end-to-end guide:
https://github.com/aws/aws-fpga/tree/master/Vitis#createafi
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 5 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago