I am currently working on a Kria KV260 preloaded with PYNQ that must now remain on a local host as the only connection for use of jupyter notebooks. Because of this, when looking to source the .bit and .hwh files from the composable overlay git repo (PYNQ_Composable_Pipeline/boards/KV260 at main · Xilinx/PYNQ_Composable_Pipeline · GitHub) I realised I cannot simply clone the repository and run the makefile. Is there anyone who has the .bit and .hwh files available so that I could get up to running on my kria with out having to activate the network, install vivado and clone the repo?
That perfect thank you.
Am I correct in saying that the ‘cv_dfx_3_pr.bit’ is the only bitstream I need to load into Jupyter to get the composable overlay notebooks working?
i.e. the long list of bit files such as ‘cv_dfx_3_pr_composable_pr_1_dilate_erode_partial.bit’ are all components held within the ‘cv_dfx_3_pr.bit’ ?
Can I clone the composable overlay github page to get the notebook folders into my jupyter quickly? or do I have to manually download and drag and drop into jupyter.
Never worry, I got the repository cloned following the info on the composable overlays front page and it adds the composable overlay folder to your jupyter directory
On the github page it details that " To rebuild the composable pipeline you need Vitis and Vivado 2020.2. Navigate to one of the supported boards folder and run make , only steps for Linux are provided."
When it says rebuild does this mean that to build your own adaptation of the composable pipeline requires vivado and vitis,? what is actually happening when you run the make file on a board with a linux operating system and vivado installed?
p.s. does it have to be version 2020.2 of vivado and vitis?
i.e. the long list of bit files such as ‘cv_dfx_3_pr_composable_pr_1_dilate_erode_partial.bit’ are all components held within the ‘cv_dfx_3_pr.bit’ ?
The files that contain pr_ and partial in the name are the dynamic reconfigurable portions of the design. The DFX part.
p.s. does it have to be version 2020.2 of vivado and vitis?
I suggest you use the v1.1.0-dev branch. Which is aligned with Vitis 2022.1 and PYNQ 3.0.1. You need both Vitis and Vivado.
When it says rebuild does this mean that to build your own adaptation of the composable pipeline requires vivado and vitis,? what is actually happening when you run the make file on a board with a linux operating system and vivado installed?
For the overlays we provide you do not need to rebuild. But, if you would like to make any change or add a new IP you need to rebuild the full project.
The Makefile encompasses several steps:
Compiles the selected vision functions to an IP using Vitis HLS
Creates the Vivado Project, Block Design, generate bitstreams and partial bitstreams
Copy extra files to the overlay project
Optionally you can zip all up with make zip
This description is at a very high level, each step contains sub steps that are described using TCL.
