cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Observer
Observer
168 Views
Registered: ‎07-11-2018

No hardware targets exist on the server

I'd like to find a way to get Scenario 2 below to work and would appreciate help with this.  

Scenario 1 (WORKS):  Connecting to remote hw_server works, and subsequently finding target hardware works, as long as the hw_server had been envoked as part of the startup process of the remote Linux box boot up.  In this case the 'hw_server -d' command is run from a startup rc.local file.

Scenario 2 (DOES NOT WORK): Connecting to remote hw_server works, but subsequently finding target hardware does not work, if the hw_server had been envoked after the remote Linux box has already been booted. In this case the 'hw_server -d' command is executed on command line after the Linux box is up and running.

 

Using the Hardware Manager in Vivado 2018.3 on Windows 10, and connecting to hw_server running on remote computer with CentOS Linux 7.

 

Output from 'hw_server -S':

****** Xilinx hw_server v2018.3
**** Build date : Dec 6 2018-23:53:53
** Copyright 1986-2018 Xilinx, Inc. All Rights Reserved.

INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application

Server-Properties: {"Name":"Xilinx Hardware Server","OSName":"Linux 3.10.0-862.9.1.el7.x86_64","UserName":"root","AgentID":"5e4433fb-76b6-4cf7-8303-81660aa8cd55","TransportName":"TCP","Port":"3121","ServiceManagerID":"5e4433fb-76b6-4cf7-8303-81660aa8cd55-0"}
INFO: To connect to this hw_server instance use url: TCP:CH-MGULOTTA1:3121

 

Output from Hardware Manager that works (Scenario 1):

connect_hw_server -url ch-mgulotta1:3121
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:ch-mgulotta1:3121
current_hw_target [get_hw_targets */xilinx_tcf/Digilent/DINI01808034A]
set_property PARAM.FREQUENCY 15000000 [get_hw_targets */xilinx_tcf/Digilent/DINI01808034A]
open_hw_target
INFO: [Labtoolstcl 44-466] Opening hw_target ch-mgulotta1:3121/xilinx_tcf/Digilent/DINI01808034A
set_property PROGRAM.FILE {C:/FPGA/WORK/myMACPHY/v127_myPCS3264_SynGBx_Bypass/Vivado/project_1/project_1.runs/impl_3/fpga_v2.bit} [get_hw_devices xcku095_0]
current_hw_device [get_hw_devices xcku095_0]

 

Output from Hardware Manager that does not work (Scenario 2):

connect_hw_server -url ch-mgulotta1:3121
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:ch-mgulotta1:3121
current_hw_target [get_hw_targets */xilinx_tcf/Digilent/DINI01808034A]
ERROR: [Labtoolstcl 44-199] No matching targets found on connected servers: ch-mgulotta1
Resolution: If needed connect the desired target to a server and use command refresh_hw_server. Then rerun the get_hw_targets command.
ERROR: [Common 17-39] 'get_hw_targets' failed due to earlier errors.

0 Kudos
1 Reply
Highlighted
Moderator
Moderator
95 Views
Registered: ‎02-09-2017

Re: No hardware targets exist on the server

Hi @mgulotta,

 

This issue seems odd to me. It seems like your commands are correct and I'd expect Scenario 2 to work.

Could you please do the following test:

On Scenario 2, open the HW Manager as normal and connect to the hw_server by running the TCL command connect_hw_server -url ch-mgulotta1:3121. After that, please run the TCL command get_hw_targets (do not add anything else after). Does it return any target or does it return a null?

get_hw_targets.PNG

I wonder if for some reason the target name is changing between Scenario 1 and Scenario 2. The test above should tell if hw_server can see any target available.

In addition, please make sure that the board is powered ON in both cases. Otherwise, it won't be able to connect.

Thanks,

Andre Guerrero

Product Applications Engineer

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