Jump to content

Specific Process Knowledge/Lithography/EBeamLithography/FilePreparation: Difference between revisions

Lgpe (talk | contribs)
Thope (talk | contribs)
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
'''Feedback to this page''': '''[mailto:e-beam@danchip.dtu.dk?Subject=Feed%20back%20from%20page%20http://labadviser.danchip.dtu.dk/index.php?title=Specific_Process_Knowledge/Lithography click here]'''
'''Feedback to this page''': '''[mailto:e-beam@nanolab.dtu.dk?Subject=Feed%20back%20from%20page%20http://labadviser.nanolab.dtu.dk/index.php?title=Specific_Process_Knowledge/Lithography click here]'''


= Introduction =
= File preparation for exposure on JEOL 9500 =


[[Image:Conversion.png|600px|right|]]


[[Image:Conversion.png|600px|right|]]
For pattern exposure on the JEOL 9500 tool the pattern must be stored in JEOLs own proprietary JEOL52v3.0 format, also known as V30.  At DTU Nanolab we use Beamer to generate the V30 file from the original design file. We recommend using GDS as the original file format although Beamer can read multiple formats. In addition to the a pattern file exposure requires a Schedule file (SDF) and a Jobdeck file (JDF). These are text files where the user defines exposure conditions. Before pattern writing these three files (V30, SDF and JDF) are compiled into a final magazine file (MGN) which fully defines the exposure job.


An e-beam exposure requires a v30-file, which contains information on the pattern to write, a jobdeck file (jdf-file), and a schedule file (sdf-file). The sdf- and jdf-file contain information about size and position of substrate, dose, current, and shot step. The sdf-file, jdf-file and v30-file are compiled to a magazine-file (mgn) on the 9500 computer.
== Conversion from GDS to V30 in Beamer ==


Beamer has a lot of different modules and can be used to manipulate a design considerably. In this section we will only look at how to import a design file and export it to V30.


When a magazine-file is prepared, the actual shot time can be estimated by the e-beam computer (9500).
Beamer uses a node based workflow and each task is defined by a node with its own set of parameter. For this simple example we will only use the "Import" and "Export" nodes.


== Basic SDF conten ==


<br clear="all" />
== Basic JDF content ==


= Preparing a GDS file =


If the layout is asymmetric, the conversion might result in an offset of the final layout onto the wafer. It is therefore recommended to symmetrise the layout, e.g. by inserting small structures in the corners of a rectangle that covers the layout.
If the layout is asymmetric, the conversion might result in an offset of the final layout onto the wafer. It is therefore recommended to symmetrise the layout, e.g. by inserting small structures in the corners of a rectangle that covers the layout.
Line 146: Line 148:
  DIRE01     INITIAL: PDEFBE, SUBDEFBE, CURRENT
  DIRE01     INITIAL: PDEFBE, SUBDEFBE, CURRENT
                     CYCLIC: CURRNT (every 5 minutes without interupting the writing of a field)
                     CYCLIC: CURRNT (every 5 minutes without interupting the writing of a field)
</pre>


</pre>
The full list of calibration [[Specific_Process_Knowledge/Lithography/EBeamLithography/FilePreparation/Pathlist|paths are available here.]]


== Alignment and global mark detection ==
== Alignment and global mark detection ==
Line 159: Line 162:




HSWITCH:
'''HSWITCH''':


HSWITCH ON,OFF: machine focusses beam to the Height average between P and Q marks
HSWITCH ON,OFF: machine focusses beam to the Height average between '''P and Q marks'''


HSWITCH OFF,ON: machine focusses beam to the height average of chip marks
HSWITCH OFF,ON: machine focusses beam to the height average of '''chip marks'''


HSWITCH ON,ON: machine focusses beam to the height average of chip marks. The chip mark height will overrule the P and Q mark height during exposure.
HSWITCH ON,ON: machine focusses beam to the height average of chip marks. The chip mark height will overrule the P and Q mark height during exposure.
Line 173: Line 176:
CHIPAL V1/V4:
CHIPAL V1/V4:


The virtual CHIPAL command in the sdf-file, CHIPAL V1 or CHIPAL V4, can be used to measure the height of the substrate at well-defined positions on the substrate, thus correcting for height variations before pattern writing. To use this, HSWITCH should be set to 'HSWITCH OFF,ON' or 'HSWITCH OFF,ON'.
The virtual CHIPAL command in the sdf-file, CHIPAL V1 or CHIPAL V4, can be used to measure the height of the substrate at well-defined positions on the substrate, thus correcting for height variations before pattern writing. To use this, HSWITCH should be set to 'HSWITCH OFF,ON' or 'HSWITCH ON,ON'.




Line 247: Line 250:
[[File:markorientation.jpg|300px]]
[[File:markorientation.jpg|300px]]


note 2: Always add 10% to the current in this command to make sure you work well below 100 MHz and thus will not be affected if the current fluctuates above the base current.
note 2: Always add 5% to the current in this command to make sure you work well below 200 MHz and thus will not be affected if the current fluctuates above the base current.


== Dose variation ==
== Dose variation ==
Line 636: Line 639:
# The order of commands might be wrong in either the sdf- or jdf-file; check the order of commands in the templates in the directory home/eb0/jeoleb/job/templates
# The order of commands might be wrong in either the sdf- or jdf-file; check the order of commands in the templates in the directory home/eb0/jeoleb/job/templates
# The sdf- or jdf-files might have been opened in a text-program different from SuperEdi, e.g. notepad; this can corrupt the files and add linefeeds or tokens at line-ends. This can be checked in SuperEdi. In most cases, the problem can be solved by opening the sdf- and jdf-file in SuperEdi and save it again while setting the line endings to UNIX.
# The sdf- or jdf-files might have been opened in a text-program different from SuperEdi, e.g. notepad; this can corrupt the files and add linefeeds or tokens at line-ends. This can be checked in SuperEdi. In most cases, the problem can be solved by opening the sdf- and jdf-file in SuperEdi and save it again while setting the line endings to UNIX.
# If none of the above works find a template home/eb0/jeoleb/job/templates and re-write your information into it, do NOT copy for the reasons of the last point above.
# The path writing requires a scan speed larger than 100MHz; increase the shot pitch (SHOT) in the sdf-file and compile again.
# The path writing requires a scan speed larger than 100MHz; increase the shot pitch (SHOT) in the sdf-file and compile again.