<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>VLSI on Raveen Kumar</title>
    <link>https://raveenkumar.com/library/programming/vlsi/</link>
    <description>Recent content in VLSI on Raveen Kumar</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <copyright>Raveen Kumar</copyright>
    <lastBuildDate>Fri, 17 Feb 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://raveenkumar.com/library/programming/vlsi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Simulations</title>
      <link>https://raveenkumar.com/library/programming/vlsi/simulations/</link>
      <pubDate>Fri, 17 Feb 2023 00:00:00 +0000</pubDate>
      <guid>https://raveenkumar.com/library/programming/vlsi/simulations/</guid>
      <description>&lt;p&gt;Notes on compiling a testbench with &lt;code&gt;irun&lt;/code&gt;. The file list it compiles lives&#xA;in &lt;code&gt;irun_args_compile&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;add-every-new-file-to-irun_args_compile&#34;&gt;Add every new file to &lt;code&gt;irun_args_compile&lt;/code&gt;&lt;/h2&gt;&#xA;&lt;p&gt;A new file stays out of the compile until you list it there.&lt;/p&gt;&#xA;&lt;h2 id=&#34;dont-compile-a-file-or-directory-twice&#34;&gt;Don&amp;rsquo;t compile a file or directory twice&lt;/h2&gt;&#xA;&lt;p&gt;Listing the same file or directory twice stops the compile with one of these&#xA;errors:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;code&gt;xmvlog: *E,COFILX&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;xmvlog: *E,ILLPDL&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;dont-include-a-file-that-is-already-compiled&#34;&gt;Don&amp;rsquo;t &lt;code&gt;`include&lt;/code&gt; a file that is already compiled&lt;/h2&gt;&#xA;&lt;p&gt;If &lt;code&gt;irun_args_compile&lt;/code&gt; already compiles a file, the &lt;code&gt;.sv&lt;/code&gt; file doesn&amp;rsquo;t need to&#xA;&lt;code&gt;`include&lt;/code&gt; it again.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SystemVerilog, verilog and UVM notes</title>
      <link>https://raveenkumar.com/library/programming/vlsi/system_verilog_and_uvm/</link>
      <pubDate>Fri, 17 Feb 2023 00:00:00 +0000</pubDate>
      <guid>https://raveenkumar.com/library/programming/vlsi/system_verilog_and_uvm/</guid>
      <description>&lt;h2 id=&#34;reading-materials&#34;&gt;Reading Materials&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.hdlworks.com/hdl_corner/verilog_ref/items/SystemSimulationTimeFuncs.htm&#34;&gt;https://www.hdlworks.com/hdl_corner/verilog_ref/items/SystemSimulationTimeFuncs.htm&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;2022-07-27-wed--waveforms-are-not-visible-properly-no-value-available-error-----verilogblogerrors&#34;&gt;&lt;span class=&#34;timestamp-wrapper&#34;&gt;&lt;span class=&#34;timestamp&#34;&gt;&amp;lt;2022-07-27 Wed&amp;gt; &lt;/span&gt;&lt;/span&gt; Waveforms are not visible properly, “no value available error“     :verilog:blog:errors:&lt;/h2&gt;&#xA;&lt;p&gt;Fixed after running new simulation probably due to simulation not exitting properly corrupting the database.&lt;/p&gt;&#xA;&lt;h2 id=&#34;2022-07-27-wed--to-get-current-simulation-time-in-verilog-----verilogblog&#34;&gt;&lt;span class=&#34;timestamp-wrapper&#34;&gt;&lt;span class=&#34;timestamp&#34;&gt;&amp;lt;2022-07-27 Wed&amp;gt; &lt;/span&gt;&lt;/span&gt; To get current simulation time in verilog     :verilog:blog:&lt;/h2&gt;&#xA;&lt;p&gt;System simulation time functions return the current simulation time.&lt;/p&gt;&#xA;&lt;pre&gt;&lt;code&gt;$time;&#xA;$stime;&#xA;$realtime;&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;code&gt;$time&lt;/code&gt; returns the current simulation time as a 64-bit unsigned integer.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;code&gt;$stime&lt;/code&gt; returns the lower 32-bits of the current simulationt time as an unsigned integer.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
