[ibis-macro] Re: One MORE time without the typo ... RE: Re: Question about Model Specific parameters

  • From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
  • To: <ibis-macro@xxxxxxxxxxxxx>
  • Date: Mon, 21 Feb 2011 15:23:01 -0800

Todd,

 

Regarding:  “What do you expect that string will look like?”,

I would expect that string to look the same as the

string that was set into the DLL (since you said

it echoes back the received parameters):

 

(My_RX_DLL(dfe(taps(1 0)(2 0)(3 0)(4 0)(5 0)))

 

But I don’t see how going through this exercise

answers the question we are discussing…

 

Arpad

====================================================

 

 

 

From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] 
On Behalf Of Todd Westerhoff
Sent: Monday, February 21, 2011 4:30 PM
To: ibis-macro@xxxxxxxxxxxxx
Subject: [ibis-macro] Re: One MORE time without the typo ... RE: Re: Question 
about Model Specific parameters

 

Arpad,

 

Sorry for the delay in reply – today’s errands ran longer than I anticipated.  
I suggest we go through the tap example front to back and then see how that 
compares to other cases.

 

The .ami file for a hypothetical RX declares the following:

 

(My_RX_DLL

   (Reserved Parameters

      …

   )

   (Model _Specific

      (dfe

         (taps 

             (1 (Usage InOut)(Range 0 -1.0 1.0)(Type Tap)

                 (Default 0)(Description "First DFE tap."))

             (2 (Usage InOut)(Range 0 -1.0 1.0)(Type Tap)

                 (Default 0)(Description "Second DFE tap."))

             (3 (Usage InOut)(Range 0 -1.0 1.0)(Type Tap)

                 (Default 0)(Description "Third DFE tap."))

             (4 (Usage InOut)(Range 0 -1.0 1.0)(Type Tap)

                 (Default 0)(Description "Fourth DFE tap."))

         )

   )

)

 

Let’s say the .dll is called with the default settings for the tap parameters, 
which gives an AMI_parameters_in string of:

 

(My_RX_DLL(dfe(taps(1 0)(2 0)(3 0)(4 0)(5 0)))

 

Let’s also say the .dll echoes back the control parameters it finds during the 
AMI_Init call, using the AMI_parameters_out interface.  What do you expect that 
string will look like?

 

Todd.

 

________________________


Todd Westerhoff
VP, Software Products
SiSoft
6 Clock Tower Place, Suite 250
Maynard, MA 01754
(978) 461-0449 x24
twesterh@xxxxxxxxxx
www.sisoft.com

 

From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] 
On Behalf Of Muranyi, Arpad
Sent: Monday, February 21, 2011 10:38 AM
To: ibis-macro@xxxxxxxxxxxxx
Subject: [ibis-macro] Re: One MORE time without the typo ... RE: Re: Question 
about Model Specific parameters

 

Todd,

 

This was exactly my point.  On what bases would an EDA tool

be expected to plot Type Tap and none of the other Types?

Or, are we saying that the tool is expected to plot any Usage

InOut/Out regardless of its Type?  And could any other

expectations from the tool arise for the other Types,

depending on what their meaning is?  This is where the

spec is clear as mud.

 

If we say that the tool should plot the Type Tap, because

we know the meaning of it (Tap), people could also come up

with other rationale for the other types.  But these

expectations may all be very subjective, personally biased.

We can’t have such expectations and such loose ends in a

specification.

 

On the other hand, if we do not have such expectations, then

why would we allow to have InOut/Out for Model Specific

parameters?  It just doesn’t make sense…

 

In my opinion the specification should mention what the tool

should or could do with these InOut/Out parameters, or

prohibit them.

 

Thanks,

 

Arpad

=============================================================

 

<SNIP>

Other related posts:

  1. Home
  2. ibis-macro
  3. Archive
  4. 02-2011