{"id":1142,"date":"2020-11-19T01:15:46","date_gmt":"2020-11-19T01:15:46","guid":{"rendered":"http:\/\/fpganow.com\/?p=1142"},"modified":"2020-11-19T01:15:46","modified_gmt":"2020-11-19T01:15:46","slug":"vivado-error-opt-31-67-and-how-i-fixed-it","status":"publish","type":"post","link":"https:\/\/fpganow.com\/index.php\/2020\/11\/19\/vivado-error-opt-31-67-and-how-i-fixed-it\/","title":{"rendered":"Vivado Error [Opt 31-67], and How I Fixed It."},"content":{"rendered":"\n

So I am dealing with the following scenarios:<\/p>\n

Scenario 1 – Genesys Zynq with SYZYGY SFP<\/strong><\/h4>\n

I have the Genesys Zynq UltraScale+ MPSoC 3EG board that does not provide direct access to the PHY pins, but has a SYZYGY port that I have plugged in to the SZG-DUALSFP module with an SFP connector.<\/p>\n

Scenario 2 – Arty A7 Artix-7 with 10\/100 Mbit PHY<\/strong><\/h4>\n

I have the Arty A7 Artx-7 FPGA Development Board that gives me direct access to the pins of a 10\/100 Mbit PHY.<\/p>\n

All I want to do is connect directly to a PHY so I can implement a LabVIEW based TCP\/IP core, and as a starting Proof-of-Concept, I will take the already existing LabVIEW FPGA implementation (see their examples) and bring the UDP echo sample in.<\/p>\n

So I create a design using the Arty board using a MicroBlaze processor, write a simple program and add an AXI Stream FIFO core and connect that to a custom verilog node that will hold the LabVIEW FPGA code.\u00a0 I do this because I want a way of communicating with the code running on the FPGA.\u00a0 The AXI Stream FIFO will bridge the LabVIEW FPGA code with the MicroBlaze processor, and what I will do is send some or all data received from the Ethernet PHY over the AXI Stream FIFO to a C++ application running on the MicroBlaze, and then via a UART connection that I make from my host computer to the Arty, see the results.<\/p>\n

I can also use this as a way to properly figure out how to use the SZG-DUALSFP module as well.<\/p>\n

Long story short, I add an AXI-Stream FIFO that is connected to a labview_ip node which will house my LabVIEW FPGA exported code.\u00a0 And for now I create a simple file that echoes a random packet of five 32-bit WORDS once per second.<\/p>\n

\"\"<\/a><\/p>\n

Optimization Error<\/strong><\/h4>\n

So I create this custom Verilog code, and click Generate Bitstream.\u00a0 After a few minutes I get the error mentioned in the title of this article.\u00a0 I originally had no idea how to debug this, but after some time on Xilinx Forums I figured it out… I forgot to wire up one value, and the design optimization removed it since it was unwired.\u00a0 Anyway, if you are using Vivado and you get this error, please continue…<\/p>\n

[Opt 31-67] Problem: A LUT3 cell in the design is missing a connection on input pin I2, which is used by the LUT equation. This pin has either been left unconnected in the design or the connection was removed due to the trimming of unused logic. The LUT cell name is: design_1_i\/axi_fifo_mm_s_0\/U0\/COMP_IPIC2AXI_S\/gtxd.COMP_TXD_FIFO\/gfifo_gen.COMP_AXIS_FG_FIFO\/COMP_FIFO\/xpm_fifo_base_inst_i_1.<\/pre>\n
\"\"<\/a><\/p>\n
\"\"<\/a><\/p>\n
So the LUT cell name is:<\/p>\n
design_1_i\/axi_fifo_mm_s_0\/U0\/COMP_IPIC2AXI_S\/gtxd.COMP_TXD_FIFO\/gfifo_gen.COMP_AXIS_FG_FIFO\/COMP_FIFO\/xpm_fifo_base_inst_i_1<\/pre>\n
I manually run ‘Optimize Design’ with the the following commands:<\/p>\n
set_param messaging.defaultLimit 100000
opt_design -verbose<\/pre>\n
(See: https:\/\/www.xilinx.com\/support\/answers\/58616.html<\/a> for more details on using this approach)<\/p>\n
This reproduces the error, but the error appears in the TCL Console this time.<\/p>\n
I open the Synthesized Design (‘Open Synthesized Design’ option on the left side-bar):<\/p>\n
\"\"<\/a><\/p>\n
Show the object\/cell by using the TCL console:<\/h4>\n
show_objects [ get_cells {design_1_i\/axi_fifo_mm_s_0\/U0\/COMP_IPIC2AXI_S\/gtxd.COMP_TXD_FIFO\/gfifo_gen.COMP_AXIS_FG_FIFO\/COMP_FIFO\/xpm_fifo_base_inst_i_1}]<\/pre>\n
Which shows me this:<\/p>\n
\"\"<\/a><\/p>\n
Then I go to the schematic by right-clicking on the cell and selecting ‘Schematic’:<\/p>\n
\"\"<\/a><\/p>\n
So this schematic shows that the signal I2 is unconnected. Now what is I2? I have no idea…\u00a0<\/p>\n
\"\"<\/a><\/p>\n
So I get more information by right-clicking and selecting ‘Expand Cone->To Selected Cells’:<\/p>\n
\"\"<\/a><\/p>\n
The schematic will be pretty big, however the selected cell will be highlighted in blue and zoomed in like so:<\/p>\n
\"\"<\/a><\/p>\n
\u00a0<\/p>\n
Then I follow the output wire until I find where it goes, notice that the wire is connected to ‘rd_en’<\/strong>, which sounds a lot like ‘Read Enable’<\/strong> which is a port that the FIFO should have connected.\u00a0<\/p>\n
\"\"<\/a><\/p>\n
Now this might be too vague, so what if I wanted to know what component or cell the rd_en signal is going to? I right-click on the border of this cell\/component and select ‘Expand\/Collapse->Collapse Inside’:<\/p>\n
\"\"<\/a><\/p>\n
With this view, I know immediately what is wrong, I must have never wired the ready or ‘Ready for Input’ signal somewhere between the AXI-Stream FIFO and my custom IP.<\/p>\n
\"\"<\/a><\/p>\n
And here is a slightly zoomed out view:<\/p>\n
\"\"<\/a><\/p>\n
I go back to my Verilog code and realize that I never assigned a value to the ‘Transmit Ready’ signal – even though I would have expected this to work and to default to a value of 0.<\/p>\n
For the curious, adding line 128 fixed the error:<\/p>\n
\"\"<\/a><\/p>\n
\u00a0<\/p>\n
\u00a0<\/p>\n
\u00a0<\/p>\n
\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"
So I am dealing with the following scenarios: Scenario 1 – Genesys Zynq with SYZYGY SFP I have the Genesys Zynq UltraScale+ MPSoC 3EG board that does not provide direct access to the PHY pins, but has a SYZYGY port that I have plugged in to the SZG-DUALSFP module with an SFP connector. Scenario 2 … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-1142","post","type-post","status-publish","format-standard","hentry","category-uncategorized","masonry-post","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50"],"_links":{"self":[{"href":"https:\/\/fpganow.com\/index.php\/wp-json\/wp\/v2\/posts\/1142","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fpganow.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fpganow.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fpganow.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fpganow.com\/index.php\/wp-json\/wp\/v2\/comments?post=1142"}],"version-history":[{"count":9,"href":"https:\/\/fpganow.com\/index.php\/wp-json\/wp\/v2\/posts\/1142\/revisions"}],"predecessor-version":[{"id":1169,"href":"https:\/\/fpganow.com\/index.php\/wp-json\/wp\/v2\/posts\/1142\/revisions\/1169"}],"wp:attachment":[{"href":"https:\/\/fpganow.com\/index.php\/wp-json\/wp\/v2\/media?parent=1142"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fpganow.com\/index.php\/wp-json\/wp\/v2\/categories?post=1142"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fpganow.com\/index.php\/wp-json\/wp\/v2\/tags?post=1142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}