02-03-2016 08:47 PM - edited 02-03-2016 08:51 PM
I am using SDK 2015.4, and have found the Tcl script and HSI commands specified in this useful document:
There are some good examples in the latter part of Chapter 4.
If I manually create a Zynq FSBL application in the GUI SDK, I can choose on the new application dialog between "create new BSP" or "use existing BSP". I want to be able to specify to use an existing BSP.
In the Tcl script, I have:
hsi::open_hw_design $hw_path/system.hdf hsi::create_sw_design -proc ps7_cortexa9_0 -os standalone BSP hsi::generate_bsp -dir $bsp_path -compile hsi::create_sw_design -proc ps7_cortexa9_0 -os standalone -app zynq_fsbl fsbl hsi::generate_app -dir $fsbl_path -compile
It ends up generating the BSP at the "generate_bsp" command, but then the subsequent "create_sw_design" command to make the application does not seem to use the current sw design, but it ends up regenerating its own BSP. So it is generated twice. I don't want that.
How do I specify within either "create_sw_design" command or "generate_app" command to use a specific existing BSP?
02-03-2016 10:49 PM - edited 02-03-2016 10:49 PM
02-04-2016 12:22 AM - edited 02-04-2016 12:26 AM
Yes, FSBL does require those libraries, but unfortunately, no, that's not the reason.
I did have the following as the actual script I was running. I just abstracted away those details that I thought weren't relevant.
hsi::open_hw_design $hw_path/system.hdf hsi::create_sw_design -proc ps7_cortexa9_0 -os standalone BSP hsi::add_library xilffs hsi::add_library xilrsa hsi::set_property CONFIG.stdin ps7_uart_1 [hsi::get_os] hsi::set_property CONFIG.stdout ps7_uart_1 [hsi::get_os] hsi::generate_bsp -dir $bsp_path -compile hsi::create_sw_design -proc ps7_cortexa9_0 -os standalone -app zynq_fsbl fsbl hsi::generate_app -dir $fsbl_path -compile
"generate_app" still creates its own BSP.
The linked AR is about using the "sdk" commands in XSCT, but I am using just HSI commands. I did see that:
"However, the FSBL app requires the xilffs and xilrsa libraries in the BSP, and BSP generation will not have these by default.
To work around this, you just need to create the Zynq FSBL app as this will generate the BSP automatically."
I don't believe that pure HSI commands should require a workaround, since you can actually specify the libraries directly, as I have.