[ibis-macro] Re: questions about AMI_GetWave
- From: <fangyi_rao@xxxxxxxxxxx>
- To: <msteinb@xxxxxxxxxx>, <ibis-macro@xxxxxxxxxxxxx>
- Date: Tue, 1 Oct 2013 10:49:23 -0600
Thanks, Mike. Regarding the clock_times array size, I checked the 5.1 spec, and
here what the spec says.
The clock_times vector is allocated by the EDA tool and is guaranteed to be
greater than the number of clocks expected during the AMI_GetWave call.
The spec didn't state that the number of clocks expected equals wave_size. If
that's the intend, we should spell it out in the text.
For the GetWave message, if AMI_parameters_out has more than one string
parameters, how can EDA tools tell which one is the message?
Fangyi
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]
On Behalf Of Mike Steinberger
Sent: Monday, September 30, 2013 7:18 PM
To: ibis-macro@xxxxxxxxxxxxx
Subject: [ibis-macro] Re: questions about AMI_GetWave
Answers below.
Mike S.
On 09/30/2013 06:31 PM, fangyi_rao@xxxxxxxxxxx<mailto:fangyi_rao@xxxxxxxxxxx>
wrote:
Hi, AMI experts;
I was asked by an AMI model developer following questions.
In AMI_GetWave calls, what is the length that EDA tools allocate for the
clock_times array? Model developers need to have this information to avoid
writing out of bound. Should this be clarified in the standard?
In the very first discussions, the length of the clock times array was set to
be equal to the length of the input waveform array. I believe that text
survived to make it into IBIS 5.0. At any rate, that's been the definition from
the very beginning.
1. Considering there is no message string argument in AMI_GetWave's
signature, how can models pass messages back to EDA tools?
AMI_parameters_out. Define a parameter of Usage Out and Type String.
Your suggestions are appreciated.
Regards,
Fangyi
Other related posts:
