[FPGA] Error when generating FPGA synthesis scripts
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### 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...
```bash
bazelisk.sh build --sandbox_debug //hw/bitstream/vivado:fpga_cw310_test_rom
```
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.
```bash
Starting local Bazel server and connecting to it...
Loading:
Loading:
Loading:
Loading: 2 packages loaded
Analyzing: target //hw/bitstream/vivado:fpga_cw310_test_rom (3 packages loaded, 0 targets configured)
Analyzing: target //hw/bitstream/vivado:fpga_cw310_test_rom (309 packages loaded, 6793 targets configured)
DEBUG: /opentitan_org/rules/autogen.bzl:151:14: NOTE: stamping is disabled, the chip_info section will use a fixed version string
Analyzing: target //hw/bitstream/vivado:fpga_cw310_test_rom (496 packages loaded, 26841 targets configured)
Analyzing: target //hw/bitstream/vivado:fpga_cw310_test_rom (598 packages loaded, 41490 targets configured)
INFO: Analyzed target //hw/bitstream/vivado:fpga_cw310_test_rom (600 packages loaded, 42303 targets configured).
INFO: Found 1 target...
INFO: Deleting stale sandbox base /home/ot_user1/.cache/bazel/_bazel_ot_user/de5905ce1a6c51190eb830628f418872/sandbox
[1 / 7] [Prepa] BazelWorkspaceStatusAction stable-status.txt
[46 / 115] checking cached actions
[944 / 945] [Prepa] FuseSoC hw/bitstream/vivado/build.fpga_cw310
[944 / 945] FuseSoC hw/bitstream/vivado/build.fpga_cw310; 1s processwrapper-sandbox
[944 / 945] FuseSoC hw/bitstream/vivado/build.fpga_cw310; 10s processwrapper-sandbox
ERROR: /opentitan_org/hw/bitstream/vivado/BUILD:39:14: FuseSoC hw/bitstream/vivado/build.fpga_cw310 failed: (Exit 1): process-wrapper failed: error executing command
(cd /home/ot_user1/.cache/bazel/_bazel_ot_user/de5905ce1a6c51190eb830628f418872/sandbox/processwrapper-sandbox/1/execroot/lowrisc_opentitan && \
exec env - \
HOME=/home/ot_user1 \
PATH=/home/ot_user1/.cache/bazelisk/downloads/bazelbuild/bazel-6.2.1-linux-x86_64/bin:/home/ot_user1/.local/bin:/opentitan_org/verilator/4.210/bin:/opentitan_org/lowrisc_rv32icmb/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
PYTHONPATH='' \
TMPDIR=/tmp \
XILINXD_LICENSE_FILE='' \
XILINX_HLS='' \
XILINX_VIVADO='' \
/home/ot_user1/.cache/bazel/_bazel_ot_user/install/50a5a3eaeaa5297d31568ab6a3a702d9/process-wrapper '--timeout=0' '--kill_delay=15' '--stats=/home/ot_user1/.cache/bazel/_bazel_ot_user/de5905ce1a6c51190eb830628f418872/sandbox/processwrapper-sandbox/1/stats.out' bazel-out/k8-opt-exec-2B5CBBC6/bin/util/fusesoc_build '--cores-root=.' run '--flag=fileset_top' '--target=synth' --setup --build '--build-root=bazel-out/k8-fastbuild/bin/hw/bitstream/vivado/build.fpga_cw310' lowrisc:systems:chip_earlgrey_cw310 '--BootRomInitFile=../../../../../../../../../../bazel-out/k8-fastbuild-ST-2cc462681f62/bin/sw/device/lib/testing/test_rom/test_rom_fpga_cw310.39.scr.vmem' '--OtpCtrlMemInitFile=../../../../../../../../../../bazel-out/k8-fastbuild/bin/hw/ip/otp_ctrl/data/img_rma.24.vmem')
I
```
Contributor guide
Research direction
Start with the command in the setup_fpga documentation and the failing target at hw/bitstream/vivado/BUILD:39. Reproduce the FuseSoC build while checking the XILINX_LICENSE_FILE, XILINX_HLS, and XILINX_VIVADO environment variables shown in the log. Done means identifying the container requirements and documenting the required Vivado setup or the supported script-generation workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100