I am working on zcu102 ultrascale+. I would like to run BIST. I was unable to run it while following the tutorial provided by Xilinx (https://www.xilinx.com/support/documents/boards_and_kits/zcu102/xtp426-zcu102-quickstart.pdf). Then after some digging i came to know that it needs to be flashed. I followed the Restore Flash Steps (provided by Xilinx). While running the script on Vivado i get this error. I am unaware that what problem it could be. I have made sure to check all the jumpers on the board are in default position.
Question
Bugtech
Hi.
I am working on zcu102 ultrascale+. I would like to run BIST. I was unable to run it while following the tutorial provided by Xilinx (https://www.xilinx.com/support/documents/boards_and_kits/zcu102/xtp426-zcu102-quickstart.pdf). Then after some digging i came to know that it needs to be flashed. I followed the Restore Flash Steps (provided by Xilinx). While running the script on Vivado i get this error. I am unaware that what problem it could be. I have made sure to check all the jumpers on the board are in default position.
Here is the output of Tcl Console
****************************************
source zcu102_program_qspi.tcl
# set_param xicom.use_bitstream_version_check false
# open_hw
# catch {disconnect_hw_server localhost:3121}
# connect_hw_server -url localhost:3121
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
# current_hw_target [get_hw_targets */xilinx_tcf/Digilent/*]
# set_property PARAM.FREQUENCY 15000000 [get_hw_targets */xilinx_tcf/Digilent/*]
# open_hw_target
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210308B52422
# current_hw_device [lindex [get_hw_devices] 0]
# refresh_hw_device -update_hw_probes false [lindex [get_hw_devices] 0]
INFO: [Labtools 27-1435] Device xczu9 (JTAG device index = 0) is not programmed (DONE status = 0).
# current_hw_device [lindex [get_hw_devices arm_dap_1] 0]
# refresh_hw_device -update_hw_probes false [lindex [get_hw_devices arm_dap_1] 0]
# current_hw_device [lindex [get_hw_devices] 0]
# create_hw_cfgmem -hw_device [lindex [get_hw_devices] 0] -mem_dev [lindex [get_cfgmem_parts {mt25qu512-qspi-x8-dual_parallel}] 0]
# set_property PROGRAM.BLANK_CHECK 0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.ERASE 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.CFG_PROGRAM 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.VERIFY 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.CHECKSUM 0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# refresh_hw_device [lindex [get_hw_devices] 0]
INFO: [Labtools 27-1435] Device xczu9 (JTAG device index = 0) is not programmed (DONE status = 0).
# set_property PROGRAM.ADDRESS_RANGE {use_file} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.FILES [list "blinkbist.mcs" ] [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0]]
# set_property PROGRAM.ZYNQ_FSBL {zynq_mp_fsbl.elf} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0]]
# set_property PROGRAM.BLANK_CHECK 0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.ERASE 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.CFG_PROGRAM 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.VERIFY 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.CHECKSUM 0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
Program File cannot be empty
ERROR: [Labtools 27-3347] Flash Programming Unsuccessful: Program File cannot be empty
ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.
while executing
"program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]"
(file "zcu102_program_qspi.tcl" line 28)
*********************************************
Tried with Vivado 2019.1, 2022.2. Same error.
Any help? Thanks!
Link to comment
Share on other sites
0 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now