adc-verification-v5.0-001.tar

======================================================================= Reference Design Database README.txt DATABASE NAME: saradc, saradcII DATABASE RELEASE: v3.0-001 ======================================================================= This reference design database is composed of the following: * AMS Reference Flow Documentation * Reference Design Database (RDK) Example NOTE: The required product software IS NOT included in this software distribution. It must be downloaded separately from http://downloads.cadence.com TABLE OF CONTENTS ----------------- 1. DESIGN DESCRIPTION 2. RECOMMENDED SOFTWARE CONFIGURATION 3. INSTALLATION AND CONFIGURATION INSTRUCTIONS 4. USAGE INSTRUCTIONS 5. DATABASE CONTENTS ======================================================================= 1. DESIGN DESCRIPTION ======================================================================= ADC Verification RAK Database Top-Level Testbench: Library Name: saradc Primary Cell Names: 10Bit_ADC_TB_new 10Bit_ADC_TB_noise 10Bit_ADC_Run_Plan 10Bit_capdac_TB_new clockPhaseGenerator_TB_new clockPhaseGenerator_dc2dc_TB_new comparator_noise_TB_new comparator_offset_TB_new comparator_tran_noise_TB ======================================================================= 2. RECOMMENDED SOFTWARE CONFIGURATION ======================================================================= This database has been tested using the following tool configuration: PRODUCT VERSION* TYPE ---------- ------------ ------ IC IC6.1.8-64b.83 ISR SPECTRE 18.1.0.235.isr3 ISR *NOTE: If the specified ISR is no longer available, use a more recent software version. ======================================================================= 3. DATABASE INSTALLATION AND CONFIGURATION INSTRUCTIONS ======================================================================= Approximate Installed Disk Space Requirements --------------------------------------------- Representative Design Database: 500 MB There are 2 steps that must be completed before the database is ready for use: 1. Installation 2. Configuration Two configuration methods are supported - Single User & Multiple User. A. Single User - User works directly inside of the installed database directory. User has write access to all database files and none of the files are shared with any other users. To restore the database to its original state, one is generally required to repeat the installation and configuration steps. B. Multiple User - In this mode, the database is installed in a central location. Each user works from a separate project workspace derived from the main installation directory. Users share reference libraries and other common files. This reduces the overall storage space requirements. It also allows the site configuration setup to be shared and thus reducing system administration. It also provides a more realistic user environment by providing users with write access to the design files while providing more restricted read-only access for the foundry-supplied PDK or technology files and reference libraries. Finally, restoring the workspace to its original state can be done much faster than repeating the full installation and configuration required for the single user. I. Installation =============== I.1. Move the downloaded tar file (adc_verification_v3.0_001.tgz) containing the database to the desired installation directory and inflate. tar zxf adc_verification_v3.0_001.tgz A folder called "adc_verification_v3.0_001" should now be present in the working directory. II. Configuration ================= II.1 Configuring the Database for Single or Multiple Users ---------------------------------------------------------- The database can be configured for single or multiple users. With the single user setup, workshops are executed from directly inside the installed database. With the multi-user setup, the database is installed in a central location and the end users create work areas containing pointers to the shared installation. The advantages of the the multi-user setup were discussed earlier. II.2 Single User Database Configuration ----------------------------------------- 1. Edit the following "project.cshrc" file(s): adc_verification_v3.0_001/WORK/saradc/project.cshrc These file(s) contain environment variables setup which must be configured in order to reflect your local software installation and licensing. II.3 Multiple User Database Configuration ----------------------------------------- After inflating the tar image there are two site-specific files that must be configured for your local site. These files define the local Cadence software product installation paths and the environment variables required for the Cadence license setup, etc. adc_verification_v3.0_001/setup/site/tools.reg (local site tool installations) adc_verification_v3.0_001/setup/site/setup.csh (local site environment settings) These files are used to create a `project.cshrc' file used to configure your UNIX environment prior to starting the design tools. You may choose to skip this step. If you do, then you will have to either setup your environment manually or edit the resulting project.cshrc file II.3.a Configuring adc_verification_v3.0_001/setup/site/tools.reg ------------------------------------------------------------------------- This file defines the installation locations for all the software packages used in this reference design. Edit this file and replace the default installation paths with the actual locations used at your site. The recommended software versions are listed in the table above. II.3.b Configuring adc_verification_v3.0_001/setup/site/setup.csh ------------------------------------------------------------------------- This file contains site-specific environment setup such as the locations of the software product licenses. These setup instructions enable the database installation to be shared among all users at the same site. With this method, a single person such as the site administrator installs and configures the database as per the instructions given in the Installation step above, The actual users then point to this central installation and use a script to create a private workspace by executing the following steps: 1. Change directories to where the local project workspace directory is to be created. Example: cd ~/ams_flow_projects 2. Set the following shell environment variable to point to the database installation directory: setenv FLOW_HOME <install_dir>/adc_verification_v3.0_001 3. Add the $FLOW_HOME/bin directory to your shell $PATH: set path = ($FLOW_HOME/bin $path ) 4. Execute the following command: ckCreateWorkspace <my_workspace_dir> ...where <my_workspace_dir> is the name of the workspace directory to be created. The workspace directory should now be created and ready for use. ======================================================================= 4. USAGE INSTRUCTIONS ======================================================================= Tools are meant to be launched from one of the "work area" directories located under the WORK folder. Follow the instructions returned by the ckCreateWorkspace script (if using). Otherwise, follow the instructions given below 1. Change directories to one of the designated work area directories: cd <my_workspace_dir>/WORK/saradc List of Flow Workareas: WORKAREA NAME SUB-FLOW ------------- -------- WORK/saradc All 2. Source the project.cshrc file containing the environment setup. source project.cshrc 3. Launch the required tool executable (e.g virtuoso) virtuoso -log CDS.log & ======================================================================= 5. DATABASE DIRECTORY STRUCTURE =====================================================