• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. ERROR ADEXL 7514

Stats

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

ERROR ADEXL 7514

sjwprcker
sjwprcker over 5 years ago

Hi,

Every time when I open the assembler, and try to view the existed result, terminal shows me the ERROR ADEXL 7514 as below, also my assembler window is stuck. What is the root cause and how to remove this ?

BR

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    I found a few reports of this in IC6.1.7 but it suggests that this was fixed in IC6.1.8 (ISR4, I think). Which IC subversion are you using? (Help->About will tell you the full sub-version).

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    I found a few reports of this in IC6.1.7 but it suggests that this was fixed in IC6.1.8 (ISR4, I think). Which IC subversion are you using? (Help->About will tell you the full sub-version).

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • sjwprcker
    sjwprcker over 5 years ago in reply to Andrew Beckett

    my cadence verison is IC617-64b.500.23, do i have to change to IC618?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to sjwprcker

    Well, the error suggests a bug - and it's related to having checks/asserts in your design. I think (from looking through the change requests) that there might be a patch that could be applied to IC617, but by far the simplest approach would be to move too IC618. After all, IC618 has been out for almost 2 years now...

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sjwprcker
    sjwprcker over 5 years ago in reply to Andrew Beckett

    Hi Andrew, thanks for your feedback. I am trying to change .cshrc to use the IC618. However, after update to IC1618, i could only insert layout instance once, after that some error is reported in the CIW  as below, and I can't insert anymore. Do you know what is the reason?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to sjwprcker

    Can you please enter the following in the CIW:

    _stacktrace=50
    sstatus(errsetTrace t)

    and then repeat the error? Ideally paste the resulting stack trace here rather than just a screenshot (it was hard for me to see that this was really gevPl and not gevPI).

    Also, which exact IC6.1.8 sub-version are you using? Typing getVersion(t) in the CIW will tell you that.

    I've found where it's used in the code, but I'd be surprised if that's the reason because it suggests that it doesn't know the cellView if that's the case. However, there's an article which uses a similar expression so it might be a consequence of something in your PDK. The stack trace will help me pinpoint that.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sjwprcker
    sjwprcker over 5 years ago in reply to Andrew Beckett

    Hi Andrew, this is new CIW info, i think the issue still exist. my version is IC6.1.8-64b.500.2

    _stacktrace=50
    50
    sstatus(errsetTrace t)
    t
    *Error* fprintf/sprintf: format spec. incompatible with data - "Format is 'gevPl%s%s%sCDFForm', argument #1 is nil"
    <<< Stack Trace >>>
    (... in CCSFormInitProc ...)
    (... in MOSFetFormInitProc ...)
    (... in unknown ...)
    (... in formInitProc ...)
    (... in uifAppendParamFields ...)
    (... in leiUpdateInstFormParamFields ...)
    (... in leHiCreateInst ...)
    leHiCreateInst()

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to sjwprcker

    OK, that appears to be based on this article:

    How to run different SKILL code in CDF Form initialization procedure when creating an instance as compared to editing an instance?

    That's called from something in your PDK, so you'll need to take this up with whoever provides that as clearly it doesn't work properly. I can't suggest how to fix it, because that article is just a template and it presumably will have been customized for your PDK. 

    I'll also contact the author of this article, because it's definitely wrong for IC6.1.8. The form names have changed in VLS L and XL to be leCreateInstLForm and leCreateInstXLForm so the line in the article (the case branch) currently showing:

        ('leCreateInstForm

    should really be:

        ((leCreateInstForm leCreateInstLForm leCreateInstXLForm)

    which would mean it would work with all three editors. I also will suggest that they improve it by adding some error checking in to avoid it breaking if it ends up in the t branch unexpectedly.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sjwprcker
    sjwprcker over 5 years ago in reply to Andrew Beckett

    Hi Andrew, I just got the Fab confirmation that their current PDK only support IC617. So I will stay with IC617 for the TO soon.

    So wrt this ADEXL error 7514, is there any way to solve it in IC617, e.g., some code or command as a temporary solution?

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to sjwprcker

    You'll have to contact customer support as I suggested earlier. I believe (from looking at CCRs 2214062 and 2305561) that there may be a patch that can be used for IC617 when facing this issue (although there seems to be some other issue that may still remain after this - so that's why I think customer support/R&D involvement is required).

    Also, there's a fair bit of guess work here because I don't know exactly what is causing the problem in your specific case - I'm merely spotting something else with similar symptoms and assuming that your issue is the same issue.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information