Article ID: 000074549 Content Type: Troubleshooting Last Reviewed: 09/11/2012

Why are mismatches reported in the HardCopy Companion Revision Comparison Report related to the OUTPUT_IO_TIMING_NEAR_END_VMEAS and OUTPUT_IO_TIMING_FAR_END_VMEAS assignments?

Environment

BUILT IN - ARTICLE INTRO SECOND COMPONENT
Description

Due to a problem in the Quartus® II software version 10.1 SP1 or earlier, if you target HardCopy® IV device, you may see mismatches related to the OUTPUT_IO_TIMING_NEAR_END_VMEAS and OUTPUT_IO_TIMING_FAR_END_VMEAS assignments. This is because the assignments are not migrated correctly to the HardCopy revision.

To work around this problem, change the two assingments in the HardCopy revision Quartus II Settings File (.qsf) manually after creating or overwriting the Hardcopy companion revision, but before compiling the HardCopy revision.

Original assignments:
set_global_assignment -name OUTPUT_IO_TIMING_NEAR_END_VMEAS "HALF VCCIO"
set_global_assignment -name OUTPUT_IO_TIMING_FAR_END_VMEAS "HALF SIGNAL SWING"

Modified assignments:
set_global_assignment -name OUTPUT_IO_TIMING_NEAR_END_VMEAS "HALF VCCIO" -rise
set_global_assignment -name OUTPUT_IO_TIMING_NEAR_END_VMEAS "HALF VCCIO" -fall
set_global_assignment -name OUTPUT_IO_TIMING_FAR_END_VMEAS "HALF SIGNAL SWING" -rise
set_global_assignment -name OUTPUT_IO_TIMING_FAR_END_VMEAS "HALF SIGNAL SWING" -fall

This problem has been fixed beginning with the Quartus II software version 11.0

Related Products

This article applies to 2 products

HardCopy™ IV E ASIC Devices
HardCopy™ IV GX ASIC Devices