-
Notifications
You must be signed in to change notification settings - Fork 24
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
App doesn't launch at all #24
Comments
I bet your installation is not successful, which usually something like
happens. I'm also trying to figure this out. |
BTW, I had some luck by installing 2022 instead of 2023 version. Maybe you want to check that as well? |
I had the same issue here for both 2022 and 2023. MacOS Sonoma and M2. I bypassed the error setting the Docker to use only one CPU. 2023 successfully installed. |
Im having the same problem with the "Generating app icon" part. Like you show on your print... |
same issue. I think it has something to do with the "permissions denied" in the beginning of the this log file: "Verifying archive integrity... All good. Log into your Xilinx account to download the necessary files. E-mail Address:vladbara1@gmail.com You successfully logged into your account. The installation will begin now. Generating App icon |
Anyone solved this problem? I also get this logs :( Launching Docker daemon and XQuartz... What's Next? E-mail Address:pirvuciprian37@gmail.com You successfully logged into your account. The installation will begin now. Generating App icon |
Hello, Cipppp , I managed to do it by following this fix: Also, be careful with the name of the folder: In the end, it worked for me. It runs. I have an M1 , 16 GB . |
...... by the way can wo show ho did you do it ( because I have same model) |
I did the installing according to README, but when I try to open Launch_Vivado, XQuartz and Terminal launches, but after that, well... nothing happens. This may be a dumb issue, but I couldn't make the Vivado open.
Here is the terminal output:
Thanks in advance :)
The text was updated successfully, but these errors were encountered: