July 16, 2019
We were provided this sample map file said to be an ALP file format.
At the beginning of the file is a short preamble:
ais likely "automation information start"AUTOMATION INFORMATION REALTIME WAFERMAPXY WAFER MAPCREATED BY REV: ZMD 0.3,MM/DD/YYYYFollowing the preamble is a list of parameter/values.
| Parameter | Value | Comment |
|---|---|---|
| LOT | XNXNNNNX | The wafer's LotID |
| WAFER | 10 | The wafer number |
| PRODUCT | Y | The product ID |
| CMAP | XNXNNNNX.XN-NXXX | the name of the map file? |
| READER | XNXNNNNX-NNXN | what the OCR reads on the wafer |
| XSIZE | 77 | the X step size |
| YSIZE | 241 | the Y step size |
| UNITS | mils | units - might also support mm or even um |
| ROWS | 32 | number of horizontal rows |
| COLS | 107 | number of vertical columns |
| FLAT | 90 | location of the flat/notch. 0,90,180,270 |
| DATE | YYYY-MM-DD | date |
| TIME | HH:MM:SS | time |
| TEST SYS | XXXXXXX | string describing the test system |
| TEST STA | XXXXXXX | string describing the test station |
| PROGRAM | XXXXXXX | string describing the program |
| PROBECARD | XXXXXXX | string identifying the probe card |
| CABLE | XXXXXXX | string describing the cable? |
| LOADBOARD | XXXXXXXX | string identifying the load board |
| SYSTEM ID | XXXXXXXX | string identifying the system ID |
| PROBER | XXXXXXXX | string describing the prober |
| COMMENT | XXXX XXXX | user comment; don't know length limitation |
| PASSTYPE_1 | 1 "PassBin" | bin code denoting pass |
| SAMP1STS | N | don't know |
| SAMP2STS | N | don't know |
| WAFER_STS | C | wafer status? |
following the header table of parameters are a few more lines which we don't really know what they do.
aie likely "automation information end"Unlike most map files, the data is in the form of Xpos,Ypos,Bin or xyb. So basically every die is listed by its position in the array followed by its bin code. This means that there is no need for a NULL bincode since only die that are present are listed.
sow, January DD YYYY, HH:MM:SS, UNKNOWN, XNXNNN-NNXN likely "start of wafer" num,11 not clear what this tells us - maybe the number of unique bin codes to follow?xyb,43,0,1xyb,44,0,1xyb,45,0,1xyb,46,0,1xyb,47,0,1xyb,48,0,1xyb,49,0,1xyb,50,0,1xyb,51,0,1xyb,52,0,1xyb,53,0,1xyb,54,0,1xyb,55,0,8xyb,56,0,1xyb,57,0,1xyb,58,0,1xyb,59,0,1xyb,60,0,1xyb,61,0,10xyb,62,0,1xyb,31,1,13xyb,32,1,1xyb,33,1,13eow likely "end of wafer"Because of the separators between the header and wafer data, it may be that this format could support multiple wafer maps.
We don't have any specifications or documentation on this format but given what is obvious by examination a good converter could be written to other formats.