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: 
Observer alxn
Observer
8,273 Views
Registered: ‎07-22-2013

Using XSCT to check FPGAs are programmed.

XSCT looks promising, so I'm going to try to use it, but I'm finding it hard to match JTAG cables with devices.

 

I have this connected to a server:

 

xsct% jtag target
  1  Digilent JTAG-HS2 210249A143C6
     2  arm_dap (idcode 4ba00477 irlen 4)
     3  xc7z010 (idcode 13722093 irlen 6 fpga)
     4  arm_dap (idcode 4ba00477 irlen 4)
     5  xc7z010 (idcode 13722093 irlen 6 fpga)
  6  Digilent JTAG-HS2 210249A14617
     7  xc7k160t (idcode 0364c093 irlen 6 fpga)
  8  Digilent JTAG-HS2 210249A143D1
     9  arm_dap (idcode 4ba00477 irlen 4)
    10  xc7z010 (idcode 13722093 irlen 6 fpga)
    11  arm_dap (idcode 4ba00477 irlen 4)
    12  xc7z010 (idcode 13722093 irlen 6 fpga)
 13  Digilent JTAG-HS2 210249A1439C
    14  arm_dap (idcode 4ba00477 irlen 4)
    15  xc7z010 (idcode 13722093 irlen 6 fpga)
    16  arm_dap (idcode 4ba00477 irlen 4)
    17  xc7z010 (idcode 13722093 irlen 6 fpga)
 18  Digilent JTAG-HS2 210249A0CEEA
    19  xc7z010 (idcode 13722093 irlen 6 fpga)
    20  arm_dap (idcode 4ba00477 irlen 4)
    21  xc7z010 (idcode 13722093 irlen 6 fpga)

All I want to do is check that the devices connected to *17 *D1 and *C6 are programmed, but for that, I need to use the "xsdb" tool still:

 

xsct% xsdb targets
  1  APU
     2  ARM Cortex-A9 MPCore #0 (Running)
     3  ARM Cortex-A9 MPCore #1 (Running)
  4  xc7z010
  5  APU
     6  ARM Cortex-A9 MPCore #0 (Running)
     7  ARM Cortex-A9 MPCore #1 (Running)
  8  xc7z010
  9* xc7k160t
    10  Debug Module at USER2
       11  MicroBlaze #0 (Running)
 12  APU
    13  ARM Cortex-A9 MPCore #0 (Running)
    14  ARM Cortex-A9 MPCore #1 (Running)
 15  xc7z010
 16  APU
    17  ARM Cortex-A9 MPCore #0 (Running)
    18  ARM Cortex-A9 MPCore #1 (Running)
 19  xc7z010
 20  APU
    21  ARM Cortex-A9 MPCore #0 (Running)
    22  ARM Cortex-A9 MPCore #1 (Running)
 23  xc7z010
 24  APU
    25  ARM Cortex-A9 MPCore #0 (Running)
    26  ARM Cortex-A9 MPCore #1 (Running)
 27  xc7z010
 28  xc7z010
 29  APU
    30  ARM Cortex-A9 MPCore #0 (Running)
    31  ARM Cortex-A9 MPCore #1 (Running)
 32  xc7z010

Then:

xsct% xsdb target 9
xsct% xsdb fpga -stat
FPGA is configured

I can presume that the ordering of the xsdb vs jtag target lists are the same, but the number is different, and xsdb doesn't show the ESN. Very irritating.

 

Is there some other work flow I'm meant to be using to do this?

 

thanks,

 

A.

0 Kudos
2 Replies
Scholar sampatd
Scholar
8,266 Views
Registered: ‎09-05-2011

Re: Using XSCT to check FPGAs are programmed.

Try the command "jtag targets" in xsdb, you should get the ESN.

 

You can also filter targets based on ESN. For e.g.,

targets -set -filter {name =~"APU" && jtag_cable_name =~ "Digilent JTAG-SMT1 210203346637A"} -index 0

0 Kudos
Xilinx Employee
Xilinx Employee
8,244 Views
Registered: ‎10-21-2010

Re: Using XSCT to check FPGAs are programmed.

XSDB targets have additional properties, which include ESN, device index, etc. You can run "targets -target-properties" to see all the properties of XSDB targets. As mentioned in the previous reply, you can filter targets based on ESN, index, etc.

0 Kudos