-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime packages #461
Comments
Hi @xlz-jgoutin, this is excellent feedback for us to take back to our development team. This adds a lot of value and ease of use for a runtime environment. I will discuss it with the development team and discuss where we can place it within our development efforts. I'll update here once I have something for you. -Deep |
Thank you so much for the feedback. We will post the future improvements and updates once available. Thanks |
* add support for dram data retention (#414) * Added new github examples for ddr data retention (#426) * Added new github examples for ddr data retention * fixing link to runtime software test * removing temporary & executable file from github * new error codes for data retention (#445) * Enable data retention. (#447) * upgrading data retention branch to devkit 1.4.2 * porting backdoor DDR load & AXI_MEMORY_MODEL simulation features to data retention customer TB for future simulation support. * updating default AFI to a data retention enabled 4-ddr calibration AFI * updating dataretention branch to develop * [2017.4 Data Retention] Backward compatibility (#454) * Load without data retention if load failed If failed for reasons FPGA_ERR_DRAM_DATA_RETENTION_NOT_POSSIBLE, FPGA_ERR_DRAM_DATA_RETENTION_FAILED, or FPGA_ERR_DRAM_DATA_RETENTION_SETUP_FAILED. * Info message Print an info message when load failed data retention. * added data retention documentation (#453) * added data retention documentation * updated data retention docs * Linking to data retention documents from top * refining description of data retention feature * adding asl license header for 2018 * fixing link for now. will add back after merging PR461 * Allow for spaces in a longer header comment * Adding apache headers and updated asl 2018 header * cl_dram_dma example cleanup (#461) * added data retention documentation * updated data retention docs * created fpga_dma library * customer example clean up for cl_dram_dma, plus data retention example * cosim * updated licence headers * cosim-fix * documentation updates for data retention (#462) * doc updates * doc updates * doc updates * doc updates * doc updates * adding sdaccel data retention example * adding license header to Makefile * fixing makefile switches * fixing typo in license header
Please, consider creating .deb/.rpm packages for runtime libraries and utilities (Ex
aws-fpga-mgmt
) for most common OS (Ubuntu/CentOS).Cloning the git and sourcing the script is OK for development environments, but much less for a runtime environment. Using packages may help to:
The package may contain:
Management utilities (Maybe not all if some are not relevant in runtime environment):
/usr/bin/fpga-clear-local-image
/usr/bin/fpga-describe-local-image
/usr/bin/fpga-describe-local-image-slots
/usr/bin/fpga-get-virtual-dip-switch
/usr/bin/fpga-get-virtual-led
/usr/bin/fpga-load-local-image
/usr/bin/fpga-local-cmd
/usr/bin/fpga-set-virtual-dip-switch
/usr/bin/fpga-start-virtual-jtag
Libraries:
/usr/lib64/libfpga_mgmt.so
/usr/lib64/libfpga_mgmt.so.1
/usr/lib64/libfpga_mgmt.so.1.0.0
Udev rule:
sdk/userspace/add_udev_rules.sh
(By example as/usr/bin/fpga-add-udev-rule
)/opt/aws/bin/change-fpga-perm.sh
(Maybe moved to/usr/bin/fpga-change-perm
)Python libraries (Eventually as extra package like
python3-aws-fpga-mgmt
, can also be uploaded as PIP package):<OS dependant path>/fpga_dma.py
<OS dependant path>/fpga_mgmt.py
<OS dependant path>/fpga_pci.py
Eventually, a development package (Example:
aws-fpga-mgmt-dev
deb package /aws-fpga-mgmt-devel
rpm package) may also be created to install include files (from/sdk/userspace/include
) to allow build software without the whole SDK.The text was updated successfully, but these errors were encountered: