Stats

  • Locked Locked
  • Replies 9
  • Subscribers 125
  • Views 5013
  • 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

Check Mosfet operation region with Checks/Asserts

LukiLeu

In ADE L I could check the mosfet operation region with the "Device Checking" Tool. I recently switched to ADE Explorer and wanted to do there the same. However I cannot get to set up the wanted check in the "Checks/Assert" Form. I added ther the following data:

- Subs: My devices (eg. nmos4 pmos4)
- Param: region
- Values: tried 3, sat
- Analyses: dcOP

However it keeps saying that there are no violations but with the Device Checking Tool there are violations reported. How do I need to set up the Checks/Assert Form to achieve the same?

Kind regards

Lukas

Parents
  • Saloni Chhabra

    Hi Lukas,

    I think that the document below should help you setup your device checks. Please refer to chapter 3 in particular which explains the different ways of setting up and running operating region checks on devices in Explorer.

    https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O0V0000090teVUAQ&pageName=ArticleContent&sq=005d0000001T4VEAA0_201852911117885

    Hope this helps.

    Regards,

    Saloni

  • LukiLeu
    in reply to Saloni Chhabra

    However, now I got a strange behaviour. It worked fine first, but then I changed something in the schematic. Now the checks always fail with the message:

    *Error* ("eval" 0 t nil ("*Error* eval: unbound variable" region))

    I tried also to delete all checks and add them again, but the same error keeps appearing. Do you have any idea?

  • LukiLeu
    in reply to LukiLeu

    If I revert the maestro view to where I haven't added the operating point check and then add it again it works again till I change something in the schematic. I then need to revert the view again and add the check again. Any ideas in how to resolve this without the need to revert the view to the point before I added the check?

  • Andrew Beckett
    in reply to LukiLeu

    Which IC subversion are you using? What does getVersion(t) return in the CIW (also shown in Help->About).

    There was a bug in IC615 where this was broken (fixed in 6.1.5.500.10, I think) - sounds a bit like that, although this is quite an old version...

    Andrew.

  • LukiLeu
    in reply to Andrew Beckett

    Hi Andrew, 

    I am using IC6.1.7.500.4. 

    I also found out, that if I delete the check before I change the schematic and add the check again after the change of the schematic, it will run.

  • Andrew Beckett
    in reply to LukiLeu

    OK, we'll need to do some checking to see if it was broken more recently (or if it's still broken). Thanks for the version info - that helps enormously.

    Regards,

    Andrew.

  • LukiLeu
    in reply to Andrew Beckett

    It seems to work correctly, when I don't add to much devices with too much conditions.

    Eg. When it didn't worked I had about 20'000 checks active. Now I have only 2400 checks active and I can change something in the schematic and it keeps working, without that I need to remove the check first, change something in the schematic and add the checks again.

Reply
  • LukiLeu
    in reply to Andrew Beckett

    It seems to work correctly, when I don't add to much devices with too much conditions.

    Eg. When it didn't worked I had about 20'000 checks active. Now I have only 2400 checks active and I can change something in the schematic and it keeps working, without that I need to remove the check first, change something in the schematic and add the checks again.

Children
  • Andrew Beckett
    in reply to LukiLeu

    This seems unlikely that it's based on on the number of checks - but maybe there's a bug with your particular set of data. 

    Please contact customer support so that we can look at it.

    Regards,

    Andrew

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.