• 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. Digital Implementation
  3. RAM Retention Test pattern generation with Encounter Te...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13316
  • 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

RAM Retention Test pattern generation with Encounter Test

dp2402
dp2402 over 13 years ago

Hello all,

I am completely new to pattern generation using ET. My aim is to generate STIL patterns for RAM retention test of a uC device.

I believe that the most important command of ET in this regard is the 'create_embedded_test'. I am using the following.........

et -e create_embedded_test \
    topshell=<design-name>\
    usercore=<design-name>\
    interfacefiledir=<path> \
    interfacefilelist=<interface-files-listed-by-commas> \
    bsdlinput=<file-name>.bsdl.edit  \
    createpatterns=production \
    prodschedule=parallel_parallel \
    rompath=<file-path> \
    romcontentsfile=<rom-file-name> \
    seqdef=<file-name>.seq

Now if I generate the patterns using the above command (of course other commands such as build_model, build_faultmodel & write_vectors will be executed in order) and then simulate the patterns, I see that my RAM is first written and then read (as percheckerboard_retention algo.) multiple times and then simulation ends.

But I want to do something more and this is where my problem starts.

I would like to power down my device which contains this RAM, basically to a voltage lower than the recommended supply voltage, then power-up the device and then recheck whether the RAM retains all the data that was written into it previously.

 I don't know how to do this using ET acripts. Some reading into Cadence Help has indicated that I can use the command 'splitretentionpatterns=yes', that will allow user intenvention to insert custom action (in my case to power down the device, pause for some time and then power up the device) and continue with the tests. I copy the following directly from Cadence Help...... 

"If createpatterns=production is combined with splitretentionpatterns=yes the pattern allows for user intervention at the points in the retention algorithm where the test pauses"

I have no clue on how to use the ET commands to achieve the action described above. The Cadence Help is also not clear to me.

Has anyone done some similiar RAM retention test using ET? Any type of help/suggestion on how to proceed will be very helpful.

Thanks in advance,

DP

 

 

 

  • Cancel
Parents
  • dp2402
    dp2402 over 13 years ago

    ok, maybe I should put this in a different way......

    I want to perform RAM-Static-Test or RAM-Retention-Test for my device and want to generate patterns through Encounter Test (STIL/Verilog) that can be simulated.

    How shall I do it using an ET script / How is it normally done in the industry for a uC which has several power-domains? 

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dp2402
    dp2402 over 13 years ago

    ok, maybe I should put this in a different way......

    I want to perform RAM-Static-Test or RAM-Retention-Test for my device and want to generate patterns through Encounter Test (STIL/Verilog) that can be simulated.

    How shall I do it using an ET script / How is it normally done in the industry for a uC which has several power-domains? 

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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