WaferProber
A wafer prober is an instrument to automatically electrically contact positions on a silicon wafer. A wafer is typically organized in rectangular 'dies' that have identical structures and are also called chips or sites. These dies can contain different test structures that are addressed by subsites (or subdies).
Concept
The module is designed to call a probe plan from an external software (e.g. Nucleus, Velox) or from a probe plan file, depending on the instrument driver. The user can then select wafers, dies, or subsites to be used in tables or simply ask for using the current one. The combination of all selected wafers, selected dies and selected subsites is used for the measurement run.
User interface
- Use the selection box "Sweep value wafer" to choose which source is used to vary wafers.
- Use the selection box "Sweep value die" to choose which source is used to vary dies.
- Use the selection box "Sweep value subsite" to choose which source is used to vary subsites.
- If the selected driver provides further options, they are shown in the section "Parameters".
- The button "Update" in the section "Probe plan" is used to retrieve the probe plan. It connects to the wafer prober and asks for all information about wafers, dies, and subsites. In case information is loaded from a wafer map file, a file dialog opens where the user can select a file. The field "File" shows the path of the file or the name of the probe plan.
- The collapsible section "Geometry" defines how the wafer is drawn in the wafer map.
- The tables for wafer, die, and subsite show the probe plan. Only checked items are used for the measurement.
- Use the right-click menu of the wafer, die, or subsite table to easily change the selection ("Check selected", "Uncheck selected", "Check only selected", "Check all", "Uncheck all"). If the driver supports it, the right-click menu also offers "Load wafer", "Unload current wafer", "Step to die", and "Step to subsite".
- During a run, the current wafer, die, and subsite are highlighted in the tables. Right-click the highlighted item and select "Go to next wafer", "Go to next die", or "Go to next subsite" to skip the remaining measurements of the current wafer, die, or subsite.
- In SweepMe! 1.5, the section "Actual values" displays the current set values for wafer, die, and subsite to see which position will be accessed next. This section is not available in SweepMe! 1.6. From version 1.6.1.5, the current position is shown in the wafer map.
Probe plan
SweepMe!'s WaferProber module uses an absolute addressing scheme. Instead of using communication functions like "go to next wafer" or "go to next die", functions are used that exactly indicate the index of the next wafer, die, or subsite. Therefore, we need the full information about the wafers in the cassettes or the dies/subsites to be measured beforehand. Using the 'Update' button one can retrieve the probe plan and crosscheck in the tables for wafer, dies, and subsites whether all information is loaded correctly. In case the wafer map is loaded from a file, the path of the file is displayed in the field "File". For such drivers, it is also possible to enter the path of the probe plan file directly in the field "File". For drivers that retrieve the probe plan from the prober software, the field is read-only.
Before each measurement run starts, the probe plan will be retrieved again to make sure it is up to date. The selection of wafer, dies, and subsites will remain unchanged.
Sweep values
The standard sweep values are "Wafer table", "Die table", and "Subsite table" which means that the selections within the tables at the bottom of the module are used. Further sweep values are "Current wafer", "Current die" and "Current subsite" which means that the corresponding table is not used. Instead, the wafer prober remains at the current wafer, current die, or current subsite. Furthermore, variables and sweep values of other modules can be selected, e.g. a column of a ReadValues module that contains the dies to be measured.
The sweep value of the module is defined to be a string of the format 'Waf[<wafer_identifier>]_Die[<die_identifier>]_Sub[<subsite_identifier>]' where <wafer_identifier>, <die_identifier>, and <subsite_identifier> are an index or any string that indicates a position to go. This sweep value is going into the data file name if the WaferProber module is above the MakeFile module. Further, this sweep value string is handed over to the driver for further processing. In case there is no variation of a wafer, a die, or a subsite the corresponding part in the sweep value is missing. For example, for a semi-automatic wafer prober that does not support changing wafers, the sweep value would be just 'Die[<die_identifier>]_Sub[<subsite_identifier>]'.
Wafer map
From version 1.6.1.5, the WaferProber module comes with a wafer map. It is shown as an additional widget in the dashboard that is named after the module label, e.g. "WaferProber Map".
The wafer map shows the dies of the probe plan and their state: "Pending", "Current", "Done", and "Inactive / Skipped". Dies with names of the format "column,row", e.g. "3,-2", are drawn at their position on the wafer. Other die names are arranged in a grid. Subsites are not drawn in the map. If the dies are provided by another module during the run, e.g. by ReadValues, the map is built from the dies as they arrive.
The bar at the top of the wafer map provides:
- Wafer: Selects the wafer that is displayed. If "Follow" is checked, the map automatically shows the wafer that is currently probed.
- Contact and Separate: Move the chuck to contact height or to separation height, if the driver supports it. The label "Contact:" shows the state "contacted", "separated", or "unknown". The state is updated after one of these buttons is used. If the driver can report the contact state, the reported state is shown.
- Fit: Fits the wafer to the window.
Below the map, the current wafer, die, and subsite are displayed. Hovering over a die shows further information about it.
If no run is active, right-click a die to select "Step to die" or to activate or deactivate the die (same as checking or unchecking it in the die table). Right-click next to the dies to load a wafer ("Load wafer") or to unload the current wafer ("Unload current wafer").
Geometry
The geometry of the wafer is defined in the collapsible section "Geometry" of the module. If the driver can report the geometry, the fields are filled automatically when the probe plan is updated.
- Notch: Position of the wafer notch: Down, Up, Left, or Right.
- Diameter in mm: Unknown, 100, 150, 200, 300, or 450. With "Unknown", the drawn outline is only fitted around the dies.
- Die pitch X in mm and Die pitch Y in mm: Distance between the dies in horizontal and vertical direction. Only available if a diameter is selected.
- Flip X and Flip Y: Mirror the wafer horizontally or vertically.
- Die convention: The die numbering used in the tooltips and labels of the map: "SEMI M20 (col,row, origin center)", "Top-left origin", or "Bottom-left origin". It only changes the display, the die names of the probe plan stay the same.
Driver programming
Module-specific concepts
- The module hands over the current sweep value to the driver during the semantic function apply() by defining self.value in the driver. The sweep value is a string given by "Waf[<wafer_identifier>]_Die[<die_identifier>]_Sub[<subsite_identifier>]" where <wafer_identifier> indicates the wafer, <die_identifier> indicates the die, and <subsite_identifier> indicates the subsite. These values are created based on the content of the wafer table, the die table, or the subsite table of the module.
- Further, the module defines the variable "self.sweepvalues" in the driver during the semantic function apply. It is a dictionary that contains the following keys - values:
"Wafer" -> the wafer to be measured "Die" -> the die to be measured "Subsite" -> the subsite to be measured "NextWafer" -> the next wafer "NextDie" -> the next die "NextSubsite" -> the next subsite
Instead of using 'self.value', we recommend to use the latest module version and make use of 'self.sweepvalues' that contains all necessary information. The key "NextWafer" can be used in fully automatic wafer probers that manage to preload the overnext wafer in order to speed up the wafer handling.
- If the user selects "Current wafer", "Current die" or "Current subsite" as sweep value, the sweep value is asked for using the driver function 'get_current_wafer', 'get_current_die', or 'get_current_subsite'. This function should return the same format of strings as used by 'get_probeplan'.
- The driver should go to separation height during signout. This allows safe combination with devices such as temperature controllers that need the chuck to be in separation height before they can start heating.
- In case the wafer prober remains at a single position (e.g. one specific subsite) while another module higher up in the sequencer does a parameter sweep (e.g. a temperature module), the wafer prober will call 'apply' at every measurement point, meaning it will go in separation height and back to contact again. If this behavior is not desired, the module running the parameter variation should be placed below the wafer prober in the sequencer tree.
- Functions that are triggered via the right-click menus or the buttons of the wafer map, e.g. 'load_wafer', 'step_to_die', or 'contact', are called individually. For each call, the module connects to the instrument, calls the function, and disconnects again.
Module-specific functions
There are driver functions that are only used and called by the WaferProber module. We recommend to use the driver 'WaferProber-Simulation_Driver' as a template. It implements all functions below and can be used to test the module without an instrument.
get_probeplan
Use this function to return either one of the options below
- list of dies and list of subsites
- list of wafers, list of dies, and list of subsites
- list of wafers, list of dies, list of subsites, and a probe plan name.
The variable 'self.port' can be used if the port_manager is used in order to communicate with the wafer prober to retrieve the wafer map information. Each list should contain strings that are then added to the corresponding table.
If the function "get_probeplan" has an additional argument, the path to the wafer map file will be handed over from the module. The module automatically opens a file dialog so that the user can select a file. Before the start of every run, "get_probeplan" will be called to renew the tables for wafer, dies, subsites.
get_current_wafer
Add this function to return a string of the current wafer. It will be called by the module, if the user selects "Current wafer" as Sweep value. Use of self.port is possible to communicate with the wafer prober.
get_current_die
Add this function to return a string of the current die. It will be called by the module, if the user selects "Current die" as Sweep value. Use of self.port is possible to communicate with the wafer prober.
get_current_subsite
Add this function to return a string of the current subsite. It will be called by the module, if the user selects "Current subsite" as Sweep value. Use of self.port is possible to communicate with the wafer prober.
load_wafer(wafer)
If a WaferProber driver defines this function, the user can right-click the wafer table or the wafer map to load the selected wafer. The selected wafer is handed over as argument to the function 'load_wafer' and the string must be parsed to identify cassette and wafer information. The driver should check whether a wafer is already on the chuck.
unload_wafer
If a WaferProber driver defines this function, the user can right-click the wafer table or the wafer map to unload the current wafer. The driver should check whether a wafer is on the chuck.
step_to_die(die)
If a WaferProber driver defines this function, the user can right-click the die table or a die in the wafer map to go to the selected die. The selected die is handed over as argument to the function 'step_to_die'.
step_to_subsite(subsite)
If a WaferProber driver defines this function, the user can right-click the subsite table to go to the selected subsite. The selected subsite is handed over as argument to the function 'step_to_subsite'.
get_wafer_geometry
Optional, from version 1.6.1.5. Return a dictionary that describes the wafer for the wafer map. The function is called when the user clicks "Update" and the returned values are used to fill the section "Geometry". The module uses the following keys:
- "diameter_mm": wafer diameter in mm
- "pitch_x_mm" and "pitch_y_mm": die pitch in mm
- "notch": "down", "up", "left", or "right"
- "origin": "upper_left" or "lower_left" to set the die convention
Further keys are allowed. Use None for values that are unknown, so that the corresponding field is not changed. The function should not raise an exception.
contact, separate, get_contact_state
Optional, from version 1.6.1.5. If a driver defines 'contact' and 'separate', the buttons "Contact" and "Separate" of the wafer map move the chuck to contact height or separation height. 'get_contact_state' returns True if contacted, False if separated, and None if unknown. It is called after one of the buttons was used.