Xilinx / Xilinx/Vitis-Tutorials
Broken documentation in Part4-data_center.md
@AnusheelXilinx is already working on this.
Since Jan 2, 2025.
- Dominant language
- C
- Stars
- 1.6k
- Forks
- 627
- PR merge metrics
- No merged PRs in 30d
Description
These lines reference host.cpp in the wrong directory (should be ../src/host.cpp)
https://github.com/Xilinx/Vitis-Tutorials/blob/6cc013da57c88e9aedf09cbcc385a3f78556190f/Getting_Started/Vitis/Part4-data_center.md?plain=1#L60
https://github.com/Xilinx/Vitis-Tutorials/blob/6cc013da57c88e9aedf09cbcc385a3f78556190f/Getting_Started/Vitis/Part4-data_center.md?plain=1#L132
https://github.com/Xilinx/Vitis-Tutorials/blob/6cc013da57c88e9aedf09cbcc385a3f78556190f/Getting_Started/Vitis/Part4-data_center.md?plain=1#L160
Likewise for u250.cfg here
https://github.com/Xilinx/Vitis-Tutorials/blob/6cc013da57c88e9aedf09cbcc385a3f78556190f/Getting_Started/Vitis/Part4-data_center.md?plain=1#L162
u250_hls.cfg doesn't exist. It should be ../src/u250.cfg
https://github.com/Xilinx/Vitis-Tutorials/blob/6cc013da57c88e9aedf09cbcc385a3f78556190f/Getting_Started/Vitis/Part4-data_center.md?plain=1#L134
https://github.com/Xilinx/Vitis-Tutorials/blob/6cc013da57c88e9aedf09cbcc385a3f78556190f/Getting_Started/Vitis/Part4-data_center.md?plain=1#L161
Whenever ./app.exe is invoked, it throws a runtime error because the xclbin file is not in the present directory.
https://github.com/Xilinx/Vitis-Tutorials/blob/6cc013da57c88e9aedf09cbcc385a3f78556190f/Getting_Started/Vitis/Part4-data_center.md?plain=1#L95
https://github.com/Xilinx/Vitis-Tutorials/blob/6cc013da57c88e9aedf09cbcc385a3f78556190f/Getting_Started/Vitis/Part4-data_center.md?plain=1#L142
https://github.com/Xilinx/Vitis-Tutorials/blob/6cc013da57c88e9aedf09cbcc385a3f78556190f/Getting_Started/Vitis/Part4-data_center.md?plain=1#L172
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.