3. Submitting Your Design to MOSIS DESIGN SUBMISSION - VIA MAGNETIC TAPE OR ELECTRONIC MAIL 3.1. Introduction This chapter describes how to submit your layout geometry for a MOSIS fabrication run. If you are not on an electronic network, you need to put your geometry on magnetic tape and mail it to MOSIS with a Project Submission Form containing important project information. (A sample of this form is in the back pocket of this manual.) To obtain an up-to-date form, contact the Documentation Coordinator (see page 13). If you are sending your files over an electronic mail network, you need to read Section 3.3, Network Users, which describes how to send files to MOSIS; this should be read in conjunction with Chapter 4, The MOSIS Mail System. Whether you are sending project design files to MOSIS on a magnetic tape or over the network, the list of MOSIS Command Language parameters in the Reference Section (see page 113) can be used as a checklist to make sure that you have taken care of all aspects of design submission. You should also review whether you have any special handling or bonding requests. It is important to consider these packaging requirements before project submittal. 3.2. Offline Users MOSIS accepts designs submitted on magnetic tape in GDSII, CIF (Caltech Intermediate Form), or MEBES format. Make sure your tape has a physical label on the outside. This label should include your name, affiliation, project name, and Project-ID, as well as technology (e.g., CBPM, SCP, SCN, SCE). Please review the technologies in Chapter 6. Fill out the Project Submission Form and have it signed by your authorized representative. Mail the labeled tape, Project Submission Form, and bonding diagram (if applicable) to: USC/Information Sciences Institute The MOSIS Service 4676 Admiralty Way Marina del Rey, CA 90292-6695 Attn: MOSIS Liaison 1. If you are using a MOSIS Standard Frame: MOSIS will generate a bonding diagram for you. You will need to indicate the Standard Frame name, e.g., 28PC23x34, on the Project Submission Form. (See Chapter 9 for a discussion of Standard and Nonstandard Frames.) 2. If you are using a Nonstandard Frame: You MUST submit a bonding diagram with your tape so that MOSIS knows exactly how you want your chip bonded. See sample bonding diagrams on page 69. Sample bonding diagram forms are in the back pocket of this manual. 3.3. Network Users MOSIS accepts designs from network users in CIF format. Project submission is accomplished through the MOSIS automatic message system, often in conjunction with FTP (File Transfer Protocol). All necessary files and information MUST be received and processed by MOSIS by 7:00 a.m. on the day of run closing. With this deadline in mind, it is important to consider your mode of file transfer and the particular characteristics of your network. MOSIS is on the Internet (previously called the ARPANET) and can be accessed by many other networks. The MOSIS automatic message software is called the MOSIS Command Language system. This software allows MOSIS to handle large amounts of user mail and to begin to process projects for fabrication. The next chapter in this manual describes in detail how to use this software to communicate with MOSIS. As a MOSIS user you need a mailbox on either the Internet or a system with a mail relay to the Internet. This chapter will discuss which network you are on and how to find a network path to MOSIS (see the illustration at the end of this chapter). 3.3.1. MOSIS and Computer Networks Some of the major networks that have access to the Internet through mail relays are listed below. - INTERNET: This network is sponsored by DARPA (the Defense Advanced Research Projects Agency) and NSF (the National Science Foundation) and has been in operation since 1969. Many government agencies, universities, and commercial companies are on this network, previously referred to as the ARPANET. Many individual networks are connected by gateways to form the Internet (e.g., MILNET, SATNET, WBNET, and many university networks). The network is managed by SRI Network Information Center. - BITNET: This network is sponsored by a consortium of universities and is managed by EDUCOM. - CSNET: This network is sponsored by a consortium of universities and contains university, industrial, and government research organizations. CSNET is managed by UCAR. - UUCP: This is a decentralized network system. It relies on phone calls and modems to communicate between sites. It is free and has mail relays to most of the other networks; however, mail transfer is often very slow, taking up to two or three days. 3.3.2. Finding the Network Path to MOSIS If you have mail relay access to the Internet, you must find out which network your computer is on and the mail path from it to MOSIS. Which network am I on? If your machine is not on a site on any of the above-mentioned networks, your machine may be a site on a local network. One of the sites on this local network may be already serving as a gateway to a remote network. To find out this information, contact your system administrator. Correct pathname MOSIS is on the Internet. If you have access to the Internet, UUCP, CSNET, or BITNET, you can send mail to MOSIS through one of the following paths: Network Network Address INTERNET mosis@mosis.edu BITNET mosis%mosis.edu@cunyvm.cuny.edu CSNET mosis%mosis.edu@relay.cs.net UUCP ...!{harvard,rutgers,seismo,sun,uiucdcs,talcott}mosis.edu!mosis (where"..." is your path to the computer listed after the "!".) 3.3.3. Network Contacts Network Network Contacts INTERNET Network mail: nic@sri-nic.arpa Tel: (800) 235-3155 BITNET Network mail: info%bitnic.bitnet@cunyvm.cuny.edu Tel: (609) 520-3377 (EDUCOM) CSNET Network mail: cic@sh.cs.net (CSNET Coordination and Information Center - CIC) Tel: (617) 497-2777 UUCP Network mail: Rick@uunet.uu.net Tel: (703) 276-7900 3.3.4. Sending the Message - Mail Size Limits and Internet Address Syntax At this time, no single item of mail having more than 900,000 characters can be sent to or from MOSIS. However, this limit does not apply to the transfer of CIF files via the CIF-FTP-Path specification. The Internet mail syntax has certain requirements that must be followed. Two of the main points are listed below: 1. The address parameter must fit on one line of less than 200 characters; address "folding" is not supported. 2. The special characters , , and may not be part of the address(es) even if part of a quoted string or quoted pair. For more details on syntax specifications, see the section at the end of this chapter entitled For More Information and note the article by David Crocker, "Standard for the Format of ARPA Internet Text Messages," which is available from the Network Information Center (NIC). If you are not directly connected to the Internet, the net-address given must be the name of the mailbox on the Internet host that acts as the mail relay between your network and the Internet. Although net-address syntax may vary in the message header, and according to your particular network path, the body of a request message (i.e., syntax) should be the same on every network. MOSIS has an automated information retrieval service for communicating with MOSIS users. This service allows you to request information on various topics, submit your project, and receive status reports on your design submission. This service uses a syntax called the MOSIS Command Language and is covered in detail in Chapter 4. The MOSIS Command Language software will read the address parameter specification and automatically use it as the reply path. 3.3.5. Reply Paths Check the following table to find the path you need to specify to enable MOSIS to reply to you. Please note that Internet addresses have a domain extension, e.g., .EDU, which indicates a domain or group of users with a similar affiliation (in this case, EDUCATION). Network Net-address INTERNET user@site.arpa (or other domain extension, e.g., .EDU) BITNET user%site.bitnet@cunyvm.cuny.edu CSNET user%site.csnet@relay.cs.net UUCP site3!site2!site1!user@{harvard,rutgers,seismo,sun,uiucdcs,talco Rutgers(= RED.RUTGERS.EDU) and Seismo(= SEISMO.CSS.GOV) are the most popular UUCP relays. UUCP is the most complex of the nets and the user is more responsible for knowing his/her net paths to and from the Internet. Because networks are dynamic and also not foolproof, it is important to give yourself plenty of time when submitting geometry to a MOSIS run. Avoid sending very large files to MOSIS at the last minute. If there are network problems, you will need time to resend your design and still make the run schedule deadline. 3.4. For More Information DDN New User Guide, December 1985. NIC 50001, DDN Network Information Center, (800) 235-3155. Abrams, Marshall, and Ira W. Cotton, Computer Networks. IEEE Computer Society, 1987. (IEEE order no. 568.) Quarterman, John S., and Josiah C. Hoskins, "Notable Computer Network Communications of the ACM, vol. 29, no. 10, October 1986. Postel, Jon, Simple Mail Transfer Protocol. *RFC 821, SRI Network Information Center. Crocker, David H., Standard for the Format of ARPA Internet Text Mess *RFC 822, SRI Network Information Center. * Requests for RFCs should be addressed to NIC@SRI-NIC.ARPA or call 800-235-3155. . . . Index Bonding diagram 16 CIF 15, 16 Computer networks 16 Electronic network 15 FTP 16 Internet 16 Mail size limits 17 MOSIS Command Language 16, 17 Nonstandard Frame 16 Project Submission Form 15 Standard Frame 16 Table of Contents 3. Submitting Your Design to MOSIS 15 3.1. Introduction 15 3.2. Offline Users 15 3.3. Network Users 16 3.3.1. MOSIS and Computer Networks 16 3.3.2. Finding the Network Path to MOSIS 16 3.3.3. Network Contacts 17 3.3.4. Sending the Message - Mail Size Limits and Internet Address 17 Syntax 3.3.5. Reply Paths 18 3.4. For More Information 18 Index 23