Missing files on Vitis HLS backend deployment

[Viggo-Avila]

Apologies for this long post.

From the tutorials, Vivado HLS was used. In my case since I only have Vivado 2024.1, Vitis HLS is the one needed to be used.

I've already changed the code according to the methods I will use (Backend for Vitis and Pynq-Zu for FPGA).

`import hls4ml
import plotting

config = hls4ml.utils.config_from_keras_model(model, granularity='name')
config['LayerName']['softmax']['exp_table_t'] = 'ap_fixed<18,8>'
config['LayerName']['softmax']['inv_table_t'] = 'ap_fixed<18,4>'
for layer in ['fc1', 'fc2', 'fc3', 'output']:
config['LayerName'][layer]['ReuseFactor'] = 64
print("-----------------------------------")
plotting.print_dict(config)
print("-----------------------------------")
hls_model = hls4ml.converters.convert_from_keras_model(
model,
hls_config=config,
output_dir='model_3/hls4ml_prj_pynq',
backend='Vitis',
board='pynq-zu'
)
hls_model.compile()`

I already have used pip install for the pynq-zu according to another post regarding the usage of pynq-zu for hls4ml. here

I've changed the backend to Vitis because that's what they said here

when I run the code above, this comes out:
TypeError: VivadoBackend.create_initial_config() got an unexpected keyword argument 'board'

So, my solution for this was to change the board = 'pynq-zu' into part = 'xczu5eg-sfvc784-1-e' which is the part for PYNQ-ZU. I ran it and it worked (well, I didn't get an error message so it worked ig)

And here comes the bit about the missing files, When I get to the part I need to run this !sed -n '30,45p' model_3/hls4ml_prj_pynq/myproject_vivado_accelerator/project_1.runs/impl_1/design_1_wrapper_utilization_placed.rpt

I get this message sed: can't read model_3/hls4ml_prj_pynq/myproject_vivado_accelerator/project_1.runs/impl_1/design_1_wrapper_utilization_placed.rpt: No such file or directory

So I checked my directories and there was no myproject_vivado_accelerator directory, so I instead looked for the .rpt file. There was no .rpt file

But I kept on going with the tutorial and when I reached the part where I had to archive the files into a .tar.gz. I got this message
cp: cannot stat 'model_3/hls4ml_prj_pynq/myproject_vivado_accelerator/project_1.runs/impl_1/design_1_wrapper.bit': No such file or directory cp: cannot stat 'model_3/hls4ml_prj_pynq/myproject_vivado_accelerator/project_1.srcs/sources_1/bd/design_1/hw_handoff/design_1.hwh': No such file or directory ./ ./y_test.npy ./X_test.npy ./axi_stream_driver.py ./part7b_deployment.ipynb

Send help please ;~;

[vloncar]

There are Vivado, VivadoAccelerator and Vitis bakends (among others), but not yet VitisAccelerator (coming soon though). Meaning to do the accelerator part as instructed by both the documentation and tutorial, you currently need older Vivado suite.

[Viggo-Avila]

I've done the importing of the pynq-zu files to the main hls4ml 1.0.0, it's been working but when I get to the 7a tutorial the problem is that the kernel suddenly shuts down. I'm still trying to fix it, maybe it has something to do with my dependencies.

I haven't yet completed fully the Vivado compatibility with the pynq-zu but if I get through this tutorial I'll let yall's know.

[Viggo-Avila]

Omg I don't know what happened but I only followed what the forums were saying and now these code:

`import numpy as np

X_test = np.load('X_test.npy')
y_hls = hls_model.predict(np.ascontiguousarray(X_test))
np.save('model_3/y_hls.npy', y_hls)`

The kernel for this part dies and restarts, even though it never had any problems before. I thought it had something to do with numpy but previous tutorials also used numpy and they never had any problem.

Man.

[bo3z]

Without a full crash log it's hard to help tell what it could be.

[Viggo-Avila]

IT WORKS NOW OMG I DONT KNOW WHAT I DID BUT I DID SOMETHING.

From the start of this discussion I have:

Gave up trying to replace vitis hls backend for the vivado accelerator backend part and just stuck with vivado accelerator
because of this I installed 2 versions of vivado, 2020.1.1(for the vivado accelerator) and 2024.1 (for the vitis backend)
Made sure that for both the versions of vivado my fpga board is recognized. For 2020.1 I had to put the board files into the board files directory and then made that the board repository for that version.
because of this everytime I use tutorials part1-4 I have to source it to 2024.1 vitis hls
and if I want to use tutorial part7 i have to source it to 2020.1 vivado
added the command of making the board repository the default repository by adding it to the vivado_init.tcl file which I first had to make, thanks for that advice btw.
Made sure that hls4ml recognizes pynq-zu, by modifying the supported_boards.json and adding the other files in the pynq-zu branch into the hls4ml main branch
Also since my hls4ml is having issues with y_hls = hls_model.predict(np.ascontiguousarray(X_test)) and I saw from a separate discussion that downgrading it to hls4ml==0.8.0 works, I did just that and it did work. Though I don't know why it would stop working since previously it always worked.
With regards to the missing files, they just suddenly worked when I did all the things above mentioned. I'm not sure if that's everything I did or I missed some parts of it but it works now YIPPEEEE!!!! Thank you very much for the helpppp.

[bluemoon0321]

IT WORKS NOW OMG I DONT KNOW WHAT I DID BUT I DID SOMETHING.

From the start of this discussion I have:

Gave up trying to replace vitis hls backend for the vivado accelerator backend part and just stuck with vivado accelerator because of this I installed 2 versions of vivado, 2020.1.1(for the vivado accelerator) and 2024.1 (for the vitis backend) Made sure that for both the versions of vivado my fpga board is recognized. For 2020.1 I had to put the board files into the board files directory and then made that the board repository for that version. because of this everytime I use tutorials part1-4 I have to source it to 2024.1 vitis hls and if I want to use tutorial part7 i have to source it to 2020.1 vivado added the command of making the board repository the default repository by adding it to the vivado_init.tcl file which I first had to make, thanks for that advice btw. Made sure that hls4ml recognizes pynq-zu, by modifying the supported_boards.json and adding the other files in the pynq-zu branch into the hls4ml main branch Also since my hls4ml is having issues with y_hls = hls_model.predict(np.ascontiguousarray(X_test)) and I saw from a separate discussion that downgrading it to hls4ml==0.8.0 works, I did just that and it did work. Though I don't know why it would stop working since previously it always worked. With regards to the missing files, they just suddenly worked when I did all the things above mentioned. I'm not sure if that's everything I did or I missed some parts of it but it works now YIPPEEEE!!!! Thank you very much for the helpppp.

hi @Viggo-Avila i'm facing the same problem, the predict part dies and the next cell with the same "can't find board" text.
can you tell me more about the "vivado added the command of making the board repository the default repository by adding it to the vivado_init.tcl file which I first had to make, thanks for that advice btw.
Made sure that hls4ml recognizes pynq-zu, by modifying the supported_boards.json and adding the other files in the pynq-zu branch into the hls4ml main branch" part?
I don't really understand what is the first vivado_init.tcl file doing, and how to make sure hls4ml recognizes pynq-z2, I cant find the supported_boards.json etc.
thanks

[bluemoon0321]

oh I think i got the pynq-z2 board files in the vivado, but I encounter another problem like the picture

saying : ERROR: [BD 5-390] IP definition not found for VLNV: xilinx.com:hls:myproject_axi:1.0
I see that @Viggo-Avila you face this problem too in the issue , but I didnt see any solution, do you figure out how to solve it?
thanks!

[Viggo-Avila]

Yeah. you can't do Vitis HLS on part 7 of the tutorials. I had to install another vivado version for that. and for the vivado_init.tcl file, i used that for the vivado 2020.1 version since it won't automatically refer to the boardrepo paths i want it to refer. There's a discussion about that in the internet that's how I found it.

[Viggo-Avila]

for the kernel suddenly dying on the predict part, I changed hls4ml version from 1.0.0 to 0.8.0, but I Think they already changed that issue