Program burning and commissioning of local devices on remote servers (Vivado-based, SDK Software)

When using Vivado and SDK for design development, it is often necessary to log on to a remote server, but one problem is that the boards used are usually connected to their own computers (LOCAL-PC), How do you get the design software running on the server to detect the devices that are connected locally? The Vivado Development Kit provides a workaround for using hardware Server, with the following steps:

1. Locate the Vivado or SDK installation directory on LOCAL-PC and locate the Hw_server program in this directory, with the following path:

<vivado_install_root>\bin or <sdk_root>\bin, then run Hw_server

Keep the window open. Then open a separate DOS command window and use Ipconfig to view the native IP.

2. On the remote side, for Vivado:

In the Flow Navigator window, locate program and Debug--->hardware Manager--->open target, select Open New target, click Next, select Remote Server

In the host then fill in the first step to get the native IP, click Next, if successful, you can see the connected device, if it fails, the local firewall will be shut down and try again.

For the SDK:

In the Target Connection window, right-hardware server, create a new target, enter the target name (any), the host window to fill in the native IP, click OK. Also if the connection fails, close the local firewall and try again.

Program burning and commissioning of local devices on remote servers (Vivado-based, SDK Software)