1

Memory Impact Assessment(MemIA)

2

MEMIA PRODUCT The MEMIA product has been made for the Impact Analysis of memory compilers with the change in SPICE.

It generates the results in an excel sheet and in graphical form for simplicity.

3

Programming Languages Used:

1. Perl

2. Shell Scripting

3. Visual Basic

Impact Assessment - Flow

4

•Compiler Name•PVT• Slope/

Loads(default)•Different Mcf

setup • Spice models•Analysis type

•Cutlit (optional)

Excel Based Input (Techno based)

•Using Initial archived setup

•Automatic update

Update existing mcf setup

• In background

mcf simulations•mcf output dump in

Excel

Excel based result file

•Excel standardization for required analysis

Comparison Analysis from Excel result file

Using VB & Pivot Table

Using Perl Script

Using Excel

Using Memvalid Kit

5

Parameters included in the Analysis

1. P_leakage

2. P_ac_rd_hpa

3. tP_ac_wr_hpa

4. Th

5. taa

6. tckh

7. tckl

8. tcycle

9. tdh

10.tph

11.tah

12.tds

13.tps

14.tas

6

How to run the MEMIA product

7

1. Update the 'Path of Directory of MCF Result' in memIA.xls as your current working directory.

2. Source the script $MEMIAROOT/bin/upt_comp_list 'space' 'name of the Technology' in the user path. eg source $MEMIAROOT/bin/upt_comp_list CMOSM40

3. In the excel file click on 'Update Compiler List' button and select the respective technology and compiler.

UPDATING THE COMPILER LIST:

8

MEMVALID KIT:

Specify the user name and path of your password file in memIA.xls (eg. /home/singht/tanvi.pf)

9

SPICE Comparison1. Select 'yes' if you want to compare the reference spice with the

given spice.

2. Give the path for the new spice4Mem in memIA.xls.

3. If user selects 'no' then it will not compare the timing parameters and will simply generate results for a single SPICE.

10

GIVING A CUTLIST:

1. In memIA.xls select 'yes' for cutlist.

2. Have the required cutlist in the work area as 'compiler_name.cutlist' (eg. CMOSM40_ST_ROM.cutlist)

3. If the user selects 'no' then a default cutlist will be taken from the mcf setup.

11

GLOBALLY RUNNING THE PRODUCT:

1. Update the path in the excel file. (same as the path above i.e. current working directory)

2. Select the required technology, compiler and it's version in the excel interface.

3. Update the username and password in the excel file.

4. Source MEMIAROOT

5. Run 'command'

12

GETTING RESULT IN GRAPHICAL FORM:

1. After getting the ouput files, click on the button 'Generate Pivot Table' in memIA.xls.

2. This creates a graphical comparison sheet named 'result.xlsx' in the work area specified in memIA.xls.

13

DEMO

14

CONTENTS OF INPUT SHEET

Input Excel contains 3 sheets :

Master sheet :It works as a interface for user it takes input from user.

Track Sheet :Contains Fixed fields of measure.setup

Configuration :Contains fields of measure.setup of different compilers

15

Update Compiler List

Compiler list is updated based on the compilers submitted in upt and uptplus.

Step For updating

Run a script in Unix area

Press a button in Excel sheet which update compiler list

Select Technology either M40 or C28SOI

Select compiler & its version

16

Implementation of Master Sheet

• It downloads the MCF setup from Its DE product

SELECT COMPILER & then its VERSION

• It will change the Ucdprod & .Ucdprod

Give Path of New Spice4Mem

• Update Measure.setup of different compilerSELECT PVTS

Input from User Purpose of input

17

Scripting Part

Copy mcf setup in

given area

Update mcf setup

Run the simulation

Save result in

excel

Collect name of

error setup

In scripting part I used Perl packages which is used to convert excel file into text file and vice versa.

A hierarchy structure of setups is made by the scripting.

18

Mcf simulation Output Hierarchy

Main Setup

Compiler1

Spice1 Spice2

Compiler2

Spice1 Spice2

19

Reporting Part

Reporting

Spice comparison(compil

er name)

Diff &%diff

Path of error setup

Result.xls (Pivot Table)

Raw data sheet

Pivot table

• It shows the difference and %difference in excel sheet w.r.t first spice which is considered as reference spice.

• In second sheet it shows the path of the mcf setup in which there is error.• In Pivot Table first it saves all results in one excel sheet• Makes pivot table using this data• Using pivot table we can compare between different compilers, spice and pvt.

20

Master Sheet

21

New Spice4Mem Path

22

23

Pivot Table Generation

On pressing button “Generate Pivot table” from Master Sheet it automatically generates the Raw data Sheet and Pivot table

24

GENERATING PIVOT TABLE

25

Spice Comparison Sheet

26

How to avoid Errors1. The product may not run properly if there is an issue in the UPT or UPTplus areas.

2. If there is an error in the MCF simulations, the result cannot be obtained. In this case the user will have to manually debug and identify the MCF error.

3. Please make sure that the path given in the memIA.xls sheet is the same as the path of the current working directory.

4. As excel is opened in windows this path should be such as ‘\\samba\data\MAT10\anju_work\TANVI\MEMIA_PRODUCT’

5. However, the path for the new spice should be the same as it’s UNIX path eg. ‘/data/cmem6/WORK_TANVI/products/’

6. Please make sure that you do not have any pending or unused jobs before running the product as then the results will not be dumped in an excel sheet.

7. Please delete the compiler and compiler.xls files before updating the compiler list again.

8. Delete or rename the old result.xlsx file before generating a new file.

9. Lastly, DON’T FORGET TO SAVE THE memIA.xls.