MRA4 UPDATE NOTICE REV 3.03 - Advantest

Cover 

C 

2004 

MRA4 

UPDATE NOTICE 

REV 3.03 

MANUAL NUMBER 

ADVANTEST CORPORATION 

All rights reserved. 

8339540-29 

First printing August 10, 2004 

Printed in Japan

PREFACE 

PREFACE 

ADVANTEST and ATL are trademarks of ADVANTEST Corporation. 

MRA4 UPDATE NOTICE REV 3.03 

Sun, Sun Microsystems, Sun logo, Ultra, Sun Blade and Solaris are trademarks or registered trademarks 

of Sun Microsystems, Inc. in the United States and other countries. 

UNIX is a registered trademark in the United States and other countries, licensed exclusively through 

The Open Group. 

Motif is a trademark of The Open Group. 

Adobe, the Adobe logo, Acrobat, Acrobat Reader, FrameMaker, FrameViewer and PostScript are trademarks 

of Adobe Systems, Inc. 

All other marks referenced herein are trademarks or registered trademarks of their respective owners. 

Aug 10/04 

Preface

Manual 

Rev 

Aug 10/04 

Date 

RECORD OF REVISIONS 

Remarks 

(Software REV) 

22 Mar 20/03 (REV 3.01) 

23 Jun 5/03 (REV 3.01A) 

24 Sep 10/03 (REV 3.01A1) 

25 Oct 15/03 (REV 3.02) 

26 Oct 30/03 (REV 3.02-1) 

27 Feb 10/04 (REV 3.02A) 

28 Mar 23/04 (REV 3.02B) 

29 Aug 10/04 (REV 3.03) 

Manual 

Rev 


Date 

Remarks 

(Software REV) 

R-1

TABLE OF CONTENTS 

TABLE OF CONTENTS 


1. SUMMARY OF REVISION ................................................................ 1-1 

2. ENHANCED FUNCTIONS ................................................................ 2-1 

3. IMPROVED ITEMS ............................................................................. 3-1 

3.1 mra4tool .................................................................................................. 3-1 

3.2 mra4_peer_analy .................................................................................... 3-2 

3.3 MRA4 Communication Control Program ................................................. 3-4 

Aug 10/04 

C-1

1. SUMMARY OF REVISION 

Aug 10/04 

(1) Revision number 

• MRA4 REV 3.03 



(2) Related manual revised 

MRA4 MEMORY REPAIR ANALYZER REFERENCE MANUAL 8311158-17 

MRA4 MEMORY REPAIR ANALYZER SOFTWARE SPECIFICATIONS 8324165-29 

MRA4 INSTALLATION GUIDE 8311153-13 

MRA4ev2 RCPU-C Unit Diagnostic Program Manual 8700347-01 

(3) Reason for revision 

Addition of functions 

Improvement of functions 

(4) Revised product 

Product code Product name 

PMR451-71E MRA451SU 

(5) Software related to MRA4 REV 3.03 

For the T5571P test system 

Software Requirements 

UNIX operating system 

(Note) 

Window manager 

Basic system software 

Solaris 2.5.1, Solaris 7 or Solaris 8 

OSF/Motif V1.2.3 or later 

CDE window manager (when using Solaris 7 or Solaris 8) 

ASX/U-51 REV 4.01 or later 

ASX/U-51 REV 5.01 or later (when using Solaris 7) 

ASX/U-51 REV 6.00-1 or later (when using Solaris 8) 

Note: When Sun Ultra 5 is used, Solaris 2.5.1 Hardware 11/97 or Solaris 7 or Solaris 8 is 

necessary. 

1-1



For the T5371 test system 


UNIX operating system Solaris 7 or Solaris 8 

Window manager CDE window manager 

Basic system software 

Note: The pattern program compiled by XATL/U-50 or XATL/U-51(PXTL51-36S) REV 1.02-1 

or earlier needs to recompile. 

For the T5375 and T5376 test systems 


For the T5377S test system 

ASX/U-51 REV 5.00 or later (Note) 

ASX/U-51 REV 5.04A or later 

(When using an FMRA board of which the AFM size is 

4 GB) 

ASX/U-51 REV 6.00-1 or later (when using Solaris 8) 


UNIX operating system Solaris 8 


Basic system software ASX/U-51 REV 6.00-1 or later 




Basic system software ASX/U-51 REV 6.03 or later 




Basic system software ASX/U-51 REV 6.03B or later 

1-2 Aug 10/04

Aug 10/04 

(6) Applicable systems 

T5571P 

T5371 

T5375 

T5376 

T5377 

T5377S 

(7) List of revisions 

For the T5571P test system 

MRA4 revision SunOS revision ASX/U-51 revision 

1.00 Solaris 2.5.1 (Note) 4.01 or later 

1.00-1 Solaris 2.5.1 (Note) 4.01 or later 



1.03 

1.04 

1.04-1 

1.04-2 

1.04-3 

1.04A 

1.05 

1.05A 

1.05A1 

Solaris 2.5.1 (Note) 4.01 or later 

Solaris 7 5.01 or later 



















1-3




2.00 

2.00-1 

2.01 

2.01-1 

2.02 

2.02A 

2.02A1 

3.00 

3.00-1 

3.01 

3.01A 







Solaris 8 6.00-1 or later 

























1-4 Aug 10/04

Aug 10/04 


3.01A1 

3.02 

3.02-1 

3.02A 

3.02B 

3.03 



Note: When Sun Ultra 5 is used, Solaris 2.5.1 Hardware 11/97 is necessary. 





















1.02 Solaris 7 5.00 or later 



1.04-1 Solaris 7 5.00 or later 



1.04A Solaris 7 5.00 or later 


1.05A Solaris 7 5.00 or later (Note) 

1.05A1 Solaris 7 5.00 or later (Note) 

2.00 Solaris 7 5.00 or later (Note) 

1-5




2.00-1 Solaris 7 5.00 or later (Note) 

2.01 

2.01-1 

2.02 

2.02A 

2.02A1 

3.00 

3.00-1 

3.01 

3.01A 

3.01A1 

3.02 

3.02-1 

3.02A 

3.02B 

3.03 

Solaris 7 5.00 or later (Note) 






























Note: When using an FMRA board of which the AFM size is 4 GB, use ASX/U-51 REV 5.04A 

or later. 

1-6 Aug 10/04

Aug 10/04 




2.00-1 Solaris 8 6.00-1 or later 

2.01 Solaris 8 6.00-1 or later 



2.02A Solaris 8 6.00-1 or later 

2.02A1 Solaris 8 6.00-1 or later 









3.02B Solaris 8 6.00-1 or later 

3.03 Solaris 8 6.00-1 or later 

















1-7







3.02B Solaris 8 6.00-1 or later 

3.03 Solaris 8 6.00-1 or later 





3.02A Solaris 8 6.03 or later 

3.02B Solaris 8 6.03 or later 

3.03 Solaris 8 6.03 or later 

For the T5377S test system 


3.03 Solaris 8 6.03B or later 

(8) Disk Space Required for the MRA4 Installation 

MRA4 

Approximately 40 MB of free space is necessary when installing MRA4. 

Online manual 

Item Required disk space 

Acrobat Reader 4.05 for UNIX 17 MB 

Acrobat Reader 5.1 for Windows 26 MB 

PDF Manual data 10 MB 

1-8 Aug 10/04

2. ENHANCED FUNCTIONS 

Aug 10/04 

(1) MRA4 can be used in the T5377S test system. 

(2) MultiArea Analysis Mode can be used when PIN MODE is set to B. 

Relevant test systems: T5377 and T5377S 


2. ENHANCED FUNCTIONS 

(3) A function, which can perform repair analysis by dividing the addresses of a device, has 

been added to MultiArea Analysis Mode. 


(4) A function (Overdrive Repair Mode), which outputs repair addresses of failure cells after 

the repair analysis is performed, has been added. 


(5) If the repair condition text file, in which comments are described, are read and saved by 

using mra4tool, the comments are also saved. 

However, only comments (a) and (b) can be saved. 

MRA{ 

}; 

(a) 

Spare line layout definition 

(b) 

(6) An option, which displays the spare group number for each block group, has been added 

to mra4comp. 


(7) The user analysis program that is created by using C++ can be loaded. 

Relevant test systems: T5375, T5376, T5377, and T5377S 

(8) MRA4 is now compatible with Sun Blade 150 in the standard 80 GB DISK model (H3- 

610146). 

Relevant test systems: T5371, T5375, T5376, and T5377 

For more information, refer to "MRA4 MEMORY REPAIR ANALYZER REFERENCE MANUAL." 

2-1

3. IMPROVED ITEMS 

3.1 mra4tool 

Aug 10/04 



(1) The following display problems occurred in the mra4tool main window and Block Group 

View window: 

1 

2 

3 

4 

In the Block Group View window, if the block information display area overlapped any 

other window or the window was moved, the displayed block information sometimes 

disappeared. 

In the Block Group View window, although the mouse pointer was moved to a block, 

the block information was sometimes not displayed in the block information display area. 

If the repair condition text file was read when the Block Group View window was displayed, 

the block information that is displayed in the Block Group View window did not 

change. 

If Block and Block Group in the View menu were selected in this order and the mouse 

pointer was moved to the block information display area in the main window, the outline 

of a button that looked as if it was selected appeared in the space of the window. 

5 In the main window, if Block and Block Group in the View menu was selected in this 

order when the Block Group View window was displayed, the Block Group button in 

the block information that was displayed in the Block Group View window sometimes 

did not appear as if it was clicked. 

Relevant software revision: REV 3.02B 

Relevant test systems: T5571P, T5371, T5375, T5376, and T5377 

Improvement The above problems have been fixed. 

(2) If the repair condition text file that includes the following definitions was read when mra4tool 

started, an error message was displayed and the file was sometimes not read: 

1 

MRAVariableRowMode was defined as "disable", however, neither RARowSections 

nor MRARowSectionAssignment were defined. 

2 

MRAVariableColumnMode was defined as "disable", however, neither MAColumnSections 

nor MRAColumnSectionAssignment were defined. 

 

Error Invalid File format. 

Relevant software revisions: REV 1.01 through REV 3.02B 


Improvement The repair condition text file that includes the above definitions can be 

read. 

3-1



3.2 mra4_peer_analy 

(1) If Fail Count Mode was executed by using the RCF that defines the number of blocks for 

repair as 9216, the Fail Count Mode results were sometimes incorrect. 


Relevant test system: T5371 

Improvement Correct Fail Count Mode results are output. 

(2) If Fail Count Mode was executed by specifying a bock group that is not analyzed by using 

the LIB MRA4EXEC device mask mode, incorrect Fail Count Mode results were sometimes 

acquired. 


Relevant test system: T5571P 

Improvement The correct Fail Count Mode results are output. 

(3) The user function, which was inserted in the user function insertion point, 

MraPOINT_POST_UNREPAIR_BITFAIL, was sometimes not called when the bit fail repair 

was decided to be unrepairable. 



Improvement The user function, which was inserted in the user function insertion point; 

MraPOINT_POST_UNREPAIR_BITFAIL, is called correctly. 

(4) The execution time of analysis was long under the following conditions because the MRA4 

hardware accessed to the failure information on the devices that were not tested or analyzed: 

 

If excluded from the test target by using the SET REJECTION statement. 

If excluded from analysis target by using the LIB MRA4EXEC device mask mode. 



Improvement The execution time of analysis can be reduced because the MRA4 hardware 

does not access the failure information on the device which are not 

tested or analyzed. 

(5) If "use higher-priority spare lines", which is a condition used to obtain the best solution in 

Tree Repair Algorithm, was selected by specifying 1 to bit 17 of the eoptn argument of LIB 

MRA4EXEC and the repair analysis was executed, the number of spare lines that was output 

was not the possible minimum number, depending on the fail pattern. 

For more information, refer to the following example. 



3-2 Aug 10/04

Aug 10/04 



Improvement The repair solution, which uses higher-priority spare lines and the minimum 

number of spare lines, is output. 

 

RCF setting 

8 row spare lines 

8 column spare lines 

Repair Priority : Column 

• Target bit fails 

Repair solution made before improvement 

Repair solution made after improvement 

Row: 8 spare lines 

Column: 8 spare lines 

Row: 6 spare lines 

Column: 8 spare lines 

After the improvement, the number 

of row spare lines that were used 

was reduced by 2. 

3-3



3.3 MRA4 Communication Control Program 

3-4 

(1) If the program was executed in the following order to acquire data by using WFBMAP3 WF- 

BAccel in the T5375, an error of code 60 occurred in SUBR WFBMRA4. 

PRO TEST 

LIB MRA4INIT 

↓ 

LIB MRA4EXEC ← Executes in the NO-WAIT mode 

↓ 

LIB MRA4INIT 

↓ 

SUBR WFBMRA4 ← WFBMAP3 WFBAccel 


Relevant test systems: T5375 and T5376 

Improvement Data can be acquired correctly by using WFBMAP3 WFBAccel. 

Aug 10/04

MRA4 UPDATE NOTICE REV 3.03 - Advantest

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?