UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Visitor pzzh
Visitor
653 Views
Registered: ‎12-26-2018

Repeatly ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/

I am using vivado 2017.4 for zynq xc7z015, OS: windows 7, when open hw target and auto connect, it can access zynq but it reports below errors in 1 or 2 mintues repeatly:

 

open_hw_target

INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210249A743CF

set_property PROGRAM.FILE {E:/Demo/Z7015/led/led.runs/impl_1/led.bit} [get_hw_devices xc7z015_1]

current_hw_device [get_hw_devices xc7z015_1]

refresh_hw_device -update_hw_probes false [lindex [get_hw_devices xc7z015_1] 0]

INFO: [Labtools 27-1435] Device xc7z015 (JTAG device index = 1) is not programmed (DONE status = 0).

ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/210249A743CF

ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/210249A743CF

ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/210249A743CF

 

I programed bit file by jtag, it reports below error:

ERROR: [Labtools 27-3165] End of startup status: LOW
ERROR: [Common 17-39] 'program_hw_devices' failed due to earlier errors.

Current board status:

1. JTAG can access chip(PL and PS appeared in JTAG Chain), it can read register, and XADC value.

2. JTAG Chain link down repeatly in 1 or 2 miniture, and JTAG chain can be connected and active automaticly by vivado

3. When program bit file, always failed.

4. The board can boot from SD card and run linux well, bot PL works well.

 

What I have done?

1. Jtag chain linked and down repeatly, I thought zynq chip may be restarted, so I check the all power rail, there are no voltage drop down and overshoot.

2. I decreased TCK frequency to 5M, 1M, but it got same results.

3. Check REGISTER.BOOT_STATUS and REGISTER.CONFIG_STATUS

report_property [current_hw_device] -regexp REGISTER.BOOT_STATUS.*
Property Type Read-only Value
REGISTER.BOOT_STATUS string true 00000000000000000000000000000000
REGISTER.BOOT_STATUS.BIT00_0_STATUS_VALID string true 0
REGISTER.BOOT_STATUS.BIT01_0_FALLBACK string true 0
REGISTER.BOOT_STATUS.BIT02_0_INTERNAL_PROG string true 0
REGISTER.BOOT_STATUS.BIT03_0_WATCHDOG_TIMEOUT_ERROR string true 0
REGISTER.BOOT_STATUS.BIT04_0_ID_ERROR string true 0
REGISTER.BOOT_STATUS.BIT05_0_CRC_ERROR string true 0
REGISTER.BOOT_STATUS.BIT06_0_WRAP_ERROR string true 0
REGISTER.BOOT_STATUS.BIT07_0_SECURITY_ERROR string true 0
REGISTER.BOOT_STATUS.BIT08_1_STATUS_VALID string true 0
REGISTER.BOOT_STATUS.BIT09_1_FALLBACK string true 0
REGISTER.BOOT_STATUS.BIT10_1_INTERNAL_PROG string true 0
REGISTER.BOOT_STATUS.BIT11_1_WATCHDOG_TIMEOUT_ERROR string true 0
REGISTER.BOOT_STATUS.BIT12_1_ID_ERROR string true 0
REGISTER.BOOT_STATUS.BIT13_1_CRC_ERROR string true 0
REGISTER.BOOT_STATUS.BIT14_1_WRAP_ERROR string true 0
REGISTER.BOOT_STATUS.BIT15_1_SECURITY_ERROR string true 0
REGISTER.BOOT_STATUS.BIT16_RESERVED string true 0000000000000000

report_property [current_hw_device] -regexp REGISTER.CONFIG_STATUS.*
Property Type Read-only Value
REGISTER.CONFIG_STATUS string true 01100110000000000001111100001100
REGISTER.CONFIG_STATUS.BIT00_CRC_ERROR string true 0
REGISTER.CONFIG_STATUS.BIT01_DECRYPTOR_ENABLE string true 0
REGISTER.CONFIG_STATUS.BIT02_PLL_LOCK_STATUS string true 1
REGISTER.CONFIG_STATUS.BIT03_DCI_MATCH_STATUS string true 1
REGISTER.CONFIG_STATUS.BIT04_END_OF_STARTUP_(EOS)_STATUS string true 0
REGISTER.CONFIG_STATUS.BIT05_GTS_CFG_B_STATUS string true 0
REGISTER.CONFIG_STATUS.BIT06_GWE_STATUS string true 0
REGISTER.CONFIG_STATUS.BIT07_GHIGH_STATUS string true 0
REGISTER.CONFIG_STATUS.BIT08_MODE_PIN_M[0] string true 1
REGISTER.CONFIG_STATUS.BIT09_MODE_PIN_M[1] string true 1
REGISTER.CONFIG_STATUS.BIT10_MODE_PIN_M[2] string true 1
REGISTER.CONFIG_STATUS.BIT11_INIT_B_INTERNAL_SIGNAL_STATUS string true 1
REGISTER.CONFIG_STATUS.BIT12_INIT_B_PIN string true 1
REGISTER.CONFIG_STATUS.BIT13_DONE_INTERNAL_SIGNAL_STATUS string true 0
REGISTER.CONFIG_STATUS.BIT14_DONE_PIN string true 0
REGISTER.CONFIG_STATUS.BIT15_IDCODE_ERROR string true 0
REGISTER.CONFIG_STATUS.BIT16_SECURITY_ERROR string true 0
REGISTER.CONFIG_STATUS.BIT17_SYSTEM_MONITOR_OVER-TEMP_ALARM_STATUS string true 0
REGISTER.CONFIG_STATUS.BIT18_CFG_STARTUP_STATE_MACHINE_PHASE string true 000
REGISTER.CONFIG_STATUS.BIT21_RESERVED string true 0000
REGISTER.CONFIG_STATUS.BIT25_CFG_BUS_WIDTH_DETECTION string true 11
REGISTER.CONFIG_STATUS.BIT27_HMAC_ERROR string true 0
REGISTER.CONFIG_STATUS.BIT28_PUDC_B_PIN string true 0
REGISTER.CONFIG_STATUS.BIT29_BAD_PACKET_ERROR string true 1
REGISTER.CONFIG_STATUS.BIT30_CFGBVS_PIN string true 1
REGISTER.CONFIG_STATUS.BIT31_RESERVED string true 0

 

from the config registerm BAD_PACKET_ERROR, what does this mean? Is this error caused this problem?

how can i solved it?

 

Thanks

0 Kudos
4 Replies
Moderator
Moderator
612 Views
Registered: ‎06-05-2013

Re: Repeatly ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/

Try to set the JTAG mode(101) instead of Slave serial. (111). Load the bitstream and see if anything changes. Next you can read the following for bad packet error https://www.xilinx.com/support/answers/34909.html

Any other design which can be loaded via JTAG?
Run the IDCODE loop test if it passes? https://www.xilinx.com/support/answers/66798.html Just source the tcl attached to the AR.

Please share the results of above then we can debug it further.
Thanks
Harshit
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Visitor pzzh
Visitor
600 Views
Registered: ‎12-26-2018

Re: Repeatly ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/

Thank you, Harshit

>>>Try to set the JTAG mode(101) instead of Slave serial. (111).

It is ZYNQ chip, I have set JTAG mode, MIO[5:3]= 000

But the configure register is:

REGISTER.CONFIG_STATUS.BIT08_MODE_PIN_M[0]    1

REGISTER.CONFIG_STATUS.BIT09_MODE_PIN_M[1]    1

REGISTER.CONFIG_STATUS.BIT10_MODE_PIN_M[2]    1

It seems strange。

 

>>>Next you can read the following for bad packet error

After open target : auto connect,  It will not appeared bad packet error immediately, some mintues later, it happened.

and If power up board, and download bit file(fialed), It is also not appeared bad packet error immediately, bad packet error appeared some minuture later.

It seems bad packet error is not reason caused download failture.

 

>>>>>Any other design which can be loaded via JTAG? 

It can be loaded some days before, but now it can't.

 

and I have run IDCODE loop test, It passed, below is the log:

source e:/idcode_loop.tcl
# puts "Version: 0.2"
Version: 0.2
# proc idcode_loop {num {index 1} } {
# set device [lindex [get_hw_devices] $index]
# set idcode [get_property IDCODE $device]
# for {set i 0} {$i <= $num} {incr i} {
# set testdata [get_property IDCODE $device]
# if {$testdata != $idcode} {
# return "LOOP Test Failed at the $i times."
# }
# }
# return "LOOP Test Finished!\nThe device is $device\nIDCODE is $idcode"
# }
idcode_loop 10000 1
LOOP Test Finished!
The device is xc7z015_1
IDCODE is 00000011011100111011000010010011

 

0 Kudos
Visitor pzzh
Visitor
513 Views
Registered: ‎12-26-2018

Re: Repeatly ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/

Hi, Harshit:

Do you have any new suggestion for this?

0 Kudos
Newbie urquan3
Newbie
106 Views
Registered: ‎04-22-2019

Re: Repeatly ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/

Yes.  Turns out this can also happen if you partially fry the USB port.  I was running an Arty A7 using just the USB for power.  Worked just fine till I attached a TMP36 for a class project.  I started getting this error and it continued even after a system reboot or adding external power.  Problem went away by using a different USB port.  I will now only run it using external power.

0 Kudos