Synthesizing the individual modules of OpensparcT1 - RSYN

 
rsyn compiles all the files using design compiler. The default library used is lsi_10k.db
  1. Open Design and verification guide
  2. In the quick start section 1.3.1 follow unzip and untar commands
  3. cd to the folder untared
  4. Open the OpenSPARC.cshrc script
  5. Edit the document to set up the environment for openSPARC.cshrc
  6. synopsys libraries - /opt/synopsys/syn
  7. sparcos5 libraries -
  8. I was not able to find the libraries at the place mentioned in the document so I used to locate command to locate sparcos5 libraries
  9. locate sparcOS5
  10. source the .tcshrc_synopsys file (it contains the license file in my case)
  11. source OpenSPARCT1.cshrc file
  12. rsyn -all
If everything runs well you can find
  1. In the folder of every component (analog/*, ccx/* etc) you can find a folder called synopsys
  2. Inside that folder you will have log files for commands and design compiler
  3. A gate folder which contains the compiled, flattened and hierarchical netlist
  4. A log folder which contains the area report for that cell
ERRORS:
Runs well till the module ctu is being synthesized
Abort at 51
Fatal: Internal system error, cannot recover.

Googled this error and found

He says
“I sorted this error it has to do with the fact that the read_file function in DC "Cannot pass parameters (must use directives in HDL)" as documented in table 6-2 of this pdf file http://www.vlsiip.com/dc_shell/dcug_6.pdf this means that the scripts for JBI and CTU must be edited. So with the CTU module the file ctu_revision.v has to be excluded from the "rtl_files" list at the top of the user_cfg.scr script (found in... /design/sys/iop/ctu/synopsys/script directory) and the following lines added at the bottom of the script:

read_file -format verilog -define RUNDC $dv_root/design/sys/iop/ctu/rtl/ctu_jtag_id.v
analyze -format verilog $dv_root/design/sys/iop/ctu/rtl/ctu_jtag_id.v
elaborate ctu_jtag_id

read_file -format verilog -define RUNDC $dv_root/design/sys/iop/ctu/rtl/ctu_mask_id.v
analyze -format verilog $dv_root/design/sys/iop/ctu/rtl/ctu_mask_id.v
elaborate ctu_mask_id

read_file -format verilog -define RUNDC $dv_root/design/sys/iop/ctu/rtl/ctu_revision.v
analyze -format verilog $dv_root/design/sys/iop/ctu/rtl/ctu_revision.v
elaborate ctu_revision ”
Works you need to do the same for more than one file . The files that fail need to be analyzed and elaborated. See appendix for sample user_cfg.scr file for ctu.
Everytime it fails, I go to the filename.log file in /design/sys/iop/ctu/synopsys and look at the last file that is executed. I then remove that line form the script file and added it at the end of the script in the format mentioned above.

Have fun,
Abishek

Comments

Post a Comment

Popular posts from this blog

Setting up atalanta ATPG to work on Linux

Atalanta is an ATPG tool that is used to generate test patterns for combinational circuits. atalanta is a windows executable file. I am using Atalanta ATPG tool to generate the test patterns required for generating the Transition fault Test patterns RUNNING ATALANTA (LINUX) You need to have WINE installed to run windows executable binary. Created a symbolic link in the usr/bin to the atalanta.exe, name of the link s atalanta. (not necessary if you do not have root privilages) chmod u+x /place/atalanta/atalanta.exe cd /usr/bin sudo ln -s /place/atalanta/atalanta.exe ./atalanta COMMAND TO RUN ATALANTA atalanta [option] filename //put this in a shell script
Read more

Sparse matrix - 3 tuple representation

//program to 3-tuple representation #include<stdio.h> #include<unistd.h> #define SIZE 3000; void main() { int a[5][5],row,columns,i,j; printf("Enter the order of the matrix(5*5)"); scanf("%d %d",&row,&columns); printf("Enter the element of the matrix\n"); for(i=0;i<row;i++) for(j=0;j<columns;j++) { scanf("%d", &a[i][j]); } printf("3-tuple representation"); for(i=0;i<row;i++) for(j=0;j<columns;j++) { if(a[i][j]!=0) { printf("%d %d %d", (i+1),(j+1),a[i][j]); } } getchar(); }
Read more

Generating 16k ROM using Xilinx IP COREGEN and simulating it in modelsim

The instruction ROM is an IP Core. so before interfacing with the open8, it has to be generated. The method of generating and simulating a ROM Xilinx IP Core is described here. FIND ALL THE FILES HERE 1. app.coe (the initialization file) 2. rom_16k_core.vhd 3. rom_16k_core.vho 4. rom_16k_core.xco 5. top_level.vhd 6. do_memgen.do Creation of the ROM Xilinx 10.1 1. open ISE 2. create a new project 3. tools -> core generator(12.1) (or right click on the device and add a new file 10.1) 4. In the IP catalog -> Memory and storage elements -> RAM and ROM 5. double click on block memory generator, A new window opens 6. In the new window select single port ROM click next, Write first mode 7. Select Read Width = 8 and Read Depth = 16384 for 16K ROM -> next 8. The output ports are unregistered, load initialization COE if required -> next 9. No need to use the Reset pin -> next 10. Generate. (takes a little time then shows successfully generated) This...
Read more