AR# 51351
MIG 7 Series DDR3/DDR2 - "ERROR:HDL Compiler:532 - Index <71> is out of range [63:0] for signals " occurs when using ECC_TEST="ON"
Description
Version Found: MIG 7 Series v1.5
The MIG 7 Series DDR3/DDR2 design includes an ECC Self-Test Functionality controlled by a top-level RTL parameter "ECC_TEST."
By default, MIG sets this parameter to "OFF," which means that the ECC part of the data written to the DRAM array is not visible at the user interface.
This can be problematic for system self-test because there is no way to test the bits in the DRAM array corresponding to the ECC bits.
There is also no way to send errors to test the ECC generation and correction logic.
By setting ECC_TEST to "ON," a DRAM array test mode can be generated.
When the ECC_TEST parameter is "ON," the entire width of the DQ data bus is extended through the read and write buffers in the user interface.
Also, the ECC correct enable is deasserted.
The MIG 7 Series DDR3/DDR2 design includes an ECC Self-Test Functionality controlled by a top-level RTL parameter "ECC_TEST."
By default, MIG sets this parameter to "OFF," which means that the ECC part of the data written to the DRAM array is not visible at the user interface.
This can be problematic for system self-test because there is no way to test the bits in the DRAM array corresponding to the ECC bits.
There is also no way to send errors to test the ECC generation and correction logic.
By setting ECC_TEST to "ON," a DRAM array test mode can be generated.
When the ECC_TEST parameter is "ON," the entire width of the DQ data bus is extended through the read and write buffers in the user interface.
Also, the ECC correct enable is deasserted.
However after manually modifying the MIG design to set ECC_TEST to "ON," the design fails during synthesis with an error similar to the following:
ERROR:HDLCompiler:532 - "\mig_7series_v1_6\user_design\rtl\ip_top\memc_ui_top_std.v" Line 735: Index <71> is out of range [63:0] for signal <wr_data_mask>.
Solution
This error occurs because of an rtl issue where wr_data_mask is not declared with the appropriate width.
To work around this issue, manually change the width of wr_data_mask:
From:
To work around this issue, manually change the width of wr_data_mask:
From:
wr_data_mask [2*nCK_PER_CLK*DATA_WIDTH/8 -1 :0]
To:
wr_data_mask [71 : 0]
Was this Answer Record helpful?
| AR# 51351 | |
|---|---|
| Date | 08/18/2014 |
| Status | Active |
| Type | Known Issues |
| Devices | |
| IP | |