addExternalIOInterface

Class: hdlcoder.Board
Package: hdlcoder

Define external IO interface for board object

Syntax

addExternalIOInterface('InterfaceID',interfacename,'InterfaceType',interfacetype,'PortName',portname,'PortWidth',portwidth,'FPGAPin',pins,'IOPadConstraint',constraints)

Description

addExternalIOInterface('InterfaceID',interfacename,'InterfaceType',interfacetype,'PortName',portname,'PortWidth',portwidth,'FPGAPin',pins,'IOPadConstraint',constraints) adds an external IO interface to an hdlcoder.Board object. You can add multiple external IO interfaces to your board object.

Use this method if your board has more than one external interface, or if you want to be able to predefine FPGA pin names for mapping from the HDL Workflow Advisor.

Input Arguments

expand all

Interface name, specified as a character vector. In the HDL Workflow Advisor, this name appears in the Target Platform Interfaces dropdown list.

Example: 'LEDs General Purpose'

Interface direction, specified as a character vector. In the HDL Workflow Advisor, when you specify a target interface for each of your DUT ports, this external IO interface is available only for ports with a matching direction.

For example, if you set interfacetype to 'OUT', this external IO interface is available only for Outport DUT ports.

Example: 'OUT'

Board top-level port name, specified as a character vector.

Example: 'GPLEDs'

Port bit width, specified as a positive integer.

Example: 4

FPGA pin names, specified as a cell array of character vectors.

Example: {'H18','AA14','AA13','AB15'}

IO pad constraints, specified as a cell array of character vectors.

Example: {'IOSTANDARD = LVCMOS25'}

Example: {'IOSTANDARD = LVCMOS25','SLEW = SLOW'}

Tips

  • For details about the external IO interface ports, pins, and constraints for your board, view the board documentation.

Introduced in R2015a