What's new in IO Checker™ 4.0

Signal view

The HDL view has been transformed into the Signal view. The user can modify all properties of the signals (like name, range, direction, location constraint) and add or delete signals. The data in the Signal view can be:

The signals in this view can be edited by the user and than be used to: The new approach allows you to adjust / modify imported data before it is used.

CSV import

The HDL CSV import and FPGA CSV data import are replaced by a single CSV import that will import data into the Signal view. The import will merge the data found in the file with data already present in the Signal view. Signals already present in the view but not in the import are not removed. The dialog has a ‘Determine import settings‘ button to automatically determine the comment character, column separator and FPGA pin name.
CSV Import dialog
CSV Import dialog

Verification

The verification is now task driven instead of source driving. The new approach makes it easier to perform a specific verification task. The verification mode specified in the wizard will be used as the default mode during verification.

The individual verification tasks can also be started from the Verify menu.
Verification wizard
Verification wizard dialog

Matching rules

IO Checker matching rules
IO Checker matching rules

The matching rules dialog has an extra checkbox, that allows you to use the derived PCB signal name in the matching rules. This is very useful when signals are tied to ground using a resistor, and the direct signal name is a system generated name. In the example below pin AT14 is functionally connected ground (over a resistor). Using the checkbox ‘derived’ in the Rules dialog this can automatically be verified.

Use of derived netname
Use of derived netname (direct pulldown)

FPGA pin file processing

Several improvements were made to the pin file readers:

Lattice

Extract vref pin data from the pin layout file.

Intel (Altera)

Support for default IO standard (STRATIX_DEVICE_IO_STANDARD) in the constraint file.

Xilinx

Unused signals in Xilinx are now reported in the pin view as <UNUSED> instead of using the pin functional name (like <IO_L11N_6>). This allows the rule engine to create rules for them.

Microsemi

Improved recognition of drive strength and slew rate.

Device Support

The following device families (or additional devices) have been added:
Home dot Company dot Products dot Sales dot Support dot HDL Corner dot Site Map
Copyright © 2004 - 2019 HDL Works