Logic Design for Array-Based Circuits

by Donnamaie E. White

Copyright © 1996, 2001, 2002, 2008, 2016 Donnamaie E. White, WhitePubs Enterprises, Inc.

 

Design Submission

Last Edit September 2, 2001


On the completion of the design verificaton and simulation for the circuit, the design submission package is assembled. This package must pass through a design acceptance review before the array vendor will accept it.

The requirement of design submission is specific - provide the array vendor with sufficient infoprmation to be able to evaluate the design, reproduce the simulation on their own internal systems, place and route the circuit, and produce Back-Annotated simulations that meet the customer's requirements.

Design submission requirements vary widely in their specific forms and supplemental material. As an added support feature, AMCC created AMCCSUBMIT - a design submission documentation program that prompts for design validation questions and for information required to document submitted simulation files. To better discuss this process, the following is the current AMCC design submission document, referencing AMCCSUMBIT and the validation questions.

Regardless of the forms it may take or be required to be in, the same basic information is required for any design submission. Variations occur when the array vendor is contracted to perform some or all of the design process to the customer's specifications.


Case Study: AMCC Design Submission

Submitting A Circuit Design To AMCC (1990)

The following document has been designed to ensure the AMCC customer, of a successful transition from concept to finished part. It is a summary of the items required for the submission of a BiCMOS or bipolar array-based circuit design to AMCC when:

  • the schematic capure and simulation vector generation has been performed by the customer;
  • the design entry is via a description language or netlist and simulation vector generation has been performed by the customer.

The items described herein must be submitted to AMCC for use in the acceptance design review prior to committing the design to layout. These are the critical information transfers which, if not completed, may delay the acceptance of the circuit.

Schematics are to be prepared following AMCC schematic conventions. Refer to the design manual for further information. Sections provide a detailed description of the AMCC rules for both EWS-generated and non-EWS-generated schematics.

A design cannot be processed without the required test vectors. Functional simulation and at-speed simulation or timing verification are required prior to releasing a design to layout. Parametric simulation may also be required. AC Tests are optional. For information on the test vector requirements and simulation procedures, refer to Volume II, Section 4, "Vector Submission Rules and Guidelines".

  • AMCC Array Design Submission With AMCCSUBMIT

    AMCCSUBMIT must be run and the questions answered. It will produce a summary of the documentation required for a successful design submission.

    Where information is requested that is not available due to the type of design submission and the contract, indicate why the information is not being supplied.

  • AMCC Assigned Circuit Name (required identification)

  • AMCC PRODUCT_NAME

    When AMCC has received a purchase order for a circuit, AMCC assigns a code name (a.k.a circuit name, product name) to protect the proprietary nature of the circuit. This code name should appear on the submission document and on all hardcopy documents as a single point of reference. It should be attached to the schematic chip macro as the PRODUCT_NAME parameter.

    If no such name assignment exists, use the first 4-6 letters of the company name as the code name ID.

  • AMCC Assigned DEVICE_NUMBER [may use default]

    Assigned with the PRODUCT_NAME, the DEVICE_NUMBER serves to identify the individual circuit. It may be defaulted if no number has been assigned.

Copyright © 1996, 2001, 2002, 2008, 2016 Donnamaie E. White , WhitePubs Enterprises, Inc.
For problems or questions on these pages, contact [email protected]