-
Notifications
You must be signed in to change notification settings - Fork 18
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
Error while building accelerator for KR260 - device tree overlay blob generation #62
Comments
see Xilinx/KRS#62 Signed-off-by: Víctor Mayoral Vilches <[email protected]>
Updated comment above with a workaround that should unblock those testing things out. For a complete fix, refer to ros-acceleration/acceleration_firmware_kr260@af069d8. This needs to be further validated and fully tested but once ready, it should be released, and that should do. |
Updated again with a more detailed walkthrough on how to apply the workaround. |
Hi @vmayoral Thanks for the workaround. I will clean up my workspace and follow it. Meanwhile, I tested the complete fix and I am seeing the below error while the building accelerator for KR260
colcon seems to be looking into data folder which doesn't exist in the acceleration firmware. I created a empty data directory in the specified location and then the build worked fine. I also observed that the platform is missing in kr260 firmware. I used the platform from kv260 firmware for this build. |
@mohammedrafi-sk I don't seem to be able to reproduce the error you described after another attempt, moreover the original intent of this ticket was to reflect the workaround needed with KR260 and Ubuntu 22.04 accelerators. Objective was fulfilled and confirmed (triple-checked) at #67. Closing. |
I caught a weird error while re-running things in a clean workspace with the KR260:
Description
The KR260 KRS v1.0.0 firmware is built minimalistic and ships as little as possible. While building accelerators, the CMake logic attempts to produce all necessary artifacts (besides the accelerator itself) including the
.dtbo
file and theshell.json
files necessary to run things on top oflibdfx
. This can be tracked down to https://github.com/ros-acceleration/ament_vitis/blob/main/cmake/vitis_acceleration_kernel.cmake#L357-L372. As things are, the accelerator will be successfully built but the CMake logic will fail because it won't find necessary files to complete the process.Reproduction of the issue
To reproduce this issue, in a clean ROS 2 workspace with KR260 as explained at https://xilinx.github.io/KRS/sphinx/build/html/docs/install.html#cross-compilation-development:
colcon build --build-base=build-kr260-ubuntu --install-base=install-kr260-ubuntu --merge-install --mixin kr260 --cmake-args -DNOKERNELS=false --packages-select simple_vadd # or any other accelerator
Workaround⚠️
As a workaround, one can fetch into the ROS 2 overlay workspace the resources from KRS KV260 v1.0.0 (from here), build the workspace (deploying the firmware), and then (re)build things:
This will instruct ament and colcon to look into KV260 firmware resources while building accelerators.
The text was updated successfully, but these errors were encountered: