4. The MOSIS Mail System LEARNING THE MOSIS COMMAND LANGUAGE 4.1. Introduction Online users can request information, submit projects, ask for the status of a wafer run, or ask questions of the MOSIS staff, by sending electronic mail messages to MOSIS. Software developed by MOSIS, using a format called the MOSIS Command Language, interprets these requests automatically. This enables MOSIS to serve thousands of users with a very small staff. Although this chapter is primarily of interest to network users, offline users may be interested in noting the various fabrication steps and the kinds of information available from MOSIS. Of course, all users are welcome to contact the MOSIS Liaison or other appropriate MOSIS staff with special questions or requests. 4.2. Accessing MOSIS Prospective users can send an initial message to MOSIS and retrieve information on various topics without being an authorized user. Messages should be sent to the MOSIS address: MOSIS@MOSIS.EDU 4.2.1. First Message A first message to MOSIS usually contains regular text, that is, the message is not in MOSIS request format: ------------------------------- | | | | | From: Dave@Navy | | To: mosis@MOSIS.EDU | | Hello, is anyone there? | | | | | ------------------------------- MOSIS' Response MOSIS will respond with the following message, which includes samples of information requests. - - - -------------------------------------------------------------------------- | | | | | | | From: MOSIS@MOSIS.EDU | | Subject: WELCOME TO MOSIS! | | To: Dave@Navy | | | r | To request information, submit projects or find the status of a wafe| | run, send an electronic mail message to MOSIS@MOSIS.EDU in the| | following 'REQUEST' message format: | | | | REQUEST: INFORMATION | | TOPIC: TOPICS | | REQUEST: END | | | d | The MOSIS software automatically interprets these REQUEST messages an| s | replies with the specific information. For this reason, it i| d | important that your message syntax be accurate. Each message shoul| | end with a 'REQUEST: END'. | | | a | If the body of messages sent to your system is required to be below | d | certain number of lines or characters, include the LINE-LIMIT an| e | BYTE-LIMIT parameters in your request messages and fill in th| r | appropriate value(s). MOSIS will fragment its response to you| s | request(s) into several individual messages to meet your system'| | requirements, e.g., | | | | LINE-LIMIT: 50 | | BYTE-LIMIT: 2000 | | | | If you have questions or special requests that require the attention | : | of the MOSIS staff, send an ATTENTION message in the following format| | | | REQUEST: ATTENTION | | (Put message here) | | REQUEST: END | | | | Do NOT include any ':'s in the message portion of your ATTENTION | e | REQUEST or the MOSIS software will attempt to parse your message. Th| | MOSIS Liaison will then receive an incomplete message. | | | | The MOSIS Service | | | | | - - - -------------------------------------------------------------------------- 4.3. Request Message Format As shown above, the format of a request is basically the same for all messages. Each message to MOSIS may contain several requests, each of which may in turn contain several parameters as arguments for the requests. See Section 13.3.2 of the Reference Section for sample messages to MOSIS. 4.3.1. Three Fields There are three parts to a request message: (1) the request field, (2) the parameter field(s), and (3) the end field. - A single message may contain different requests. A list of the available requests is given in Section 4.5 of this chapter. - Each request has various parameters that can go with it. For example, 'REQUEST: ATTENTION' may be followed by such parameters as 'ID' or 'P-PASSWORD'. See Section 13.3 of the Reference Section for request templates with their available parameters. - The "END" request marks the end of requests in a message. Please note that any text written after this line will be ignored. Therefore, do not append two or more requests together without removing the "REQUEST: END" line between them; otherwise, ONLY the first request will be seen by MOSIS. - All request and parameter names may be abbreviated, as long as there are no ambiguities. 4.3.2. Keep in Mind All MOSIS Request and Parameter names are case independent. No control codes other than , , , or should be used. No line should begin with "XXX:" unless "XXX" is a keyword as described above (i.e., "REQUEST" or a parameter). It is recommended that requests include the type of request and the Project-ID in the SUBJECT field of your message (use the project name if you have not yet been assigned an ID). This will facilitate searching through a series of messages if the MOSIS staff needs to find a particular message that you sent in. 4.3.3. Net-Address Parameter MOSIS sends replies to your messages to the NET-ADDRESS, a parameter specifed for your project in the NEW-PROJECT request. This is always true, unless there is a problem with the NET-ADDRESS parameter or the specified ID is not valid (does not exist or is not accompanied by the proper P-PASSWORD). In this case, MOSIS directs responses to the SENDER of the request. 4.4. Project Submission Sequence You should understand the MOSIS request system as it relates to the entire project submission sequence. Section 13.3 of the Reference Section gives more details on each request template; you should review this section before proceeding with project submission to MOSIS. There are four states within the submission sequence that define primarily whether MOSIS has a valid CIF file for your project and where this file is in the sequence. The following sections describe some of the major MOSIS requests in the context of these four states: ------------------------- | | | 1. Before Valid CIF | | | ------------------------- -------------------------------------- | | | 2. Valid CIF (Accepted by MOSIS) | | | -------------------------------------- ----------------------------------- | | | 3. CIF Queued for Fabrication | | | ----------------------------------- -------------------------- | | | 4. Being Fabricated | | | -------------------------- 1. Before Valid CIF The New-Project Request The first request to MOSIS is usually the NEW-PROJECT request. MOSIS replies to this message by assigning you a Project-ID (e.g., 12345) in its reply. You MUST refer to this Project-ID in all subsequent communications to MOSIS concerning this project. 2. Valid CIF (Accepted by MOSIS) Checking your CIF File To check the validity (syntax) of your CIF file before fabrication, use the SUBMIT request. This submits your file for a syntax validation check called CHECK_PROJ. You may then use the FABRICATE request or, if there are problems with your file, you may correct and resubmit it. Updating CIF To update CIF, simply resubmit it (using the SUBMIT or FABRICATE request). If your CIF was submitted in fragments, however, you must use the DELETE-CIF command before resubmitting. Use this command request also when you have submitted a bad fragment and want to change it. This does NOT cancel your project. The Update Request To change one or more parameters to your project, e.g., SIZE, use the UPDATE request. This does NOT affect your CIF file. (TECHNOLOGY or LAMBDA parameters cannot be changed with this request.) 3. CIF Queued for Fabrication The Request for Fabrication After receiving your Project-ID, you may submit your CIF for syntax check and subsequent fabrication. If your CIF is valid, you will receive an acknowledgment from MOSIS that your project is queued for fabrication. (If your CIF fails the syntax check, you will also be notified.) Note that this message includes a new ID, called a Fab-ID which identifies the wafer lot of your project. A Fab-ID (for example, "M11XAA1") consists of three parts: a four-character Run-ID ("M11X"), a two-letter Chip-ID ("AA"), and a project number ("1") on the chip. If you are sharing a chip, your project could be 1 through 4. A run is also given a nickname (e.g., "Xerxes") for easy reference (and for fun!). This four letter Run-ID (referred to in this manual as "M11X") is assigned to each distinct mask set used to fabricate a lot (a set) of wafers. If you have requested that a chip be refabricated on another run, you will receive a new fabrication announcement with a new Fab-ID which retains the Chip-ID and assigns a new Run-ID. Cancelling Fabrication If you decide, after issuing the FABRICATE request, that you want to cancel fabrication, use the CANCEL-FABRICATE request. You MUST do this before you resubmit a new CIF for fabrication (under the same Project-ID). If you want to cancel your entire project, use the CANCEL-PROJECT request. 4. Being Fabricated Status Request Use the status (STS) request to ask for estimated fabrication and project delivery dates for your particular run (REQUEST: M11X.STS). Probe Request Vendors probe each wafer lot to ensure that wafers meet their specifications. MOSIS then does its own parametric probing using MOSIS test structures, making sure that wafers meet the fabricator's electrical parameter specifications and MOSIS' requirements. You can request probing results for a wafer lot (for example, lot M11X) by including REQUEST: M11X.PRM in an INFORMATION request. Delivery of Packaged Chips When device packaging is complete, MOSIS delivers your packaged chips to you, along with information describing the characteristics of your particular wafer lot. This information package includes a summary of the electrical characteristics of the wafer lot, a SPICE and/or BSIM deck, and a bonding diagram. Report Request After you have received your packaged parts and tested them, send MOSIS your test results in the form of a report message to MOSIS. These test results are used by MOSIS' quality control in vendor evaluation. See page 112 of the Reference Section for a sample report to MOSIS. 4.5. List of MOSIS Requests Following is a list of the MOSIS requests. Note that Section 13.3 of the Reference Section contains templates of these requests, along with special instructions for certain requests. ATTENTION This request brings your message or special project requirement directly to the attention of the MOSIS staff. CANCEL-FABRICATE Request to cancel previously requested fabrication of a project. CANCEL-PROJECT Total withdrawal of a project. DELETE-CIF Deletion of last CIF file submitted for a project. END Termination of all requests in a message. FABRICATE Request to fabricate a project. FOUNDRY This option allows you to choose a specific fabricator. INFORMATION Request for information on MOSIS procedures and documents. LIBRARIES Request for cells and/or documentation from MOSIS libraries. NEW-PROJECT Request for creation of a new project. OPTIONS Yes/No options for sharing a chip and requesting a substrate. If you use the SHARE parameter, your chip will be packaged with other projects and the standard quantity divided by the number of projects (the default is NOSHARE). If you request SUBSTRATE (default is NOSUBTRATE), you are requesting that MOSIS include a subtrate connection on the standard pin for that package. QUANTITY Used only to order MORE than the minimum number of parts (see the sample Price Schedule on page 80 for minimum quantities per technology). REPORT User report on the performance of fabricated project(s). STATUS Request for project status. SUBMIT This request ONLY checks the syntax (validity) of a CIF file. UPDATE Modification of project parameters. 4.5.1. Standard Submissions The standard submission style includes three templates: NEW-PROJECT, SUBMIT, and FABRICATE. It is possible to expedite submission by combining a few steps (One-Step Submission), and it is sometimes necessary to fragment large CIF files (N-Step Submission). These are reviewed in Section 13.3 of the Reference Section. 4.5.2. Avoiding Delays Accurate syntax is very important in avoiding error and delay in project submission and in all communication with MOSIS. Remember also that common network problems can cause your project to be received too late for inclusion on the desired run. DO NOT wait until the last minute to submit your project, since this will increase the probability that you won't make the run. Use the MOSIS mail system to make sure that you have the most up-to-date copies of important documents, e.g., the fabrication schedule. 4.6. For More Information Check Reference Section Section 13.3 of the Reference Section contains sample MOSIS request templates and defines the request parameters and their usage. Index MOSIS Command Language 23 Request messages 23 Table of Contents 4. The MOSIS Mail System 23 4.1. Introduction 23 4.2. Accessing MOSIS 23 4.2.1. First Message 23 4.3. Request Message Format 23 4.3.1. Three Fields 23 4.3.2. Keep in Mind 23 4.3.3. Net-Address Parameter 23 4.4. Project Submission Sequence 23 4.5. List of MOSIS Requests 26 4.5.1. Standard Submissions 26 4.5.2. Avoiding Delays 26 4.6. For More Information 26 Index 27