/u1/Xilinx/Downloads/2019.1/payloadI make a tarball of these.
I then repeat the whole thing again, but let it immediately install. I get 3 choices: XDSK, XSCT, or BootGen. I select XSDK. It wants to install to /tools/Xilinx, which is fine. It will go to /tools/Xilinx/SDK/2019.1 Note that on my system, /tools/Xilinx is a link to /u1/Xilinx. I do this because /u1 is a big disk with plenty of space.
Now I go for a 3rd time. I have to move /tools/Xilinx/SDK off to the side before it will run for me. Now I choose the 2021.2 design tools option. Aha -- this is leading me to the 2021.2 Vivado ML that I already have, so never mind. I put SDK back where it belongs and call it quits.
Once it is all done I see an SDK "icon" on my desktop. Inspecting it reveals that it runs /tools/Xilinx/SDK/2019.1/xsdk.
I tell it to use /home/tom/Xilinx_SDK_workspace as its workspace. It seems to want to use a different workspace directory every time you fire it up, which is pretty stupid actually. The message is that the workspace is "currently in use by another Eclipse application". Well, it turns out this is correct and I did have another instance running. Note that Eclipse is this nasty slow Java based IDE gadget that I have used on other projects and hated for its sluggishness.
Once you get past the workspace issue, it gives you 5 choices:
I create a project "Easy" and tell it to make it a "standalone" project. I select the Hello World template and just build it without making any changes using "Project -- Build Project". Then I look at
/home/tom/Xilinx_SDK_workspace/EasyIt looks like all of the source code (and a makefile) is there to build the standalone project. In fact "Debug/Easy.elf" seems to be the final executable. Just how to somehow load and run it is another question entirely, and if we can ever figure out how to get back to those tutorials, maybe they will give us a clue. There is a "Run" button with many options.
Tom's Computer Info / [email protected]