Home > Community > Forums > Digital Implementation > RAM Retention Test pattern generation with Encounter Test

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 RAM Retention Test pattern generation with Encounter Test 

Last post Mon, May 7 2012 3:07 AM by dp2402. 1 replies.
Started by dp2402 04 May 2012 07:04 AM. Topic has 1 replies.
Page 1 of 1 (2 items)
Sort Posts:
  • Fri, May 4 2012 7:04 AM

    • dp2402
    • Not Ranked
    • Joined on Wed, Mar 14 2012
    • Posts 6
    • Points 75
    RAM Retention Test pattern generation with Encounter Test Reply

    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

     

     

     

    • Post Points: 5
  • Mon, May 7 2012 3:07 AM

    • dp2402
    • Not Ranked
    • Joined on Wed, Mar 14 2012
    • Posts 6
    • Points 75
    Re: RAM Retention Test pattern generation with Encounter Test Reply

    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? 

     

     

    • Post Points: 5
Page 1 of 1 (2 items)
Sort Posts:
Started by dp2402 at 04 May 2012 07:04 AM. Topic has 1 replies.