RE: [sv-ac] comments on Surrendra's corrections


Subject: RE: [sv-ac] comments on Surrendra's corrections
From: Bassam Tabbara (bassam@novas.com)
Date: Fri Nov 07 2003 - 14:54:37 PST


Surrendra, I don't think it is clear enough. "mclk" is shown, so it is
natural for the reader do "sample" again based on the waveform (the
waveform is similar to the earlier ones that explain the sampling.... If
mclk is taken out then yeah it is clearer...).

I still say: It does not seem that much of a change to just push the
edge a teeny bit back so everyone is happy ... Is it ?

Thx.
-Bassam.

--
Dr. Bassam Tabbara
Technical Manager, R&D
Novas Software, Inc.

http://www.novas.com (408) 467-7893

> -----Original Message----- > From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On > Behalf Of John Havlicek > Sent: Friday, November 07, 2003 1:51 PM > To: Surrendra.Dudani@synopsys.com > Cc: sv-ac@eda.org > Subject: Re: [sv-ac] comments on Surrendra's corrections > > > Surrendra: > > Maybe this is o.k. I understand the need to keep the diagram > simple, but when I looked at it I thought everything was > shifted off by a cycle. > > However, there is a practical consideration, which is, what > will people actually see in waveform viewers? I am concerned > that the convention you suggest is at odds with this. > > J.H. > > > > > X-Sender: dudani@us04.synopsys.com > > Date: Fri, 07 Nov 2003 15:44:19 -0500 > > From: Surrendra Dudani<Surrendra.Dudani@synopsys.com> > > Sender: owner-sv-ac@eda.org > > Precedence: bulk > > > > <html> > > Hi Bassam,John<br> > > Regarding Fig. 17-12, the values shown are sampled values of the > > signals. The LRM explains what sampled values are in Fig. 17-1. In > > Fig. 17-3, simulation values are explicitly shown for value change > > expressions. Once explained, the LRM doesn't show the raw > simulation > > values of signals. All values are sampled with respect to the clock > > and shown.This is also mentioned&nbsp; again<br><br> <font > face="Times > > New Roman, Times">Each time a data phase is true, a match for > > </font><font face="Courier, Courier" size=2>data_phase </font><font > > face="Times New Roman, Times">is recognized. The attempt at > clock tick > > 6 is illustrated<br> in Figure 17-13. The values shown for > the signals > > are the sampled values with respect to the clock. At clock<br> > > tick 6, </font><font face="Courier, Courier" size=2>data_end > > </font><font face="Times New Roman, Times">is true because > > </font><font face="Courier, Courier" size=2>stop > > </font><font face="Times New Roman, Times">gets asserted while > > </font><font face="Courier, Courier" size=2>irdy > > </font><font face="Times New Roman, Times">is asserted.<br><br> > > </font>I think when a figure appears like a waveform, > perhaps, people > > associate it with simulation values, not sampled values. <br> > > There used to be a big note about this, but somehow it > disappeared (don't > > know why).<br> > > Should we add back a note explaining that after Figure > 17-1, all values > > are sampled values?<br><br> > > Surrendra<br> > > At 12:08 PM 11/4/2003 -0800, you wrote:<br> > > <blockquote type=cite class=cite cite>Hi John,<br><br> > > Thanks for catching this! Yes you are right I think the burst_mode > > edge<br> > > *needs some pushing to the left, that would be the minimal change > > to<br> > > this figure*,(the default here is the #1step sampling so this needs > > a<br> > > push). I think we caught this in Figure 17-1 a while back > with the<br> > > &quot;req&quot;, let's update all of 'em, we missed these.<br><br> > > ** I agree with all of John's corrections (1.17, &lt;statements&gt;; > > already<br> > > has a semicolon).<br><br> > > Good catch John, this would've been one huge headache!<br><br> > > -Bassam.<br><br> > > --<br> > > Dr. Bassam Tabbara<br> > > Technical Manager, R&amp;D<br> > > Novas Software, Inc.<br><br> > > <a href="http://www.novas.com/" > eudora="autourl">http://www.novas.com><br> > > (408) 467-7893<br><br> > > &gt; -----Original Message-----<br> > > &gt; From: owner-sv-ac@eda.org > > [<a href="mailto:owner-sv-ac@eda.org" > eudora="autourl">mailto:owner-sv-ac@eda.org</a>] > > On <br> > > &gt; Behalf Of John Havlicek<br> > > &gt; Sent: Sunday, November 02, 2003 9:35 AM<br> > > &gt; To: sv-ac@eda.org<br> > > &gt; Subject: [sv-ac] comments on Surrendra's corrections<br> > > &gt; <br> > > &gt; <br> > > &gt; All:<br> > > &gt; <br> > > &gt; Below are my comments on Surrendra's suggested changes in <br> > > &gt; SV_AC_LRM_corrections_10.12.pdf.<br> > > &gt; <br> > > &gt; Best regards,<br> > > &gt; <br> > > &gt; John H.<br> > > &gt; <br> > > &gt; > ==============================================================<br> > > &gt; ==========<br> > > &gt; <br> > > &gt; 1.1&nbsp; I agree.<br> > > &gt; <br> > > &gt; 1.2&nbsp; I agree.<br> > > &gt; <br> > > &gt; 1.3&nbsp; I agree.<br> > > &gt; <br> > > &gt; 1.4&nbsp; I agree.<br> > > &gt; <br> > > &gt; 1.5&nbsp; I agree.<br> > > &gt; <br> > > &gt; 1.6&nbsp; I agree.<br> > > &gt; <br> > > &gt; 1.7&nbsp; I agree.<br> > > &gt; <br> > > &gt; 1.8&nbsp; I agree.<br> > > &gt; <br> > > &gt; 1.9&nbsp; I agree.<br> > > &gt; <br> > > &gt; 1.10 I agree, but I'm not happy about the way the picture <br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fig 17-12 seems to confuse the > > sampling of values.&nbsp; <br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sampling at mclk, it > looks to me as > > though $fell burst_mode<br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be true at time > 3, not time > > 2.&nbsp; Etc., etc., etc.<br> > > &gt; <br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I think the same goes for fig > > 17-11.&nbsp; <br> > > &gt; <br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What do other people think?<br> > > &gt; <br> > > &gt; 1.11 I agree.&nbsp; With this change, the definition > of property r2 > > is<br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the same as that of > property r3.&nbsp; > > However, I think that <br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; > property r3;<br> > > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; > > @(posedge mclk)(q != d);<br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; endproperty<br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; always > @(posedge > > mclk) begin<br> > > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs > p;&nbsp; if > > (a) begin<br> > > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs > p;&nbsp;&nbsp;&nbsp;&nbsp; > > q &lt;= d1;<br> > > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs > p;&nbsp;&nbsp;&nbsp;&nbsp; > > r3_p: assert property (r2);<br> > > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; > > end<br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; end<br> > > &gt; <br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be<br> > > &gt; <br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; > property r3;<br> > > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; > > @(posedge mclk)(q != d);<br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; endproperty<br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; always > @(posedge > > mclk) begin<br> > > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs > p;&nbsp; if > > (a) begin<br> > > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs > p;&nbsp;&nbsp;&nbsp;&nbsp; > > q &lt;= d1;<br> > > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs > p;&nbsp;&nbsp;&nbsp;&nbsp; > > r3_p: assert property (r3);<br> > > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; > > end<br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; end<br> > > &gt; <br> > > &gt; 1.12 I agree.<br> > > &gt; <br> > > &gt; 1.13 I agree.<br> > > &gt; <br> > > &gt; 1.14 I agree.<br> > > &gt; <br> > > &gt; 1.15 I agree, but change &quot;atleat&quot; to &quot;at > > least&quot;.&nbsp; I have already said<br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that I think these figures are > > misleading representations of the <br> > > &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signal sampling.<br> > > &gt; <br> > > &gt; 1.16 I agree, same caveat about the sampling in the > diagrams.<br> > > &gt; <br> > > &gt; 1.17 I agree.&nbsp; Probably there should not be a > semicolon after > > <br> > > &gt; &lt;statements&gt;.<br> > > &gt; <br> > > &gt; 1.18 I agree.<br> > > &gt; <br> > > &gt; 1.19 I agree.<br> > > &gt; <br> > > &gt; 1.20 I agree.<br> > > &gt; </blockquote> > > <x-sigsep><p></x-sigsep> > > <br><br> > > **********************************************<br> > > Surrendra A. Dudani<br> > > Synopsys, Inc.<br> > > 377 Simarano Drive, Suite 300<br> > > Marlboro, MA 01752<br><br> > > Tel:&nbsp;&nbsp; 508-263-8072<br> > > Fax:&nbsp;&nbsp; 508-263-8123<br> > > email: Surrendra.Dudani@synopsys.com&nbsp; <br> > > **********************************************</html> >



This archive was generated by hypermail 2b28 : Fri Nov 07 2003 - 14:55:18 PST