Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

How to find a device which is programmed with an instrument design?

Status
Not open for further replies.

u24c02

Advanced Member level 1
Joined
May 8, 2012
Messages
404
Helped
2
Reputation
4
Reaction score
2
Trophy points
1,298
Activity points
4,101
Hi,

When I use the identify, I've got the below log message which is

"
ERROR: Could not find a device which is programmed with an instrumented design:
Device dev_0_XCF32P: Device is not instrumented.
Device dev_1_XC5VLX110: Device is not instrumented.
"
But I dont' know what exactly it want to say. and what should I do ?


Meanwhile, when I program the mcs, bit file to the FPGA, it works as well in ISE. I mean that there's no problem. it works as well in check the boundary-scan in the iMPACT.

So what the problem?

Code:
INFO: chain info -raw
INFO: chain info -active
INFO: chain info -active
D:/work/fpga_synplify$ com check
INFO: com check
INFO: Setting up hardware driver ...
INFO:  Info: Attempting to connect to the platform USB cable (port=USB2) ! 
INFO: ok.
INFO: Checking port I/O ...
INFO: Checking communication with the xilinxusb cable and the hardware...
INFO: The hardware is responding correctly.
INFO: ok.
INFO: Checking device chain setup ...
INFO: ok.
INFO: Checking Hardware ID ...
ERROR: Could not find a device which is programmed with an instrumented design:
     Device dev_0_XCF32P:  	Device is not instrumented.
     Device dev_1_XC5VLX110:  	Device is not instrumented.
ERROR: 
1
 
Last edited:

Which debugging functions (e.g. Chipscope) did you compile into the design? If none, what are you complaining about?
 

Meanwhile, when I program the mcs, bit file to the FPGA, it works as well in ISE. I mean that there's no problem. it works as well in check the boundary-scan in the iMPACT.
Instrumenting the design with debug cores using Synopsys Identify isn't the same thing as connecting the JTAG chain to iMPACT. iMPACT doesn't know anything about any custom debug cores in a design, iMPACT wouldn't even recognize a Chipscope core if you put one in a design all it recognizes is the JTAG chain and the devices on the chain and whether or not they are recognized as being programmable with a bit file.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top