cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
gudurvenkatesh
Observer
Observer
7,298 Views
Registered: ‎04-14-2014

After programming Virtex 7 Evaluation Board, Get Device ID gives wrong ID in Impact

Jump to solution

Dear all,

I am working on  a project of working on Virtex 7 Evaluation Board. I can generate bit file and go to Impact to program it. I add the device and right click to get Device ID. I get the correct Device ID. Then I program the device with the bit file. After programming if I again right click on the device and click on get device ID, then the read device ID doesnot match with expected device ID.

 

In short I can say that after programming device ID is not matching.

Thank you all in advance.


Regards

0 Kudos
1 Solution

Accepted Solutions
gudurvenkatesh
Observer
Observer
11,789 Views
Registered: ‎04-14-2014

Got the solution.

 

I am using ChipScope Pro to see the outputs. What I have done is I didn't give physical constraints to output ports. And gave a switch to ignore this error. But while generating the bit file, I guess these unmapped output pins have disturbed the JTAG pins. Due to which after programming JTAG was not working.
Later I removed those output ports and made them internal signals. Then I generated programming file and programmed the FPGA. When I checked for device id, I got the correct device id. Thus JTAG is working after programming the bit file.

 

Thanks a lot for all of you for your time.

 

Regards

VY Gudur

View solution in original post

6 Replies
vuppala
Xilinx Employee
Xilinx Employee
7,293 Views
Registered: ‎04-16-2012
Hello

Since you are using Virtex 7 device, can you please try programming with vivado and see the issue occurs.

Thanks,
vinay
--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.
0 Kudos
kkn
Moderator
Moderator
7,290 Views
Registered: ‎01-15-2008

can you copy the impact log files to this thread.

 

--Krishna

0 Kudos
gudurvenkatesh
Observer
Observer
7,289 Views
Registered: ‎04-14-2014

Thanks for your time and reply.

 

I have worked on few other programs related to the same board. I successfully programmed them and get those works done. But this time its not the same. Everything is fine till programming but once I program I see that the JTAG is not working properly. Also I dont have experience in working in Vivado. But what can be the reason for this? Whether something related to JTAG is getting changed after programming?

0 Kudos
gudurvenkatesh
Observer
Observer
7,262 Views
Registered: ‎04-14-2014

Thanks for your reply and time. Here is the log in iMPACT.

 

 



INFO:iMPACT:1777 -
Reading C:/Xilinx/14.7/ISE_DS/ISE/virtex7/data/xc7vx485t.bsd...
INFO:iMPACT - Using CseAdapterBSDevice
INFO:iMPACT:2257 - Startup Clock has been changed to 'JtagClk' in the bitstream stored in memory,
but the original bitstream file remains unchanged.
UserID read from the bitstream file = 0xFFFFFFFF.
Data width read from the bitstream file = 1.
INFO:iMPACT:501 - '1': Added Device xc7vx485t successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
GUI --- Auto connect to cable...
INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4
INFO:iMPACT - Digilent Plugin: found 1 device(s).
INFO:iMPACT - Digilent Plugin: opening device: "JtagSmt1", SN:210203823474
INFO:iMPACT - Digilent Plugin: User Name: JtagSmt1
INFO:iMPACT - Digilent Plugin: Product Name: Digilent JTAG-SMT1
INFO:iMPACT - Digilent Plugin: Serial Number: 210203823474
INFO:iMPACT - Digilent Plugin: Product ID: 30800151
INFO:iMPACT - Digilent Plugin: Firmware Version: 0108
INFO:iMPACT - Digilent Plugin: JTAG Port Number: 0
INFO:iMPACT - Digilent Plugin: JTAG Clock Frequency: 10000000 Hz
INFO:iMPACT - Current time: 11/28/2014 2:25:53 PM
Maximum TCK operating frequency for this device chain: 66000000.
Validating chain...
Boundary-scan chain validated successfully.
1: Device Temperature: Current Reading:   34.63 C, Min. Reading:   29.21 C, Max. Reading:   35.12 C
1: VCCINT Supply: Current Reading:   1.002 V, Min. Reading:   1.002 V, Max. Reading:   1.005 V
1: VCCAUX Supply: Current Reading:   1.805 V, Min. Reading:   1.799 V, Max. Reading:   1.808 V
'1': IDCODE is '00110011011010000111000010010011'
'1': IDCODE is '33687093' (in hex).
'1': : Manufacturer's ID = Xilinx xc7vx485t, Version : 3
INFO:iMPACT - Current time: 11/28/2014 2:25:56 PM
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 66000000.
Validating chain...
Boundary-scan chain validated successfully.
1: Device Temperature: Current Reading:   34.63 C, Min. Reading:   29.21 C, Max. Reading:   35.12 C
1: VCCINT Supply: Current Reading:   1.005 V, Min. Reading:   1.002 V, Max. Reading:   1.005 V
1: VCCAUX Supply: Current Reading:   1.802 V, Min. Reading:   1.799 V, Max. Reading:   1.808 V
INFO:iMPACT - Creating XC7VX485T device.
PROGRESS_START - Starting Operation.
'1': Programming device...
done.
INFO:Cse - Error shows in the status register, release done bit is NOT 1.
INFO:Cse - Status register values:
INFO:Cse - 0000 0000 0000 0000 0000 0000 0000 0000
PROGRESS_END - End Operation.
Elapsed time =     17 sec.
 Match_cycle = NoWait.
Match cycle: NoWait
 LCK_cycle = NoWait.
LCK cycle: NoWait
INFO:iMPACT - '1': Checking done pin....done.
'1': Programmed successfully.
INFO:iMPACT - Current time: 11/28/2014 2:26:31 PM
INFO:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - '1':  Device IDCODE :        00000000000000000000000000000000
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000011011010000111000010010011

0 Kudos
gudurvenkatesh
Observer
Observer
11,790 Views
Registered: ‎04-14-2014

Got the solution.

 

I am using ChipScope Pro to see the outputs. What I have done is I didn't give physical constraints to output ports. And gave a switch to ignore this error. But while generating the bit file, I guess these unmapped output pins have disturbed the JTAG pins. Due to which after programming JTAG was not working.
Later I removed those output ports and made them internal signals. Then I generated programming file and programmed the FPGA. When I checked for device id, I got the correct device id. Thus JTAG is working after programming the bit file.

 

Thanks a lot for all of you for your time.

 

Regards

VY Gudur

View solution in original post

umamahe
Xilinx Employee
Xilinx Employee
7,245 Views
Registered: ‎08-01-2012

Getting the Device ID is the manufacturer’s ID is retrieved from the selected devices in the JTAG chain and displayed in a dialog box. It should not change. I guess after programming you are not executing command properly. Initialize the JTAG chain and then try. 

________________________________________________

Please mark this post as an "Accept as solution" in case if it helped to resolve your query. So that it will help to other forum users to directly refer to the answer.

Give kudos to this post in case if you think the information is useful and reply oriented.

0 Kudos