06-26-2015 10:07 AM - edited 06-26-2015 10:40 AM
I've run into an issue with the new XSCT tools (Vivado 2015.1) in Ubuntu 14.04 LTS. I'm running XSCT with a script using the -s switch. XSCT is able to build the hardware design, but fails during BSP generation. This is the SDK.log file that's generated:
10:51:12 ERROR : [Hsi 55-1545] Problem running tcl command ::sw_standalone_v5_0::post_generate : couldn't execute "mb-ar": no such file or directory while executing "exec $archiver -d $libgloss_a _interrupt_handler.o" (procedure "::sw_standalone_v5_0::post_generate" line 18) invoked from within "::sw_standalone_v5_0::post_generate standalone" [Hsi 55-1443] Error(s) while running TCL procedure post_generate() 10:51:12 ERROR : Error generating bsp sources: Failed to generate BSP.
So, though my Xilinx tools are sourced, "mb-ar" cannot be found. "which mb-ar" from the terminal command line returns "/opt/Xilinx/SDK/2015.1/gnu/microblaze/lin/bin/mb-ar", and XSCT appears to be looking in the right place:
xsct% mb-ar couldn't execute "/opt/Xilinx/SDK/2015.1/gnu/microblaze/lin/bin/mb-ar": no such file or directory
mb-ar does exist at that location on my machine, but as a symbolic link. Could this be a permissions problem?
This all works in Fedora 22.
Here's the XSCT script:
set SDK_WORKSPACE sw set HW_DEF hw/hw.runs/run_1/bd_wrapper.hdf set HW_PROJ bd_wrapper_hw set SA_BSP_PROJ standalone_bsp set APP_PROJ app_standalone # set the SDK workspace sdk set_workspace $SDK_WORKSPACE # create the hardware outputs in SDK sdk create_hw_project -name $HW_PROJ -hwspec $HW_DEF # create the standalone BSP sdk create_bsp_project -name $SA_BSP_PROJ -hwproject $HW_PROJ -proc microblaze_0 -os standalone # create application sdk create_app_project -name $APP_PROJ -hwproject $HW_PROJ -proc microblaze_0 -bsp $SA_BSP_PROJ # build the application sdk build_project exit
06-28-2015 10:07 PM
06-27-2015 11:05 PM
can you confirm if you are able to compile BSP using GUI?
06-28-2015 10:07 PM