-
PYNQ Version: 2.3 (Because I’m using Vivado 2018_R2 and other SW based on it)
-
Using a customized image.
-
Board(s): Zed evaluation board + FMCOMMS2
-
Detailed problem:
-
I’m able to load my own bitstream into PL and work with it in a Python script with PYNQ support on a PYNQ-Z1 board and a Zed evaluation board.
-
I’m able to create a PYNQ-supported image for Zed evaluation board (which has one FMCOMMS2 attached to it).
-
I’m able to create an image by Petalinux with the tools/settings from ADI web site to have FMCOMMS2 being detected and work on Zed evaluation board. In this case, a bitstream generated from ADI HDL is combined into BOOT.BIN and is loaded during boot-up phase.
-
Then, we have one combined image – “BOOT.BIN/image.ub with PYNQ support and ad9361 support and bitstream from ADI HDL” + “PYNQ file system”.
-
Now I’m going to add my own IP (a small design) into that default bitstream from ADI HDL, so I can work with my own IP design in a PYNQ Python script and send data to FMCOMMS2 (ad9361) for transmitting data at the same time (in the same PYNQ Python script).
-
But, in that case, it looks like I will not need use “overlay()” to load bitstream again because that bitstream is supposed to have been loaded and working during the boot-up phase. (Maybe I can load the same bitstream again by “overlay()” in my PYNQ Python script but not sure what will happen for other functions which have been working.)
-
Thus I’m thinking if I can get an object in a PYNQ Python script which identifies the current working HW design in PL (from the bitstream which has been loaded during boot-up phase) w/o loading the bitstream by “overlay()”, and thus I can use it for my following actions in my PYNQ Python script. Would you please advise me how to do it? Or maybe I misunderstand something here. Thx a lot for the advice!
-
Error messages: N/A
-
Steps to reproduce the problem: N/A
-
Detailed steps you have tried to resolve the problem: Checked PYNQ docs but couldn’t find a clear answer about it or maybe I was missing or misunderstood something in the PYNQ docs.