Re: [IBIS-Users] ibischk5 Issue for ISSO_PU/ISSO_PD keywords

Hi Sergey:

The best approach is to draft a BUG report and use a format shown in
other Bug reports:

   http://www.eda.org/ibis/bugs/ibis_bugs/

or given as

   http://www.eda.org/ibis/bugs/ibis_bugs/bugform.txt

Leave the Administrative Tracking details blank.

If you can reduce the test case file to a simple file, that would
help. Then we can look at the exact details and decide how to
resolve the issue.

Please send this back to me.

Best Regards,
Bob

Nikonchuk Sergey-R6294C wrote:
> Dear Community,
> During evaluation of new IBIS5.0 keywords we faced strange behavior of
> ibischk5 version 5.0.3 for the ISSO_PU/ISSO_PD keywords.
>
> There is two type of issues:
> 1. Looks like "Typ" conditions does NOT checked at all.
> At the first time we had a bit wrong implementation of ISSO_PU curves
> capturing.
> We had Warning messages for Min and Max keywords, but NOT Typ which one
> was wrong really as well.
> Could you double check a code, please?
>
> 2. Additional question about "threshold" or "accuracy" level when
> IBISCHK compare currents..
> Example is below:
>
> WARNING - Model model_example: Minimum ISSO_PU current (-0.015A) at 0V
> does not match Pullup current (-0.015A) at reference ( 0.000V)
> WARNING - Model model_example: Minimum ISSO_PD current ( 0.017A) at 0V
> does not match Pulldown current ( 0.017A) at reference ( 1.620V)
> WARNING - Model model_example: Maximum ISSO_PU current (-0.017A) at 0V
> does not match Pullup current (-0.017A) at reference ( 0.000V)
> WARNING - Model model_example: Maximum ISSO_PD current ( 0.025A) at 0V
> does not match Pulldown current ( 0.025A) at reference ( 1.980V)
>
> As You can see - from report point of view values looks exactly same.
> It's looks like "interpolation" issue - we have no exact voltage
> reference points in our I-V data.
> The neighbor points are quite close to the expected values..
>
> So, Is it possible to either print actual current values with all
> significant numbers,
> Or - use some "threshold" (like as 1e-9A or so) to filter out
> micro-differences ...
>
>
> Do you have any comments about? Is it looks like real problem?
> If so - what is formal procedure to open a Bug report for the IBISCHK ?
>
> Regards,
>
> Sergey Nikonchuk
> Characterization and View Generation
> TSO / DT / DC / IO Libraries
> Freescale Semiconductor, Inc.
> www.freescale.com <http://www.freescale.com/>
>
> Contacts:
> Phone +7 (495) 589 1839
> Mobile +7 (916) 993 3467
> Fax +7 (495) 787 0151
> Sergey.Nikonchuk@freescale.com <mailto:Sergey.Nikonchuk@freescale.com>
>
> This e-mail and any attachments have been classified as:
> [x] Public
> [ ] Internal Use Only
> [ ] Confidential Proprietary
>
>
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner <http://www.mailscanner.info/>, and is
> believed to be clean.

-- 
Bob Ross
Teraspeed Consulting Group LLC     Teraspeed Labs
121 North River Drive              13610 SW Harness Lane
Narragansett, RI 02882             Beaverton, OR 97008
401-284-1827                       503-430-1065
http://www.teraspeed.com           503-246-8048 Direct
bob@teraspeed.com
Teraspeed is a registered service mark of Teraspeed Consulting Group LLC
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993