3C7-Assignment-1/vivado.log at master · dslogget/3C7-Assignment-1 · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
#-----------------------------------------------------------
# Vivado v2017.4 (64-bit)
# SW Build 2086221 on Fri Dec 15 20:55:39 MST 2017
# IP Build 2085800 on Fri Dec 15 22:25:07 MST 2017
# Start of session at: Thu Feb 28 17:38:29 2019
# Process ID: 9980
# Current directory: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1
# Command line: vivado.exe -gui_launcher_event rodinguilauncherevent4292 C:\Users\Daniel\Documents\College\3C7\3C7-Assignment-1\Assignment1.xpr
# Log file: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/vivado.log
# Journal file: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1\vivado.jou
#-----------------------------------------------------------
start_gui
open_project C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.xpr
INFO: [Project 1-313] Project file moved from 'E:/Vivado/Assignment1' since last save.
Scanning sources...
Finished scanning sources
WARNING: [filemgmt 56-2] Board Part Repository Path: Could not find the directory 'C:/Users/Daniel/Documents/College/3C7/vivado-boards-master/new/board_files', nor could it be found using path 'E:/Vivado/vivado-boards-master/new/board_files'.
CRITICAL WARNING: [Board 49-67] The board_part definition was not found for digilentinc.com:basys3:part0:1.1. This can happen sometimes when you use custom board part. You can resolve this issue by setting 'board.repoPaths' parameter, pointing to the location of custom board files. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command.
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/2017.4/data/ip'.
open_project: Time (s): cpu = 00:00:13 ; elapsed = 00:00:36 . Memory (MB): peak = 725.680 ; gain = 70.371
update_compile_order -fileset sources_1
WARNING: [filemgmt 56-199] Attempt to get parsing info during refresh. "On-the-fly" syntax checking information may be incorrect. [C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.srcs/sources_1/new/Display.v:]
WARNING: [filemgmt 56-199] Attempt to get parsing info during refresh. "On-the-fly" syntax checking information may be incorrect. [C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.srcs/sources_1/new/BoardMap.v:]
reset_run synth_1
launch_runs synth_1 -jobs 8
[Thu Feb 28 17:44:58 2019] Launched synth_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/synth_1/runme.log
reset_run synth_1
launch_runs synth_1 -jobs 8
[Thu Feb 28 17:52:40 2019] Launched synth_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/synth_1/runme.log
reset_run synth_1
launch_runs impl_1 -to_step write_bitstream -jobs 8
[Thu Feb 28 17:57:55 2019] Launched synth_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/synth_1/runme.log
[Thu Feb 28 17:57:55 2019] Launched impl_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/runme.log
open_hw
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 v2017.4
  **** Build date : Dec 15 2017-21:08:27
    ** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.


connect_hw_server: Time (s): cpu = 00:00:00 ; elapsed = 00:00:07 . Memory (MB): peak = 848.980 ; gain = 1.328
open_hw_target
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210183A75A3BA
set_property PROGRAM.FILE {C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/BoardMap.bit} [get_hw_devices xc7a35t_0]
current_hw_device [get_hw_devices xc7a35t_0]
refresh_hw_device -update_hw_probes false [lindex [get_hw_devices xc7a35t_0] 0]
INFO: [Labtools 27-1434] Device xc7a35t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device.  To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).
set_property PROBES.FILE {} [get_hw_devices xc7a35t_0]
set_property FULL_PROBES.FILE {} [get_hw_devices xc7a35t_0]
set_property PROGRAM.FILE {C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/BoardMap.bit} [get_hw_devices xc7a35t_0]
program_hw_devices [get_hw_devices xc7a35t_0]
INFO: [Labtools 27-3164] End of startup status: HIGH
refresh_hw_device [lindex [get_hw_devices xc7a35t_0] 0]
INFO: [Labtools 27-1434] Device xc7a35t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device.  To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).
reset_run synth_1
launch_runs impl_1 -to_step write_bitstream -jobs 8
[Thu Feb 28 18:08:11 2019] Launched synth_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/synth_1/runme.log
[Thu Feb 28 18:08:11 2019] Launched impl_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/runme.log
reset_run synth_1
launch_runs impl_1 -to_step write_bitstream -jobs 8
[Thu Feb 28 18:14:31 2019] Launched synth_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/synth_1/runme.log
[Thu Feb 28 18:14:31 2019] Launched impl_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/runme.log
reset_run synth_1
launch_runs impl_1 -to_step write_bitstream -jobs 8
[Thu Feb 28 18:26:43 2019] Launched synth_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/synth_1/runme.log
[Thu Feb 28 18:26:43 2019] Launched impl_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/runme.log
set_property PROBES.FILE {} [get_hw_devices xc7a35t_0]
set_property FULL_PROBES.FILE {} [get_hw_devices xc7a35t_0]
set_property PROGRAM.FILE {C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/BoardMap.bit} [get_hw_devices xc7a35t_0]
program_hw_devices [get_hw_devices xc7a35t_0]
INFO: [Labtools 27-3164] End of startup status: HIGH
refresh_hw_device [lindex [get_hw_devices xc7a35t_0] 0]
INFO: [Labtools 27-1434] Device xc7a35t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device.  To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).
reset_run synth_1
launch_runs impl_1 -to_step write_bitstream -jobs 8
[Thu Feb 28 18:55:29 2019] Launched synth_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/synth_1/runme.log
[Thu Feb 28 18:55:29 2019] Launched impl_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/runme.log
set_property PROBES.FILE {} [get_hw_devices xc7a35t_0]
set_property FULL_PROBES.FILE {} [get_hw_devices xc7a35t_0]
set_property PROGRAM.FILE {C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/BoardMap.bit} [get_hw_devices xc7a35t_0]
program_hw_devices [get_hw_devices xc7a35t_0]
INFO: [Labtools 27-3164] End of startup status: HIGH
refresh_hw_device [lindex [get_hw_devices xc7a35t_0] 0]
INFO: [Labtools 27-1434] Device xc7a35t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device.  To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).
reset_run synth_1
launch_runs impl_1 -to_step write_bitstream -jobs 8
[Thu Feb 28 19:00:57 2019] Launched synth_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/synth_1/runme.log
[Thu Feb 28 19:00:57 2019] Launched impl_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/runme.log
reset_run synth_1
launch_runs impl_1 -to_step write_bitstream -jobs 8
[Thu Feb 28 19:07:07 2019] Launched synth_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/synth_1/runme.log
[Thu Feb 28 19:07:07 2019] Launched impl_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/runme.log
set_property PROBES.FILE {} [get_hw_devices xc7a35t_0]
set_property FULL_PROBES.FILE {} [get_hw_devices xc7a35t_0]
set_property PROGRAM.FILE {C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/BoardMap.bit} [get_hw_devices xc7a35t_0]
program_hw_devices [get_hw_devices xc7a35t_0]
INFO: [Labtools 27-3164] End of startup status: HIGH
refresh_hw_device [lindex [get_hw_devices xc7a35t_0] 0]
INFO: [Labtools 27-1434] Device xc7a35t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device.  To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).
reset_run synth_1
launch_runs impl_1 -to_step write_bitstream -jobs 8
[Thu Feb 28 19:10:39 2019] Launched synth_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/synth_1/runme.log
[Thu Feb 28 19:10:39 2019] Launched impl_1...
Run output will be captured here: C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/runme.log
ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/210183A75A3BA
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210183A75A3BA
INFO: [Labtools 27-1434] Device xc7a35t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device.  To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).
WARNING: [Labtoolstcl 44-129] No matching hw_ila_data was found.
ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/210183A75A3BA
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210183A75A3BA
INFO: [Labtools 27-1434] Device xc7a35t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device.  To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).
WARNING: [Labtoolstcl 44-129] No matching hw_ila_data was found.
ERROR: [Labtoolstcl 44-513] HW Target shutdown. Closing target: localhost:3121/xilinx_tcf/Digilent/210183A75A3BA
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210183A75A3BA
INFO: [Labtools 27-1434] Device xc7a35t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device.  To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).
WARNING: [Labtoolstcl 44-129] No matching hw_ila_data was found.
set_property PROBES.FILE {} [get_hw_devices xc7a35t_0]
set_property FULL_PROBES.FILE {} [get_hw_devices xc7a35t_0]
set_property PROGRAM.FILE {C:/Users/Daniel/Documents/College/3C7/3C7-Assignment-1/Assignment1.runs/impl_1/BoardMap.bit} [get_hw_devices xc7a35t_0]
program_hw_devices [get_hw_devices xc7a35t_0]
INFO: [Labtools 27-3164] End of startup status: HIGH
refresh_hw_device [lindex [get_hw_devices xc7a35t_0] 0]
INFO: [Labtools 27-1434] Device xc7a35t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Labtools 27-3361] The debug hub core was not detected.
Resolution:
1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active.
2. Make sure the BSCAN_SWITCH_USER_MASK device property in Vivado Hardware Manager reflects the user scan chain setting in the design and refresh the device.  To determine the user scan chain setting in the design, open the implemented design and use 'get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]'.
For more details on setting the scan chain property, consult the Vivado Debug and Programming User Guide (UG908).