This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DS16EV5110A: Hspice model syntax error

Part Number: DS16EV5110A

Tool/software:

Hi experts,

I just tried to run the hspice model provided in the link below:

DS16EV5110A: Customer needs IBIS (or some simulation) model - Interface forum - Interface - TI E2E support forums

but the results showed that parameters, within the encrypted block, contain illegal characters in line 1 column 19: "0.16u+0.32u+0.48u*"
May I have an updated spice model (or any other AC-supported model) to run frequency domain simulation?

Thanks for helping!

Edu 

  • Hi Edu,

    Unfortunately, we do not have an updated spice model for this device.

    I saw in the readme for this model that it requires a "hspice3des" license token.  Do you have this token enabled?

    If you run into the same issue after enabling this, I'm wondering if you could try with an older version of h-spice, or perhaps reach out to Synopsys for assistance.

    DS16EV5110A README:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    Readme to use Triple DES Encrypted HSPICE model file
    It is highly recommended to use HSPICE version 2006.03-SP1 or later for running simulations. In addition, HSPICE requires an "hspice3des" license token. It can be obtained from Synopsys at NO cost to user.
    The HSPICE Model of DS16EV5110 is encrypted using "metaencrypt" utility from 2006.03-SP1 version of HSPICE. The encryption option of "192 BIT Random Key Triple DES Encryption" was used. With this encryption option, users do not need any additional keys. The encrypted file can be used in simulations just like any other macro model file.
    Due to export compliance regulations in the US, Synopsys does not enable the "3DES" option in HSPICE by default. Furthermore, an "hspice3des" license may be required. There is usually no cost to upgrade to the recent version or to obtain the "hspice3des" license. The license can be obtained by contacting Synopsys directly.
    Note: Customers need to meet export compliance guidelines to use HSPICE3DES. Please check with your Synopsys sales representative.
    If the customer is using HSPICE 2005.03 or 2005.09 versions, then they need to have HSPICE with 3DES binaries. These binary files are different from the regular HSPICE binary files due to export compliance regulations. Again, an "hspice3des" license may be required. There is no cost to the user to obtain the required binary or the license.
    Note: Files encrypted with this Triple DES algorithm cannot be read by previous releases of HSPICE.
    How to obtain hspice3des license token from Synopsys
    The token can be obtained from the regional Synopsys account managers. The triple DES license needs to be added to the PO, however, it is a zero cost item. The part number is 4279. This process is supposed to take up to 3 days, typically faster. A temporary key can be requested at the same time when the formal key is requested. The temporary key can be generated quickly and is approved by Synopsys sales department. Please contact Synopsys sales support specialist for the temporary key.
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Thanks,
    Drew

  • Hi Drew,

    Thank you very much for the prompt reply. I checked about hspice3des and made sure its enabled. The error message showed the content can be decrypted but there was a syntax error so I’m wondering if it’s possible to double check the validity of line 1 column 19 of the spice file before encryption. I’m also reaching out to Synopsys to verify the license issue.

    Kind regards,

    Edu

  • Hi Edu,

    Thanks for checking on hspice3des.  Due to the age of this device, locating the original spice file may be challenging.  I'll check in with some team mates to see if we have anything.

    Thanks,

    Drew