Open lmg260a opened 3 months ago
Hi @lmg260a,
Did you come up with another solution for this?
Yes the command you were trying to execute does indeed require Vivado. (All bazel targets under //hw/bitstream/
are fpga bitstreams, in this case the vivado in the target name means using vivado to build an EarlGrey bitstream for the CW310 board (Kintex K410T) with a test-rom spliced into the image).
Currently we don't support generating scripts that can be run externally for this. Bazel is responsible for invoking fusesoc which then invokes vivado, and this probably won't change in the future. Bazel manages the build flow, so we can't just break outside of that to run certain steps manually unfortunately. If you can install Vivado yourself, one option might be to append the vivado installation to the OpenTitan development container dockerfile, and then Bazel will invoke Vivado in headless-mode when building. There are instructions online on how you can do this.
If this is not possible, could you let me know a bit about your environment restrictions that might make running the OpenTitan flows difficult for you? I can't promise to fix everything, but it helps us anticipate problems. Managing the web of proprietary dependencies and locked-down environments is a continual challenge :)
Re. your original error, there is a missing vivado error way down the STDOUT. I just tested locally, and reproduced the following error...
$ bazel build --sandbox_debug //hw/bitstream/vivado:fpga_cw310_test_rom
...
<snip>
...
ERROR: /home/harry/projects/opentitan/hw/bitstream/vivado/BUILD:39:14: FuseSoC hw/bitstream/vivado/build.fpga_cw310 failed: (Exit 1): linux-sandbox failed: error executing command
(cd /home/harry/.cache/bazel/_bazel_harry/6aecaaad7827b990b88d034b9d0ce702/sandbox/linux-sandbox/665/execroot/lowrisc_opentitan && \
exec env - \
...
<snip ~300 lines>
...
INFO: Building
INFO: vivado -notrace -mode batch -source lowrisc_systems_chip_earlgrey_cw310_0.1.tcl
ERROR: make: vivado: No such file or directory
make: *** [Makefile:8: lowrisc_systems_chip_earlgrey_cw310_0.1.xpr] Error 127
ERROR: Failed to build lowrisc:systems:chip_earlgrey_cw310:0.1 : '['make']' exited with an error: 2
...
<snip>
...
Hi Harry! I'll try out getting Vivado installed in the Container.
Thanks, Erik
Sent with Proton Mail secure email.
On Sunday, July 14th, 2024 at 3:23 PM, Harry Callahan @.***> wrote:
Hi @.***(https://github.com/lmg260a),
Did you come up with another solution for this?
Yes the command you were trying to execute does indeed require Vivado. (All bazel targets under //hw/bitstream/ are fpga bitstreams, in this case the vivado in the target name means using vivado to build an EarlGrey bitstream for the CW310 board (Kintex K410T) with a test-rom spliced into the image).
Currently we don't support generating scripts that can be run externally for this. Bazel is responsible for invoking fusesoc which then invokes vivado, and this probably won't change in the future. Bazel manages the build flow, so we can't just break outside of that to run certain steps manually unfortunately. If you can install Vivado yourself, one option might be to append the vivado installation to the OpenTitan development container dockerfile, and then Bazel will invoke Vivado in headless-mode when building. There are instructions online on how you can do this.
If this is not possible, could you let me know a bit about your environment restrictions that might make running the OpenTitan flows difficult for you? I can't promise to fix everything, but it helps us anticipate problems. Managing the web of proprietary dependencies and locked-down environments is a continual challenge :)
Re. your original error, there is a missing vivado error way down the STDOUT. I just tested locally, and reproduced the following error...
$ bazel build --sandbox_debug //hw/bitstream/vivado:fpga_cw310_test_rom
...
<
snip
...
ERROR: /home/harry/projects/opentitan/hw/bitstream/vivado/BUILD:39:14: FuseSoC hw/bitstream/vivado/build.fpga_cw310 failed: (Exit 1): linux-sandbox failed: error executing
command
(cd /home/harry/.cache/bazel/_bazel_harry/6aecaaad7827b990b88d034b9d0ce702/sandbox/linux-sandbox/665/execroot/lowrisc_opentitan
&&
\
exec
env - \
...
<
snip
~
300 lines
...
INFO: Building INFO: vivado -notrace -mode batch -source lowrisc_systems_chip_earlgrey_cw310_0.1.tcl
ERROR: make: vivado: No such file or directory make:
[Makefile:8: lowrisc_systems_chip_earlgrey_cw310_0.1.xpr] Error 127
ERROR: Failed to build lowrisc:systems:chip_earlgrey_cw310:0.1
:
'
[
'
make
'
]
'
exited with an error: 2
...
<
snip
...
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Description
I do not have a VM running Ubuntu, I only have a Container. I don't have ivado installed in the container, but I do have Vivado running on CentOS. I'd like to generate all the Vivado scripts inside the container, then execute them outside the container in CentOS. When I execute the following command, taken from https://opentitan.org/book/doc/getting_started/setup_fpga.html...
I get this on STDOUT. I don't know how to root-cause the failure. I've been looking around but I didn't spot any appropriate error or log files, etc.
If Vivado installation is required, please let me know and please update the documentation to make that clear for future users.