08-31-2018 02:54 AM
I am running Windows 10 (latest update). I have Vivado & SDK 2016.2 installed. Upon building a project in Vivado, exporting the hardware & launching SDK through Vivado, the SDK windows opens but is getting stuck in "Initializing s/w repositories" phase. It took 1hr to do this & the SDK log showed following
15:06:14 INFO : Launching XSDB server: xsdb.bat -interactive E:\hdl_dev_adc_dac_MEO_Booster_v00\projects\fmcomms5\zc706\fmcomms5_zc706.sdk\temp_xsdb_launch_script.tcl
15:06:16 INFO : XSDB server has started successfully.
15:06:16 INFO : Restoring global repository preferences:
16:06:38 ERROR : (XSDB Server)ERROR: [Hsi 55-1433] Error boost::filesystem::status: Access is denied: "C:/Xilinx\SDK\2016.2\gnu\microblaze\linux_toolchain\nt64_be\microblaze-xilinx-linux-gnu\lib32"
16:06:38 ERROR : (XSDB Server)ERROR: [Hsi 55-1433] Error boost::filesystem::status: Access is denied: "C:/Xilinx\SDK\2016.2\gnu\microblaze\linux_toolchain\nt64_le\microblazeel-xilinx-linux-gnu\lib32"
16:06:38 ERROR : (XSDB Server)ERROR: [Hsi 55-1433] Error boost::filesystem::status: Access is denied: "C:/Xilinx\SDK\2016.2\gnu\microblaze\linux_toolchain\nt_le\microblazeel-xilinx-linux-gnu\lib32"
16:07:21 ERROR : Internal error. Unable to add C:\Xilinx as a repository.
16:07:21 INFO : Processing command line option -hwspec E:/hdl_dev_adc_dac_MEO_Booster_v00/projects/fmcomms5/zc706/fmcomms5_zc706.sdk/system_top.hdf.
So, two questions, why is initialization taking so long & what is the above error I received?
09-17-2018 01:59 AM
09-03-2018 01:31 AM
It seems that SDK does not have the right to access the installation folders. Could you check if you can read or write files into these folders?
09-11-2018 10:24 PM
Yes, I can read & write files in C:\Xilinx\SDK directory. So what seems to be the problem
09-12-2018 12:53 AM
09-12-2018 02:54 AM
The account on my PC is itself an Administrator account. So launching SDK through Vivado would be equivalent to launching it as an administrator no?
09-12-2018 02:58 AM
No sure how windows is working so I would try directly lauching SDK as admin.
Could you also check the proxy settings in SDK. Try to set it to direct. It has helped to solve some weird issues
09-17-2018 01:59 AM