Stats

  • Locked Locked
  • Replies 4
  • Subscribers 126
  • Views 2897
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

netlist generated by ADEXL doesn't match with ADEL

nicola91it

Hi,

I am currently using Cadence IC6.1.6.500.4. performing corner simulation. All the corners have been good until I encountered a corner I didn't like, so I checked possible solutions with ADEL. The problem is that the result doesn't match with the one obtained with ADEXL.

Obviously. I double checked all the settings, all the variables, the library path, the references to the schematic and they are exactly the same. So, I created the netlist using both ADEL and ADEXL and I compared them with a text comparator. Here attached there is the picture that shows the only difference encountered (left is ADEL netlist and right is the ADEXL). As can be seen, in ADEXL netlist the part I52.I74:2 is missing (in my case I52 and I74 are both instances, but I don't know what :2 means).

Following this way, I tried to look at a transient signal in the part that is missing in the same corner, and ADEXL correctly plot it without any problems.

I also tried to verify other corners, but in many other cases (I can't compare all the corners) the results from ADEXL perfectly match with the results of ADEL. even if the netlist difference is still present.

I really don't know what's happening: furthermore, I don't know why when I open the ADEXL test I can't run a simulation with that interface (the picture is attached).

I would be graceful to receive some help. Thank you and regards

Parents
  • Marc Heise
    Hi Nicola,

    the difference in your netlist is the save statement for the current in the terminal "2" of the device "I74". The current is not saved to the disk and can't be viewed after the simulation. The simulation itself should not be influenced by that.
    It's not clear for me what exactly is not matching between the ADEXL and the ADE simulation. Do you get different results for some measurements?
    The last picture you attached is showing t our so called "Test Editor". It is basically the ADE interface without the run buttons. It's purpose is to make it easy to setup
    tests for ADEXL using the old trusted environment. After you make your changes there, you close it and run the test in ADEXL.
    The easiest way to debug a troublesome corner is to use the "Troubleshoot Corner"mode. First you run your Corners in ADEXL, when looking at the results display you can right click in the results and select "Troubleshoot Corner" from the popup. This will transfer the corner setup to an ADE interface, where you can dig deeper into that corner. Please see the documentation for that one.

    Hope that cleared up some things.

    Regards,
    Marc
Reply
  • Marc Heise
    Hi Nicola,

    the difference in your netlist is the save statement for the current in the terminal "2" of the device "I74". The current is not saved to the disk and can't be viewed after the simulation. The simulation itself should not be influenced by that.
    It's not clear for me what exactly is not matching between the ADEXL and the ADE simulation. Do you get different results for some measurements?
    The last picture you attached is showing t our so called "Test Editor". It is basically the ADE interface without the run buttons. It's purpose is to make it easy to setup
    tests for ADEXL using the old trusted environment. After you make your changes there, you close it and run the test in ADEXL.
    The easiest way to debug a troublesome corner is to use the "Troubleshoot Corner"mode. First you run your Corners in ADEXL, when looking at the results display you can right click in the results and select "Troubleshoot Corner" from the popup. This will transfer the corner setup to an ADE interface, where you can dig deeper into that corner. Please see the documentation for that one.

    Hope that cleared up some things.

    Regards,
    Marc
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.