compile EDIF(generated by Celoxica DK4) using Quartus II

Hi all,

I got an error when I compile the EDIF file generated by Celoxica DK4. The code is written in Handel-C. I add the EDIF file and the TCL file generated by DK4 to the project, the error is following: Error: Node "B57_testforQuartusII_hcc_8_DTYPE0IR" is missing source

the TCL file is following:

############################################################################## # # Assignment and Constraints Quartus TCL script for design N:\myhome \my stuff\handel-c\test\testforQuartusII\EDIF\testforQuartusII.edf # # Generated by Celoxica Hardware Compiler (Version 3.5.3555.63181) # Timestamp 2007 4 17 15 54 52 # ##############################################################################

# Set family and part set_global_assignment -name FAMILY "STRATIX II" set_global_assignment -name DEVICE "ep2s15f484c5"

# Set compilation options set_global_assignment -name ALLOW_POWER_UP_DONT_CARE Off set_global_assignment -name AUTO_PACKED_REGISTERS Normal

############################### IO assignments ###############################

set_instance_assignment -name IO_STANDARD "LVTTL" -to PADIN_testforQuartusII_hcc_ClockInPin set_instance_assignment -name IO_STANDARD "LVTTL" -to PADIN_testforQuartusII_hcc_Read_read_4 set_instance_assignment -name IO_STANDARD "LVTTL" -to PADIN_testforQuartusII_hcc_Read_read_3 set_instance_assignment -name IO_STANDARD "LVTTL" -to PADIN_testforQuartusII_hcc_Read_read_2 set_instance_assignment -name IO_STANDARD "LVTTL" -to PADIN_testforQuartusII_hcc_Read_read_1 set_instance_assignment -name IO_STANDARD "LVTTL" -to PADIN_testforQuartusII_hcc_Read_read_0 set_instance_assignment -name IO_STANDARD "LVTTL" -to PADOUT_testforQuartusII_hcc_Write_write_4 set_instance_assignment -name IO_STANDARD "LVTTL" -to PADOUT_testforQuartusII_hcc_Write_write_3 set_instance_assignment -name IO_STANDARD "LVTTL" -to PADOUT_testforQuartusII_hcc_Write_write_2 set_instance_assignment -name IO_STANDARD "LVTTL" -to PADOUT_testforQuartusII_hcc_Write_write_1 set_instance_assignment -name IO_STANDARD "LVTTL" -to PADOUT_testforQuartusII_hcc_Write_write_0

############################# Timing requirements ############################

set_instance_assignment -name X_ON_VIOLATION_OPTION OFF -to B48_testforQuartusII_hcc_8_DTYPE0IR set_instance_assignment -name X_ON_VIOLATION_OPTION OFF -to B49_testforQuartusII_hcc_8_DTYPE0IR set_instance_assignment -name X_ON_VIOLATION_OPTION OFF -to B50_testforQuartusII_hcc_8_DTYPE0IR set_instance_assignment -name X_ON_VIOLATION_OPTION OFF -to B51_testforQuartusII_hcc_8_DTYPE0IR set_instance_assignment -name X_ON_VIOLATION_OPTION OFF -to B52_testforQuartusII_hcc_8_DTYPE0IR set_instance_assignment -name X_ON_VIOLATION_OPTION OFF -to B53_testforQuartusII_hcc_8_DTYPE0IR set_instance_assignment -name X_ON_VIOLATION_OPTION OFF -to B54_testforQuartusII_hcc_8_DTYPE0IR set_instance_assignment -name X_ON_VIOLATION_OPTION OFF -to B55_testforQuartusII_hcc_8_DTYPE0IR set_instance_assignment -name X_ON_VIOLATION_OPTION OFF -to B56_testforQuartusII_hcc_8_DTYPE0IR set_instance_assignment -name X_ON_VIOLATION_OPTION OFF -to B57_testforQuartusII_hcc_8_DTYPE0IR

The EDIF file generated by DK4 is working fine with Xillinx ISE. Is there any special requirement for compiling EDIF using QuartusII?

Many Thanks, Ying

Reply to
lyfieryflame
Loading thread data ...

An EDIF file is a device netlist. There should be two of them if you want to try both X and A.

-- Mike Treseler

Reply to
Mike Treseler

Unless the netlist is incorrect i.e. there is truly a net missing a source, it is possible that the strings used to identify VCC and GND signals have not been specified. To specify the VCC and GND signals that is used in the EDIF file do the following:

  1. Go to Assignments->EDA Tool Settings->Design Entry/Synthesis
  2. Set Tool name to Custom
  3. Make Sure Tool is EDIF
  4. Set the VCC and GND values as you see them in the EDIF file being used.

Hope this helps, Subroto Datta Altera Corp.

Reply to
Subroto Datta

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.