Closed potatochick2020 closed 10 months ago
i am using m2 macbook air,Docker version 23.0.5, build bc4487a after typing docker -v
Are you using the 2023 version of Vivado? Because I haven't tested it myself yet.
I'll fix it this week when I download the new version of Vivado.
@ichi4096 Any update on this?
Yeah, I‘ll get around it in a few days or so.
I got the same problem
This is a fresh install.
INFO Could not detect the display scale (hDPI).
If you are using a high resolution monitor, you can set the insaller scale factor like this:
export XINSTALLER_SCALE=2
setenv XINSTALLER_SCALE 2
Running in batch mode...
Picked up JAVA_TOOL_OPTIONS: -Dsun.java2d.xrender=false
This command is not for general use and should only be run as the result of a call to
ProcessBuilder.start() or Runtime.exec() in a java application
Copyright (c) 1986-2022 Xilinx, Inc. All rights reserved.
Copyright (c) 2022-2023 Advanced Micro Devices, Inc. All rights reserved.
INFO - User has accepted the EULAs.
ERROR - The value specified in the configuration file for Modules (Virtex UltraScale+ HBM:1,DocNav:1,Kintex UltraScale:1,Artix UltraScale+:1,Spartan-7:1,Artix-7:1,Virtex UltraScale+:1,Vitis Model Composer(Xilinx Toolbox for MATLAB and Simulink. Includes the functionality of System Generator for DSP):1,Zynq UltraScale+ MPSoC:1,Zynq-7000:1,Virtex UltraScale+ 58G:1,Kintex-7:1,Install Devices for Kria SOMs and Starter Kits:1,Kintex UltraScale+:1) is not valid.
Generating App icon
./install.sh:68: no matches found: Xilinx/Vivado/*/doc/images/vivado_logo.png
Warning: not a valid file - skipping
Warning: not a valid file - skipping
Warning: not a valid file - skipping
Warning: not a valid file - skipping
Warning: not a valid file - skipping
Warning: not a valid file - skipping
Warning: not a valid file - skipping
Warning: not a valid file - skipping
Warning: not a valid file - skipping
icon.iconset:Failed to generate ICNS.
mv: rename icon.icns to Launch_Vivado.app/Contents/Resources/icon.icns: No such file or directory
I think it's because of the 2023 bin? So I changed to 2022 bin
After installation, it failed at creating hard link
WARN - Failed to create the hard link /home/user/Xilinx/.xinstall/Vivado_2022.2/tps/boost_1_72_0/boost/fusion/include/list_tie.hpp pointing to /home/user/Xilinx/Vivado/2022.2/tps/boost_1_72_0/boost/fusion/include/list_tie.hpp. /home/user/Xilinx/.xinstall/Vivado_2022.2/tps/boost_1_72_0/boost/fusion/include/list_tie.hpp -> /home/user/Xilinx/Vivado/2022.2/tps/boost_1_72_0/boost/fusion/include/list_tie.hpp INFO - Successfully recovered the original file /home/user/Xilinx/.xinstall/Vivado_2022.2/tps/boost_1_72_0/boost/fusion/include/list_tie.hpp WARN - The file /home/user/Xilinx/Vivado/2022.2/tps/boost_1_72_0/boost/fusion/include/list_tie.hpp was optimized (hardlinked) 10 times out of possible 11 WARN - Failed to create the hard link /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/sklearn/metrics/cluster/tests/__init__.py pointing to /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/sklearn/inspection/_plot/tests/__init__.py. /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/sklearn/metrics/cluster/tests/__init__.py -> /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/sklearn/inspection/_plot/tests/__init__.py INFO - Successfully recovered the original file /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/sklearn/metrics/cluster/tests/__init__.py WARN - Failed to create the hard link /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/joblib/test/data/__init__.py pointing to /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/sklearn/inspection/_plot/tests/__init__.py. /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/joblib/test/data/__init__.py -> /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/sklearn/inspection/_plot/tests/__init__.py INFO - Successfully recovered the original file /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/joblib/test/data/__init__.py WARN - Failed to create the hard link /home/user/Xilinx/Vivado/2022.2/tps/lnx64/binutils-2.37/bfd/stamp-lib pointing to /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/sklearn/inspection/_plot/tests/__init__.py. /home/user/Xilinx/Vivado/2022.2/tps/lnx64/binutils-2.37/bfd/stamp-lib -> /home/user/Xilinx/Vivado/2022.2/tps/lnx64/python-3.8.3/lib/python3.8/site-packages/sklearn/inspection/_plot/tests/__init__.py
It created the Launch_vivado app and I trusted it in Accessibility, then trusted the xvcd unix exe in Accessibility as well. However, the app launch the icon then stop.
(M1 pro ,13.5)
Looks like I'm trying this out at the same time. I have the exact same issues as @hakatu - I tried 2023 and then 2022.2, both with the issues that are posted above.
Today I also tried 2022.1 which has the same problem for me.
So I managed to get Vivado to open by editing Launch_Vivado.app/Launch_Vivado. I commented out the while
line and the done
lines. Then it doesn't get stuck in a loop and the program opens up. I installed 2022.2 by the way.
However, I do have a Terminal window that pops up having trouble with not seeing a USB device connected:
ftdi_usb_open(0x0403, 0x6010): -3 (device not found) io_init failed
But I'm not very concerned about that and just hit Control-C in that window. I'll probably program the FPGA using other means. I haven't done more testing, but this may work for me. Thank you and hope this helps!
I've updated the script to support the 2023 version and also added some little bugfixes. Do your linker errors still persist with these updates?
I'm gonna close this as the issue has been fixed with the 2023 version being supported now. The linker errors, if they persist, should be addressed in #15.
Bellow is everything I did