Electronics

Electronics

Topics relate to HFSS, Maxwell, SIwave, Icepak, Electronics Enterprise and more

IBIS AMI models

TAGGED: 

    • Eglantine PERRON
      Subscriber

      I'm simulating a circuit in AEDT with IBIS AMI models of a component. However, these models use a version 6.0 or 6.1 which seems not to be supported by ANSYS. I get the following error message on the console "Unexpected engine termination" and "ERROR - AMI_Version 6.0 is not valid" on the Linux console. Have you ever had this problem and it is possible to solve it ?

    • Dan Dv
      Ansys Employee

      AEDT Circuit does support IBIS 6.x AMI models. So I'm not sure the exact reason for that error. Can you go to the full log file (right mouse click on the AMI definition in the project manager and select "browse log file") and paste the full error message in question from that log here? 

    • Eglantine PERRON
      Subscriber

      Thanks for your response. I don't have error message in the full log file but only this :

      (info): Procesing circuit for new analysis

      omp(status): Requested number of threads in UI setting is 16

    • Dan Dv
      Ansys Employee

      That seems odd. Any simulation warning or error that appears in the message manager should also be in that log file. You may need to try re-simulating. Worst case, if you can copy the full message out of the message manager that may give me a little bit more to go on. 

    • Eglantine PERRON
      Subscriber

      I re-simulated several times there is still nothing. On the Linux terminal I have the following messages :

      WARNING - Filename 'PolarFire_IBIS_AMT_SR_Model.ibs' should be lowercase
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'P'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'F'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'I'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'B'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'I'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'S'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'A'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'M'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'T'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'S'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'R'.
      ERROR (line    5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'M'.

      ... Reading PolarFire_IBIS_AMT_SR_Model_100.ami
      WARNING - Filename 'PolarFire_IBIS_AMT_SR_Model_100.ami' should be lowercase

      ... Checking PolarFire_IBIS_AMT_SR_Model_100.ami for Implicit AMI Version 5.0 Compatibility...

      ERROR - AMI_Version "6.1" is not valid
      ... Done Checking PolarFire_IBIS_AMT_SR_Model_100.ami
      ... Done Reading PolarFire_IBIS_AMT_SR_Model_100.ami


      ... Reading PolarFire_IBIS_AMT_SR_Model_150.ami
      WARNING - Filename 'PolarFire_IBIS_AMT_SR_Model_150.ami' should be lowercase

      ... Checking PolarFire_IBIS_AMT_SR_Model_150.ami for Implicit AMI Version 5.0 Compatibility...

      ERROR - AMI_Version "6.1" is not valid
      ... Done Checking PolarFire_IBIS_AMT_SR_Model_150.ami
      ... Done Reading PolarFire_IBIS_AMT_SR_Model_150.ami


      ... Reading PolarFire_IBIS_AMT_SR_Model_float.ami
      WARNING - Filename 'PolarFire_IBIS_AMT_SR_Model_float.ami' should be lowercase

      ... Checking PolarFire_IBIS_AMT_SR_Model_float.ami for Implicit AMI Version 5.0 Compatibility...

      ERROR - AMI_Version "6.1" is not valid
      ... Done Checking PolarFire_IBIS_AMT_SR_Model_float.ami
      ... Done Reading PolarFire_IBIS_AMT_SR_Model_float.ami

      It wouldbe better to send you the project with the IBIS models that I took directly from the microchip's website.

       

    • Dan Dv
      Ansys Employee

      Those appear to be comittee parser messages. That implies as hard failure with respect to the IBIS file rules. I'll look into that further. I probably should have asked earlier. What version of AEDT are you running? 


    • Eglantine PERRON
      Subscriber

      I use AEDT 2021/R2.2

    • Dan Dv
      Ansys Employee

      OK. Those really look like IBIS comittee parser errors. You can download the stand alone version of that here:
      IBISCHK

      If you run the stand alone checker on these files and get these errors then it is something that the model writer needs to addres.

       

       

    • Eglantine PERRON
      Subscriber

      I tried. Indeed I have errors on one of the models. The first errors are due to the presence of capital letters in the .ibs filename. The second errors are the presence of two identical numbers.

      For the second IBIS AMI model I have no errors with IBISCHK but during the simulation I have two error codes that appear in AEDT which are the following :

      • Expression cannot be evaluated "CTE"
      • Expression cannot be evaluated "agc"
    • Dan Dv
      Ansys Employee

      Can you also try running the parser on the .ami files? The syntax should be:

      ibischk7_64  -ami 

      I'm not sure what might be going on with those other errors in AEDT about he "CTE" and "agc" parameters. What model set do those come from?

    • Eglantine PERRON
      Subscriber

      There are no errors with the .ami files. The models come from Microsemi directly : https://www.microsemi.com/products/fpga-soc/design-resources/ibis-models/ibis-models-polarfire

    • Dan Dv
      Ansys Employee

      I did download those models and they seem to run for me without errors in 2022R1 and 2023R1. I was running on Windows, and I think you mentioned that you were using Linux. I've asked a colleague to check this on Linux for me. I'll let you know if that shows anything different. 
      Just to check, are you able to try this on our latest 2023R1 release? 

    • Dan Dv
      Ansys Employee

      I did confer with development. The version of the committee parser used in release 2022R1 was not updated to support 6.1. Would you be able to try in a newer version of the tool and let me know if that works better? 

Viewing 12 reply threads
  • You must be logged in to reply to this topic.