Errors while running simulation

0

I am getting the following errors, while trying to simulate my design with AWS shell. It seems like the arch_package, proj_package declaration is missing. Where are they supposed to be declared. I already checked the the init.tcl file is being sourced and it contains the following lines:

set AWSINSTALL "C:/AWS_Repo/aws-fpga"
source $AWSINSTALL/hdk/common/shell_v04261818/hlx/hlx_setup.tcl

Errors from the log:

INFO: [VRFC 10-2263] Analyzing SystemVerilog file "C:/AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_rdimm_wrapper/ddr4_db_delay_model.sv" into library xil_defaultlib
INFO: [VRFC 10-311] analyzing module ddr4_db_delay_model
INFO: [VRFC 10-2263] Analyzing SystemVerilog file "C:/AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/ddr4_model.sv" into library xil_defaultlib
ERROR: [VRFC 10-91] arch_package is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTable.sv:5]
INFO: [VRFC 10-311] analyzing module StateTable
ERROR: [VRFC 10-91] proj_package is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:1553]
ERROR: [VRFC 10-91] proj_package is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:1554]
ERROR: [VRFC 10-91] proj_package is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:2950]
ERROR: [VRFC 10-91] MAX_ROW_ADDR_BITS is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:14]
ERROR: [VRFC 10-1775] range must be bounded by constant expressions [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:14]
ERROR: [VRFC 10-91] MAX_RANKS is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:15]
ERROR: [VRFC 10-1775] range must be bounded by constant expressions [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:15]
ERROR: [VRFC 10-91] MAX_RANKS is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:27]
ERROR: [VRFC 10-1775] range must be bounded by constant expressions [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:27]
ERROR: [VRFC 10-91] MAX_RANKS is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:28]
ERROR: [VRFC 10-1775] range must be bounded by constant expressions [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:28]
ERROR: [VRFC 10-91] MAX_RANKS is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:29]
ERROR: [VRFC 10-1775] range must be bounded by constant expressions [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:29]
ERROR: [VRFC 10-91] MAX_RANKS is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:30]
ERROR: [VRFC 10-1775] range must be bounded by constant expressions [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:30]
ERROR: [VRFC 10-91] MAX_RANKS is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:31]
ERROR: [VRFC 10-1775] range must be bounded by constant expressions [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:31]
ERROR: [VRFC 10-91] MAX_RANKS is not declared [../../../../../../../../../../../../AWS_Repo/aws-fpga/hdk/common/verif/models/ddr4_model/StateTableCore.sv:32]
INFO: [#UNDEF] Sorry, too many errors..

asked 5 years ago252 views
1 Answer
0

Sorry, repeat post. This looks like an issue if current version of shell is used with 2017.4

answered 5 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions