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: 
Adventurer
Adventurer
10,789 Views
Registered: ‎09-25-2015

VC709 V1.0, cannot flash BPI, Vivado 2016.1 ==> Xilinx specialist needed

Jump to solution

Hello,

 

I am not able to flash the board. This is needed as I want to place it into a PC unsing its PCI interface. At first I wanted to test general functionality with the TRD demo design and it looks, like that was not on the flash.

 

So - no problem. We have the design files also and .tcl scripts to do the flashing ... but: they all fail with erase errors.

Then I used the GUI and got similar results....

Before I forget to mention: The SW2 is set to '00000000' and SW11 to '00010' as everywhere described.

 

Then I modified the Flash type as different versions of the board have different types. Still no luck ...

I believe (from chip imprints) that I have a "00AG18F" which should be the alias of "mt28gu01gaax1e-bpi-x16"

Here is the link to the design files: https://secure.xilinx.com/webreg/clickthrough.do?cid=373411

 

I add the output of Vivado below.

 

ANY help is welcome and really appreciated!

Thanks!

 

start_gui
open_hw
INFO: [IP_Flow 19-234] Refreshing IP repositories
INFO: [IP_Flow 19-1704] No user IP repositories specified
INFO: [IP_Flow 19-2313] Loaded Vivado IP repository 'C:/Xilinx/Vivado/2016.1/data/ip'.
connect_hw_server
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
INFO: [Labtools 27-2222] Launching hw_server...
INFO: [Labtools 27-2221] Launch Output:

****** Xilinx hw_server v2016.1
  **** Build date : Apr  8 2016-16:12:32
    ** Copyright 1986-2016 Xilinx, Inc. All Rights Reserved.


open_hw_target
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210203825728A
current_hw_device [lindex [get_hw_devices] 0]
refresh_hw_device -update_hw_probes false [lindex [get_hw_devices] 0]
INFO: [Labtools 27-1435] Device xc7vx690t (JTAG device index = 0) is not programmed (DONE status = 0).
refresh_hw_device [lindex [get_hw_devices] 0]
INFO: [Labtools 27-1435] Device xc7vx690t (JTAG device index = 0) is not programmed (DONE status = 0).
create_hw_cfgmem -hw_device [lindex [get_hw_devices] 0] -mem_dev  [lindex [get_cfgmem_parts {mt28gu01gaax1e-bpi-x16}] 0]
set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.ERASE  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.CFG_PROGRAM  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.VERIFY  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.CHECKSUM  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
refresh_hw_device [lindex [get_hw_devices] 0]
INFO: [Labtools 27-1435] Device xc7vx690t (JTAG device index = 0) is not programmed (DONE status = 0).
set_property PROGRAM.ADDRESS_RANGE  {use_file} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.FILES [list "F:/trd/ready_to_test/VC709.mcs" ] [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0]]
set_property PROGRAM.BPI_RS_PINS {none} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.UNUSED_PIN_TERMINATION {pull-none} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.ERASE  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.CFG_PROGRAM  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.VERIFY  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.CHECKSUM  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
startgroup 
if {![string equal [get_property PROGRAM.HW_CFGMEM_TYPE  [lindex [get_hw_devices] 0]] [get_property MEM_TYPE [get_property CFGMEM_PART [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]]]] }  { create_hw_bitstream -hw_device [lindex [get_hw_devices] 0] [get_property PROGRAM.HW_CFGMEM_BITFILE [ lindex [get_hw_devices] 0]]; program_hw_devices [lindex [get_hw_devices] 0]; }; 
INFO: [Labtools 27-3164] End of startup status: HIGH
program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
Mfg ID : 0   Memory Type : 0   Memory Capacity : 0   Device ID 1 : 0   Device ID 2 : 0
Performing Erase Operation...
Erase Operation failed.
ERROR: [Labtools 27-3161] Flash Programming Unsuccessful
ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.

set_property PROGRAM.ADDRESS_RANGE  {use_file} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.FILES [list "F:/trd/ready_to_test/VC709.mcs" ] [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0]]
set_property PROGRAM.BPI_RS_PINS {none} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.UNUSED_PIN_TERMINATION {pull-none} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.ERASE  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.CFG_PROGRAM  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.VERIFY  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.CHECKSUM  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
startgroup 
if {![string equal [get_property PROGRAM.HW_CFGMEM_TYPE  [lindex [get_hw_devices] 0]] [get_property MEM_TYPE [get_property CFGMEM_PART [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]]]] }  { create_hw_bitstream -hw_device [lindex [get_hw_devices] 0] [get_property PROGRAM.HW_CFGMEM_BITFILE [ lindex [get_hw_devices] 0]]; program_hw_devices [lindex [get_hw_devices] 0]; }; 
INFO: [Labtools 27-3164] End of startup status: HIGH
program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
Mfg ID : 0   Memory Type : 0   Memory Capacity : 0   Device ID 1 : 0   Device ID 2 : 0
Performing Program Operation...
Program/Verify Operation failed.

ERROR: [Labtools 27-3144] Invalid option: 
ERROR: [Labtools 27-3161] Flash Programming Unsuccessful
program_hw_cfgmem: Time (s): cpu = 00:00:04 ; elapsed = 00:00:50 . Memory (MB): peak = 923.496 ; gain = 16.602
ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.

set_property CFGMEM_PART {mt28gu01gaax1e-bpi-x16} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0]]
set_property PROGRAM.ADDRESS_RANGE  {entire_device} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.UNUSED_PIN_TERMINATION {pull-none} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.ERASE  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.CFG_PROGRAM  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.VERIFY  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
set_property PROGRAM.CHECKSUM  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
startgroup 
if {![string equal [get_property PROGRAM.HW_CFGMEM_TYPE  [lindex [get_hw_devices] 0]] [get_property MEM_TYPE [get_property CFGMEM_PART [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]]]] }  { create_hw_bitstream -hw_device [lindex [get_hw_devices] 0] [get_property PROGRAM.HW_CFGMEM_BITFILE [ lindex [get_hw_devices] 0]]; program_hw_devices [lindex [get_hw_devices] 0]; }; 
INFO: [Labtools 27-3164] End of startup status: HIGH
program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
Mfg ID : 0   Memory Type : 0   Memory Capacity : 0   Device ID 1 : 0   Device ID 2 : 0
Performing Erase Operation...
Erase Operation failed.
ERROR: [Labtools 27-3161] Flash Programming Unsuccessful
ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.
set_property CFGMEM_PART {mt28gu01gaax1e-bpi-x16} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0]]

 

0 Kudos
1 Solution

Accepted Solutions
Adventurer
Adventurer
13,196 Views
Registered: ‎09-25-2015

Re: VC709 V1.0, cannot flash BPI, Vivado 2016.1 ==> Xilinx specialist needed

Jump to solution

Hi markzak,

 

I have an update for you ... not sure whether it helps you:

 

One year ago I experimented with the VC709 board and tried the BIST (BuildInSelfTest). There was a flash test integrated, which I tried.

 

My fault was to compile the test by myself and to debug it with the SDK. I tried out to debug the Flash-Test part and stopped in between.

 

The Flash test contains several parts:

  1. Init
  2. Lock device
  3. Try to write
  4. Success if write deny
  5. Unlock device
  6. write data
  7. read data
  8. verify data
  9. compare, success if equal

I broke with the debugger at 3 or 4.

 

Then I did different things and forgot about this - meaning the device was still locked all the time.

Unfortunately: The state of the device cannot be changed back by the test anymore because the init (1) tries to write the device(!) to get the endianness of it (which fails, whereas the init itself fails) ...

 

I had to modify the BIST to ignore those errors during initialization and directly go to unlock device.

 

Then: it works pretty fine again until now - for me.

 

==> I already asked Xilinx to change the BIST code, don't know whether they do or not.

 

/Jesko

 

View solution in original post

0 Kudos
6 Replies
Scholar pratham
Scholar
10,772 Views
Registered: ‎06-05-2013

Re: VC709 V1.0, cannot flash BPI, Vivado 2016.1 ==> Xilinx specialist needed

Jump to solution

@jesko Can you please follow debug guidelines given in the below AR?

http://www.xilinx.com/support/answers/54355.html

-Pratham

----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
0 Kudos
Adventurer
Adventurer
10,398 Views
Registered: ‎09-25-2015

Re: VC709 V1.0, cannot flash BPI, Vivado 2016.1 ==> Xilinx specialist needed

Jump to solution

Hi Pratham,

 

was on a business trip without the board ...

 

I have tried various things. At least I tried the Multi-Boot.

http://xgoogle.xilinx.com/search?output=xml_no_dtd&ie=UTF-8&oe=UTF-8&client=xilinx&proxystylesheet=xilinx&site=Documentation&filter=0&num=10&sort=date:D:L:d1&getfields=%2a&show_dynamic_navigation=1&as_epq=VC709%20Multiboot%20Tutorial&as_occt=any&requ...

 

There is everything explained and I did as shown but still no luck.

 

From the "source vc709_program_bpi.tcl" command I get

Vivado% source vc709_program_bpi.tcl
# open_hw
# connect_hw_server -url localhost:3121
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
INFO: [Labtools 27-2222] Launching hw_server...
INFO: [Labtools 27-2221] Launch Output:

****** Xilinx hw_server v2016.1
  **** Build date : Apr  8 2016-16:12:32
    ** Copyright 1986-2016 Xilinx, Inc. All Rights Reserved.


connect_hw_server: Time (s): cpu = 00:00:00 ; elapsed = 00:00:06 . Memory (MB): peak = 234.914 ; gain = 1.738
# current_hw_target [get_hw_targets */xilinx_tcf/Digilent/*]
# set_property PARAM.FREQUENCY 15000000 [get_hw_targets */xilinx_tcf/Digilent/*]
# open_hw_target
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210203825728A
# current_hw_device [lindex [get_hw_devices] 0]
# refresh_hw_device [lindex [get_hw_devices] 0]
INFO: [Labtools 27-1435] Device xc7vx690t (JTAG device index = 0) is not programmed (DONE status = 0).
# create_hw_cfgmem -hw_device [lindex [get_hw_devices] 0] -mem_dev  [lindex [get_cfgmem_parts {mt28gu01gaax1e-bpi-x16}] 0]
# set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.ERASE  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.CFG_PROGRAM  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.VERIFY  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# refresh_hw_device [lindex [get_hw_devices] 0]
INFO: [Labtools 27-1435] Device xc7vx690t (JTAG device index = 0) is not programmed (DONE status = 0).
# set_property PROGRAM.ADDRESS_RANGE  {use_file} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.FILE {vc709_multiboot_bpi.mcs} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0]]
WARNING: [Common 17-599] Property 'PROGRAM.FILE' is deprecated for object type 'hw_cfgmem'. Use PROGRAM.FILES property.
# set_property PROGRAM.UNUSED_PIN_TERMINATION {pull-none} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.BPI_RS_PINS {25:24} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.ERASE  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.CFG_PROGRAM  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.VERIFY  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# if {![string equal [get_property PROGRAM.HW_CFGMEM_TYPE  [lindex [get_hw_devices] 0]] [get_property MEM_TYPE [get_property CFGMEM_PART [get_property PROGRAM.H
W_CFGMEM [lindex [get_hw_devices] 0 ]]]]] }  { create_hw_bitstream -hw_device [lindex [get_hw_devices] 0] [get_property PROGRAM.HW_CFGMEM_BITFILE [ lindex [get_
hw_devices] 0]]; program_hw_devices [lindex [get_hw_devices] 0]; };
INFO: [Labtools 27-3164] End of startup status: HIGH
# program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
MCS programming start address 0x00800000 should be a multiple of the flash program buffer size (2104623104/0x7D720000 bytes).
ERROR: [Labtools 27-3161] Flash Programming Unsuccessful
ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.

    while executing
"program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]"
    (file "vc709_program_bpi.tcl" line 23)

Vivado% source vc709_program_bpi.tcl
# open_hw
# connect_hw_server -url localhost:3121
ERROR: [Labtoolstcl 44-586] Disconnect server connection, TCP:localhost:3121, before making a new one.

Vivado%

Additionally I cannot see the flash device if I open the Vivado Hardware Manager and select "Open target/Auto connect" ...

 

SW11 seems to be correct "00010" ...

 

What can I do?

0 Kudos
Highlighted
Visitor dlisi_src
Visitor
9,765 Views
Registered: ‎05-20-2016

Re: VC709 V1.0, cannot flash BPI, Vivado 2016.1 ==> Xilinx specialist needed

Jump to solution

I am seeing identical issues with a VC707 board and Vivado 2016.1. Same as @jesko I have all of the switches set to default.

 

When I try to use the GUI the flash fails to erase. When I try to use the BIST programming scripts I get:

 

C:\vc707_restore_flash>call C:\\Xilinx\\Vivado\\2016.1\\.\\bin\\vivado.bat -mode batch -source vc707_program_bpi.tcl

****** Vivado v2016.1 (64-bit)
  **** SW Build 1538259 on Fri Apr  8 15:45:27 MDT 2016
  **** IP Build 1537824 on Fri Apr  8 04:28:57 MDT 2016
    ** Copyright 1986-2016 Xilinx, Inc. All Rights Reserved.

source vc707_program_bpi.tcl
# open_hw
# connect_hw_server -url localhost:3121
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
# current_hw_target [get_hw_targets */xilinx_tcf/Digilent/*]
# set_property PARAM.FREQUENCY 30000000 [get_hw_targets */xilinx_tcf/Digilent/*]
# open_hw_target
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210203344279A
# current_hw_device [lindex [get_hw_devices] 0]
# refresh_hw_device [lindex [get_hw_devices] 0]
INFO: [Labtools 27-2302] Device xc7vx485t (JTAG device index = 0) is programmed with a design that has 1 BPI core(s).
# create_hw_cfgmem -hw_device [lindex [get_hw_devices] 0] -mem_dev  [lindex [get_cfgmem_parts {mt28gu01gaax1e-bpi-x16}] 0]
# set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.ERASE  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.CFG_PROGRAM  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.VERIFY  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# refresh_hw_device [lindex [get_hw_devices] 0]
INFO: [Labtools 27-2302] Device xc7vx485t (JTAG device index = 0) is programmed with a design that has 1 BPI core(s).
# set_property PROGRAM.ADDRESS_RANGE  {use_file} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.FILE {vc707_bpi_flash_0.mcs} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0]]
WARNING: [Common 17-599] Property 'PROGRAM.FILE' is deprecated for object type 'hw_cfgmem'. Use PROGRAM.FILES property.
# set_property PROGRAM.UNUSED_PIN_TERMINATION {pull-none} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.BPI_RS_PINS {25:24} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.ERASE  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.CFG_PROGRAM  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.VERIFY  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# if {![string equal [get_property PROGRAM.HW_CFGMEM_TYPE  [lindex [get_hw_devices] 0]] [get_property MEM_TYPE [get_property CFGMEM_PART [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
] }  { create_hw_bitstream -hw_device [lindex [get_hw_devices] 0] [get_property PROGRAM.HW_CFGMEM_BITFILE [ lindex [get_hw_devices] 0]]; program_hw_devices [lindex [get_hw_devices] 0]; };
INFO: [Labtools 27-3164] End of startup status: HIGH
# program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
MCS programming start address 0x00800000 should be a multiple of the flash program buffer size (4225892352/0xFBE20000 bytes).
ERROR: [Labtools 27-3161] Flash Programming Unsuccessful
ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.

    while executing
"program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]"
    (file "vc707_program_bpi.tcl" line 23)
INFO: [Common 17-206] Exiting Vivado at Tue Jun 21 13:56:55 2016...
Press any key to continue . . .

 

Any ideas?

0 Kudos
Visitor dlisi_src
Visitor
9,760 Views
Registered: ‎05-20-2016

Re: VC709 V1.0, cannot flash BPI, Vivado 2016.1 ==> Xilinx specialist needed

Jump to solution

Ironically I get more information if I try to use 2014.4 to do the programming.

 

****** Vivado v2014.4 (64-bit)
  **** SW Build 1071353 on Tue Nov 18 18:29:27 MST 2014
  **** IP Build 1070531 on Tue Nov 18 01:10:18 MST 2014
    ** Copyright 1986-2014 Xilinx, Inc. All Rights Reserved.

source vc707_program_bpi.tcl
# open_hw
# connect_hw_server -url localhost:3121
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
# current_hw_target [get_hw_targets */xilinx_tcf/Digilent/*]
# set_property PARAM.FREQUENCY 30000000 [get_hw_targets */xilinx_tcf/Digilent/*]
# open_hw_target
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210203344279A
# current_hw_device [lindex [get_hw_devices] 0]
# refresh_hw_device [lindex [get_hw_devices] 0]
INFO: [Labtools 27-1434] Device xc7vx485t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3123] The debug hub core was not detected at User Scan Chain 1 or 3.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active OR
2. Manually launch hw_server with -e "set xsdb-user-bscan <C_USER_SCAN_CHAIN scan_chain_number>" to detect the debug hub at User Scan Chain of 2 or 4. To determine the user scan chain setting, open th
e implemented design and use: get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub].
# create_hw_cfgmem -hw_device [lindex [get_hw_devices] 0] -mem_dev  [lindex [get_cfgmem_parts {mt28gu01gaax1e-bpi-x16}] 0]
# set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.ERASE  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.CFG_PROGRAM  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.VERIFY  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# refresh_hw_device [lindex [get_hw_devices] 0]
INFO: [Labtools 27-1434] Device xc7vx485t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3123] The debug hub core was not detected at User Scan Chain 1 or 3.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active OR
2. Manually launch hw_server with -e "set xsdb-user-bscan <C_USER_SCAN_CHAIN scan_chain_number>" to detect the debug hub at User Scan Chain of 2 or 4. To determine the user scan chain setting, open th
e implemented design and use: get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub].
# set_property PROGRAM.ADDRESS_RANGE  {use_file} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.FILE {vc707_bpi_flash_0.mcs} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0]]
WARNING: [Common 17-599] Property 'PROGRAM.FILE' is deprecated for object type 'hw_cfgmem'. Use PROGRAM.FILES property.
# set_property PROGRAM.UNUSED_PIN_TERMINATION {pull-none} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.BPI_RS_PINS {25:24} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.BLANK_CHECK  0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.ERASE  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.CFG_PROGRAM  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# set_property PROGRAM.VERIFY  1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
# if {![string equal [get_property PROGRAM.HW_CFGMEM_TYPE  [lindex [get_hw_devices] 0]] [get_property MEM_TYPE [get_property CFGMEM_PART [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]]]
] }  { create_hw_bitstream -hw_device [lindex [get_hw_devices] 0] [get_property PROGRAM.HW_CFGMEM_BITFILE [ lindex [get_hw_devices] 0]]; program_hw_devices [lindex [get_hw_devices] 0]; };
INFO: [Labtools 27-32] Done pin status: HIGH
# program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
Mfg ID : 0   Memory Type : 0   Device ID 1 : 0   Device ID 2 : 0
ERROR: [Labtools 27-2251] Unable to read device properties. Please make sure that the proper configuration memory part is selected.
ERROR: [Labtoolstcl 44-473] Flash programming failed

    while executing
"program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]"
    (file "vc707_program_bpi.tcl" line 23)
INFO: [Common 17-206] Exiting Vivado at Tue Jun 21 14:13:35 2016...
Press any key to continue . . .
0 Kudos
Explorer
Explorer
9,099 Views
Registered: ‎12-01-2010

Re: VC709 V1.0, cannot flash BPI, Vivado 2016.1 ==> Xilinx specialist needed

Jump to solution

Any updates to this thread?  I also am suddenly having Flash programming errors since installing 2016.1

0 Kudos
Adventurer
Adventurer
13,197 Views
Registered: ‎09-25-2015

Re: VC709 V1.0, cannot flash BPI, Vivado 2016.1 ==> Xilinx specialist needed

Jump to solution

Hi markzak,

 

I have an update for you ... not sure whether it helps you:

 

One year ago I experimented with the VC709 board and tried the BIST (BuildInSelfTest). There was a flash test integrated, which I tried.

 

My fault was to compile the test by myself and to debug it with the SDK. I tried out to debug the Flash-Test part and stopped in between.

 

The Flash test contains several parts:

  1. Init
  2. Lock device
  3. Try to write
  4. Success if write deny
  5. Unlock device
  6. write data
  7. read data
  8. verify data
  9. compare, success if equal

I broke with the debugger at 3 or 4.

 

Then I did different things and forgot about this - meaning the device was still locked all the time.

Unfortunately: The state of the device cannot be changed back by the test anymore because the init (1) tries to write the device(!) to get the endianness of it (which fails, whereas the init itself fails) ...

 

I had to modify the BIST to ignore those errors during initialization and directly go to unlock device.

 

Then: it works pretty fine again until now - for me.

 

==> I already asked Xilinx to change the BIST code, don't know whether they do or not.

 

/Jesko

 

View solution in original post

0 Kudos