• 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. ADE-L generates .grf files with non-existing expression...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 14158
  • 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

ADE-L generates .grf files with non-existing expression definitions

dontpanic
dontpanic over 8 years ago

Hi! I'm having an annoying issue with some states in ADE-L. For some reason, some old expression definitions are being held somehow somewhere (even if they don't exist at all in the outputs list), and when I save any waveform files (.grf) these definitions are included on them, causing lots of warning to appear each time I load these .grf files.

For instance I get the following warnings on the CIW when loading a .grf file:

*WARNING* Symbol(s) named " 'S01__vRESdiff' " used in the definition of dependent expression
                     Name: 'S01__vRESdiff__sampled__at_100pc_Tamp'
               Expression: 'sample(S01__vRESdiff VAR("MEAS__TRAN__Tstart__at_100pc_Tamp") VAR("MEAS__TRAN__Tstop__at_100pc_Tamp") "linear" VAR("MEAS__TRAN__Tsample"))'
 have not been defined as expressions. This may result in evaluation errors or ambiguous values for the dependent expression.
 Either add these symbol(s) as expression(s) in the Outputs or remove them from the definition of the dependent expression.

*WARNING* Symbol(s) named " 'TRAN___Iavg__PIPELINE__vddA', 'TRAN___Iavg__PIPELINE__vddCMP', 'TRAN___Iavg__PIPELINE__vddD', 'TRAN___Iavg__PIPELINE__vddSW' " used in the definition of dependent expression
                     Name: 'TRAN___Iavg__PIPELINE__total'
               Expression: '(TRAN___Iavg__PIPELINE__vddA + TRAN___Iavg__PIPELINE__vddCMP + TRAN___Iavg__PIPELINE__vddD + TRAN___Iavg__PIPELINE__vddSW)'
 have not been defined as expressions. This may result in evaluation errors or ambiguous values for the dependent expression.
 Either add these symbol(s) as expression(s) in the Outputs or remove them from the definition of the dependent expression.

and so on. On the header of the .grf file I do find the following definitions, which I don't understand where they come from!:

<?xml version="1.0" encoding="UTF-8" ?>
<!--StateFileType saveLoadState-->
[...]

    </IndexedProp>
    <IndexedProp Name="dependentExprsList">
        <SimpleProp Name="E0" Value='dB20(mag(dft(vtime(&apos;tran &quot;/SDSC1/Qout&quot;) 20*VAR(&quot;Ts&quot;) VAR(&quot;Ts&quot;)*(20+VAR(&quot;fft_order&quot;)) VAR(&quot;fft_order&quot;) &quot;Rectangular&quot; 1 &quot;default&quot; )))' Type="stringValue" />
        <SimpleProp Name="E1" Value='dB20(mag(dft(vtime(&apos;tran &quot;/SDSC1/Qout&quot;) 20*VAR(&quot;Ts&quot;) VAR(&quot;Ts&quot;)*(20+VAR(&quot;fft_order&quot;)) VAR(&quot;fft_order&quot;) &quot;Rectangular&quot; 1 &quot;default&quot; )))' Type="stringValue" />
        <SimpleProp Name="E2" Value='getData(&quot;/DUT/PIPELINE/BACKEND_PIPELINE/STAGE05/subADC/H__subADC/PHIquantizeN_local&quot; ?result &apos;tran)' Type="stringValue" />
        <SimpleProp Name="E3" Value='getData(&quot;/DUT/PIPELINE/BACKEND_PIPELINE/STAGE05/subADC/H__subADC/PHIsampleE_local&quot; ?result &apos;tran)' Type="stringValue" />
        <SimpleProp Name="TRAN__CMFBamp__S1__MN__region" Value='getData(&quot;DUT.RESGEN.CMFBamp.S1__MN:region&quot; ?result &quot;tran&quot;)' Type="stringValue" />
        <SimpleProp Name="TRAN__CMFBamp__S2__MN__region" Value='getData(&quot;DUT.RESGEN.CMFBamp.S2__MN__L:region&quot; ?result &quot;tran&quot;)' Type="stringValue" />
        <SimpleProp Name="S1__sADC__H__vCshared_p" Value='(VT(&quot;/S01__subADC__H__vSHAREDp&quot;) - VT(&quot;/S01__subADC__H__vINp_COMP&quot;))' Type="stringValue" />
        <SimpleProp Name="S01__vRESdiff__sampled__at_100pc_Tamp" Value='sample(S01__vRESdiff VAR(&quot;MEAS__TRAN__Tstart__at_100pc_Tamp&quot;) VAR(&quot;MEAS__TRAN__Tstop__at_100pc_Tamp&quot;) &quot;linear&quot; VAR(&quot;MEAS__TRAN__Tsample&quot;))' Type="stringValue" />
        <SimpleProp Name="E4" Value='getData(&quot;/PIPELINE/S01__vREFcm_sample&quot; ?result &apos;tran)' Type="stringValue" />
        <SimpleProp Name="TRAN___Iavg__PIPELINE__total" Value="(TRAN___Iavg__PIPELINE__vddA + TRAN___Iavg__PIPELINE__vddCMP + TRAN___Iavg__PIPELINE__vddD + TRAN___Iavg__PIPELINE__vddSW)" Type="stringValue" />
        <SimpleProp Name="TRAN__Iavg__S01__CMFBAMP__S1" Value='average(IT(&quot;/S01/CORE/MDAC/RINGAMPcmfb/AMP/S1__MP/S&quot;))' Type="stringValue" />
    </IndexedProp>
    [...]

None of the above expressions exist anymore in my ADE state. If I delete manually everything between <IndexedProp> ... </IndexedProp> and reload the .grf, I still get warnings for expressions which don't exist neither in the ADE-L outputs list nor in the .grf file:

*WARNING* Symbol(s) named " 'S01__vRESdiff' " used in the definition of dependent expression
                     Name: 'S01__vRESdiff__sampled__at_100pc_Tamp'
               Expression: 'sample(S01__vRESdiff VAR("MEAS__TRAN__Tstart__at_100pc_Tamp") VAR("MEAS__TRAN__Tstop__at_100pc_Tamp") "linear" VAR("MEAS__TRAN__Tsample"))'
 have not been defined as expressions. This may result in evaluation errors or ambiguous values for the dependent expression.
 Either add these symbol(s) as expression(s) in the Outputs or remove them from the definition of the dependent expression.

*WARNING* Symbol(s) named " 'TRAN___Iavg__PIPELINE__vddA', 'TRAN___Iavg__PIPELINE__vddCMP', 'TRAN___Iavg__PIPELINE__vddD', 'TRAN___Iavg__PIPELINE__vddSW' " used in the definition of dependent expression
                     Name: 'TRAN___Iavg__PIPELINE__total'
               Expression: '(TRAN___Iavg__PIPELINE__vddA + TRAN___Iavg__PIPELINE__vddCMP + TRAN___Iavg__PIPELINE__vddD + TRAN___Iavg__PIPELINE__vddSW)'
 have not been defined as expressions. This may result in evaluation errors or ambiguous values for the dependent expression.
 Either add these symbol(s) as expression(s) in the Outputs or remove them from the definition of the dependent expression.

So my question is: where are these definitions coming from and how can I get rid of them once and for all?

Thanks in advance for any help!

Cheers,

Jorge.

P.S. I've tried searching (on the command line) for files containing the problematic expression names under the cell's hierarchy and couldn't find anything. I suspect these definitions are being held in some sort of cache somewhere!

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Hi Jorge,

    I suggest you contact customer support for this one. Whilst there have been a number of similar issues (not identical though) in the past, I think we'd need to take a detailed look at your data to try to figure out what is going on.

    Thanks,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dontpanic
    dontpanic over 8 years ago
    Thanks for your reply, Andrew; I'll fill in a support request for this a.s.a.p.
    Cheers,
    Jorge.
    • 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