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: 
Highlighted
Voyager
Voyager
202 Views
Registered: ‎05-30-2018

Vivado couldn't detect debug core [Labtools 27-3361]

Hello,

Vivado couldn't instantiate debug core getting the following message:

[Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device. To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).

This message was gnenerated after synthesis/implementation ... in the "Implemented Design" section in Message window.

Nevertheless I checked debug clock ... it comes from PLL IP. (please see screenshot below - bleu line). Can such clock be considered as free-running ?

link to screenshot

Thanks

0 Kudos
3 Replies
Voyager
Voyager
185 Views
Registered: ‎05-30-2018

Re: Vivado couldn't detect debug core [Labtools 27-3361]

executing

get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]

in the TCL console gets '1'.

0 Kudos
Voyager
Voyager
174 Views
Registered: ‎05-30-2018

Re: Vivado couldn't detect debug core [Labtools 27-3361]

Well, PLL output isn't actually free-running clock.

I changed debug clock to the external clock and debug core was instantiated.

Yet it does not help me too much, because external clock has almost the same freqeqnce as the signal that I want to debug.

Does exist some way to use PLL sigal as clock source for debug core ?

 

Moderator
Moderator
43 Views
Registered: ‎02-09-2017

Re: Vivado couldn't detect debug core [Labtools 27-3361]

Hi @pavel_47,

 

I'm glad you figurred out the issue was with the clocking.

I actually can use the PLL/MMCM as a source of clock for the Debug Core / ILA.

The trick is that you have to make sure that:

  1. The PLL/MMCM is not being held in reset during startup, neither you are reseting it after configuration.
  2. Provide the proper constraints for the input clock, so it can be correctly timed and propagated through the PLL and to the final destination.

Thanks,

Andre Guerrero

Product Applications Engineer

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos