We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello! I am trying to build the kv260_ispMipiRx_vcu_DP platform for Smartcam. I am using this manual for this (https://xilinx.github.io/kria-apps-docs/main/build/html/docs/smartcamera/smartcamera_landing.html#tutorials). I also changed video input from the IAS to the Raspberry Pi connector. But at the step "Integrating the overlay into the Platform" (https://xilinx.github.io/kria-apps-docs/main/build/html/docs/build_accel.html) the program displays an error message about failed timing one of HLS-core.
What do I need to do to fix it? runme.log terminal.txt
The text was updated successfully, but these errors were encountered:
The timing is quite tight on this design. You can change implementation strategies on the kernel to see if it will meet timing. The strategy is set in the following file. https://github.com/Xilinx/kv260-vitis/blob/release-2020.2.2_k26/overlays/examples/smartcam/prj_conf/prj_config_1dpu#L44
Sorry, something went wrong.
@shadivl can this issue be closed?
No branches or pull requests
Hello! I am trying to build the kv260_ispMipiRx_vcu_DP platform for Smartcam. I am using this manual for this (https://xilinx.github.io/kria-apps-docs/main/build/html/docs/smartcamera/smartcamera_landing.html#tutorials).
I also changed video input from the IAS to the Raspberry Pi connector.
But at the step "Integrating the overlay into the Platform" (https://xilinx.github.io/kria-apps-docs/main/build/html/docs/build_accel.html) the program displays an error message about failed timing one of HLS-core.
What do I need to do to fix it?
runme.log
terminal.txt
The text was updated successfully, but these errors were encountered: