Closed
Description
Problem Description
- Following the dev branch workflow, I successfully compiled the SLASH project in HW mode, and generated the corresponding
vrtbinandpdifiles. - However, programming the
pdifile always fails, whether usingvrt::Device device(bdf, vrtbinFile)orami_tool cfgmem_program -d <bdf> -t <type> -i <path> -p <n>. - Initially, I suspected the
--segmentparameter, but removing it did not resolve the issue. - My current ami_tool version is 2.3.0, and all related dependencies and drivers are aligned to this version.
Environment Information
- OS: Ubuntu 22.04, Kernel 5.15
- Accelerator Card: Alveo V80 PQ
- ami_tool version: 2.3.0 (Hash: 0bab29e568f64a25f17425c0ffd1c0e89609b6d1, Build date: 2024-03-07)
- Driver version: 2.3.0
- Due to environment constraints, compilation and programming are done on separate machines:
- The machine with Alveo V80 installed for programming uses Vitis/Vivado 2024.1
- The machine used for compiling the SLASH project uses Vitis/Vivado 2024.2
- According to the AVED official documentation, only Vivado 2024.1 is currently supported (AVED Documentation).
Actual Command Used
sudo ami_tool cfgmem_program -d a1:00.0 -t primary -i /home/bjut316-v80/SLASH/examples/01_aximm/design.pdi -p 0
Terminal Output and Error Log
----------------------------------------------
Device | a1:00.0
----------------------------------------------
Current Configuration
----------------------------------------------
UUID | 3907c6f088e5c23471ab99aae09a9928
----------------------------------------------
Incoming Configuration
----------------------------------------------
UUID | bf0dbb51390393e5f07638c001d5482e
Path | /home/bjut316-v80/SLASH/examples/01_aximm/design.pdi
Partition | 0
----------------------------------------------
Are you sure you wish to proceed? [Y/n]: Y
Updating base flash image...
[####################################################################################################] 100% |
Image programming complete.
Will do a hot reset to boot into partition 0. This may take a minute...
Error: could not select boot partition
ENODEV: No such device [ami_dev_find_next:479].
Note: Running
./01_aximm a1:00.0 01_aximm_hw.vrtbinresults in the program hanging, so no output can be captured.
Main Questions and Requests
- Is the programming failure related to compatibility issues between ami_tool, AVED, and Vitis/Vivado versions?
- If it is a version compatibility issue, does AVED plan to support Vivado 2024.2 in the near future? Are there any recommendations for adaptation?
- If it is not a compatibility issue, please help analyze other potential causes for the
could not select boot partitionandENODEVerrors and provide troubleshooting suggestions. - In theory, programming should succeed when all official deployment requirements are met on the same device. If there are additional considerations, please point them out.
Reference
Thank you!
Metadata
Metadata
Assignees
Labels
No labels