-
Notifications
You must be signed in to change notification settings - Fork 53
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
write_dsa failed #11
Comments
I'm having the exact same problem. I followed the tutorial to the letter. The project is stored in:
|
Can you attach your vivado.log and vivado.jou files for the lab exercise so I can look it over? You may need to step through the lab again to get a clean copy. Just the log for Lab 1 would be great. Thanks. |
1 similar comment
Can you attach your vivado.log and vivado.jou files for the lab exercise so I can look it over? You may need to step through the lab again to get a clean copy. Just the log for Lab 1 would be great. Thanks. |
There are numerous vivado.log and vivado.jou logs:
Which one(s) do you want? |
The Vivado journal and log files would be in the directory from which you launched Vivado on a Linux system, or in the <user>/AppData/Roaming/Xilinx/Vivado folder on Windows. They would be called vivado.jou and vivado.log. The journal file is a simple list of the commands you used when using Vivado, and the log file is those same commands with response transcript from the tool. I am attaching my vivado.jou journal file for Lab 1 (renamed to vivado.txt to post here). You can use this to check against your own journal. |
Hi, |
This tutorial was written for 2018.2 and will be updated shortly for 2018.3. The document you should use for 2017.4 is UG1236: https://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_4/ug1236-sdsoc-platform-tutorial.pdf |
Got it, thanks. |
As the picture shows,when I try to write dsa in vivado 2018.2, it shows the error that "Project property dsa.name needs to be set before generating a DSA.", how to solve this problem?
The text was updated successfully, but these errors were encountered: