Skip to content
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

Error in build-sdk.tcl? #4

Open
jkwho opened this issue Nov 14, 2019 · 4 comments
Open

Error in build-sdk.tcl? #4

jkwho opened this issue Nov 14, 2019 · 4 comments

Comments

@jkwho
Copy link

jkwho commented Nov 14, 2019

I follwed this tutorial under vivado2018.2, and build the vivado hardware successfully, but after that, when I tried to build the sdk by running build-sdk.tcl in VIVADO tcl console, I got an error, said that "setws" is an unvalid command (Line 229 in build-sdk.tcl).
So, is there something wrong in this tcl, or I did some mistake in building the SDK?

@fpgadeveloper
Copy link
Owner

The build-sdk.tcl should be run by Xilinx SDK, not Vivado. See the build-sdk.bat file for the command to run.

@jkwho
Copy link
Author

jkwho commented Nov 14, 2019

You mean the XSCT Console in SDK?
I tried as follwings:

  1. export hardware include bitstream
  2. open SDK and select $prj_name.sdk as workspace
  3. open XSCT Console and cd to SDK directory, then source build-sdk.tcl

Then the console output :
Building the local SDK repo from original sources
Copying files from /opt/Xilinx/SDK/2018.2/data/embeddedsw/ThirdParty/sw_services/lwip141_v2_0 to ../EmbeddedSw/ThirdParty/sw_services/lwip141_v2_09
Copying files from /opt/Xilinx/SDK/2018.2/data/embeddedsw/ThirdParty/sw_services/lwip141_v1_9 to ../EmbeddedSw/ThirdParty/sw_services/lwip141_v1_99
Copying files from /opt/Xilinx/SDK/2018.2/data/embeddedsw/ThirdParty/sw_services/lwip141_v1_6 to ../EmbeddedSw/ThirdParty/sw_services/lwip141_v1_69
Copying files from /opt/Xilinx/SDK/2018.2/data/embeddedsw/ThirdParty/sw_services/lwip202_v1_1 to ../EmbeddedSw/ThirdParty/sw_services/lwip202_v1_19
Copying files from /opt/Xilinx/SDK/2018.2/data/embeddedsw/ThirdParty/sw_services/lwip202_v1_0 to ../EmbeddedSw/ThirdParty/sw_services/lwip202_v1_09
Copying files from /opt/Xilinx/SDK/2018.2/data/embeddedsw/ThirdParty/sw_services/lwip141_v1_7 to ../EmbeddedSw/ThirdParty/sw_services/lwip141_v1_79
Copying files from /opt/Xilinx/SDK/2018.2/data/embeddedsw/ThirdParty/sw_services/lwip141_v1_8 to ../EmbeddedSw/ThirdParty/sw_services/lwip141_v1_89
Copying files from /opt/Xilinx/SDK/2018.2/data/embeddedsw/lib/sw_apps/zynqmp_fsbl to ../EmbeddedSw/lib/sw_apps/zynqmp_fsbl
Creating the SDK workspace
There were 1 exported project(s) found in the ../Vivado directory.
Creating SDK workspace.
xsct% workspace is already set. use -switch option to switch to new workspace

Something still wrong with setws

@fpgadeveloper
Copy link
Owner

Sorry, the instructions are not clear for Linux users, I will fix this up.
You need to run XSCT in the "non-interactive mode", ie. from the Linux command line. Don't run the SDK until the script has completed. From a Linux command prompt:

cd <path-to-repo>/SDK
/<path-to-sdk>/2018.2/bin/xsct build-sdk.tcl

That will launch XSCT and build your SDK workspace into the <path-to-repo>/SDK directory. You need to select this directory as your workspace when running SDK (do not select $prj_name.sdk).

@jkwho
Copy link
Author

jkwho commented Nov 15, 2019

thanks for solution, it's done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants