Skip to content
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

Update firmware in Xclbin #185

Open
Mellich opened this issue Mar 7, 2024 · 2 comments
Open

Update firmware in Xclbin #185

Mellich opened this issue Mar 7, 2024 · 2 comments
Assignees

Comments

@Mellich
Copy link
Contributor

Mellich commented Mar 7, 2024

This may not be directly related to ACCL itself but I found this old script in the test directory which seems like it was used to update the ACCL firmware in an existing bitstream: test/host/debug/update_xclbin_fw.sh

I updated the updatemem call to make it work with my bitstreams and now the script seems to run fine.

updatemem -force --meminfo descriptor.mmi --data $3 --bit bitstream.bit --proc level0_i/ulp/ccl_offload_0/ccl_offload_bd_i/cclo/control/microblaze_0 --out bitstream_updated.bit

However, when I try to program the FPGA with the updated bitstream, XRT will timeout.
Did anyone get this working with the recent dev branch or is this updatemem workflow inherently broken (with XRT)?

@quetric
Copy link
Collaborator

quetric commented Mar 19, 2024

@Mellich what shell are you targeting? I haven't checked that script for a long time and TBH i don't remember which shell it was written for. The path to the microblaze instance will change for different shells, while the script doesn't check shell version. This might cause the bitstream to become invalid.

@quetric quetric self-assigned this Mar 19, 2024
@Mellich
Copy link
Contributor Author

Mellich commented Mar 19, 2024

I use the U280 with xilinx_u280_gen3x16_xdma_1_202211_1, Vitis 2022.2, XRT 2.14, and the UDP refdesign . The existing bitstream was synthesized with the same versions. I already modified the path to the microblaze to the path given above based on the output of the extract_mmi script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants