<!--
Template Revision 1.2
 -->
Online version of this manual and other related documents can be found at https://wiki.trenz-electronic.de/display/IP/Trenz+Electronic+IP+Cores

Table of Contents

IP Facts

Introduction

This Trenz Electronic teCORE IP provides a RGPIO (Remote GPIO) Interface to talk to external RGPIO Devices. Convert parallel data bus into 3 wire signal and back to parallel data bus.

IP can be used as Master communicate with external RGPIO devices with Slave interface or as Slave to communicate with external RGPIO devices with Master interface.

Features

  • Master RGPIO
  • Slave RGPIO
  • GPIO Expander
teCORE™ IP Facts Table 
Supported Device FamilyUltrasScale+ Zynq, 7 Series Zynq,UltraScale+ Series, UltraScale Series, 7 Series
Supported User InterfacesCustom
Resources
Special FeaturesRGPIO Master and Slave Controller
Provided with Core
Design FilesVHDL Source Code
Constraint FilesNot provided, depends on module PCB
Example DesignNot Provided
Test BenchNot Provided
Simulation ModelNot Provided
Supported S/W DirverNot Provided
Tested Design Flows
Design Entry

Vivado® Design Suite, IP Integrator

SimulationVivado Simulator
SynthesisVivado Synthesis
Tested Hardware Platforms

Support
Provided by Trenz Electronic GmbH

Overview

This Trenz Electronic teCORE IP provides a RGPIO (Remote GPIO) Interface to talk to external RGPIO Devices over 3 wire

IP can be used as Master communicate with external RGPIO devices with Slave interface or as Slave communicate with external RGPIO devices with Master interface

Feature Summary

Licensing and Ordering Information

This Trenz Electronic teCORE is licensed under MIT License. This IP is included in various Reference Designs or contact Trenz Electronic Support (support[at]trenz-electronic.de) with subject line "[TE-IP-Core Request]" to order this IP-Core.

Product Specification

Performance

Maximum RGPIO output CLK depends on Master and Slave device implementation. In the most cases maximum frequency of 25MHz is allowed.

Resource Utilization

Port Description

RGPIO_EXT External Interface

Communication channel between master and slave interface.


Port NameIODescription
RGPIO_M_CLKoutRGPIO Master Clock
RGPIO_M_RXin

RGPIO Master RXD  

RGPIO_M_TXoutRGPIO Master TXD
Port NameIODescription
RGPIO_S_CLKoutRGPIO Slave Clock
RGPIO_S_RXin

RGPIO Slave RXD  

RGPIO_S_TXoutRGPIO Slave TXD


RGPIO_M_USR Interface

Master user interface to communicate with slave device.

Port NameIODescription
RGPIO_M_OUTout23bit data output to slave device*
RGPIO_M_INin

23bit data input from slave device*

RGPIO_M_RESERVED_OUTout

4bit reserved for future usage

RGPIO_M_RESERVED_INin4bit reserved for future usage
RGPIO_M_SLAVE_ACTIVATION_CODEout4bit activation code from external slave for information only
RGPIO_M_ENABLEinEnable RGPIO communication. High active. Set RGPIO data as valid for Slave. Data will always transmitted, if CLK is available.
RGPIO_M_USRCLKinRGPIO transmission CLK for master and slave
RGPIO_M_RESET_Nin

RGPIO Reset. Low active.

*currently limited to 23 bit to use IP with CPLD implementations of TE Boards. For general usage, this restriction will be removed on future IP update.

RGPIO_S_USR Interface

Slave user interface to communicate with master device.

Port NameIODescription
RGPIO_S_OUTout23bit  data output to master device*
RGPIO_S_INin

23bit data input from master device*

RGPIO_S_RESERVED_OUTout4bit reserved for future usage
RGPIO_S_RESERVED_INin4bit reserved for future usage
RGPIO_S_MASTER_ACTIVATION_CODEout4bit activation code from external master for information only
RGPIO_S_ENABLEDoutInterface status. Indicates RGPIO data are valid.

*currently limited to 23 bit to use IP with CPLD implementations of TE Boards. For general usage, this restriction will be removed on future IP update.

Designing with the Core

This chapter includes guidelines and additional information to facilitate designing with the core.

Design Flow Steps

This chapter describes customizing and generating the core, constraining the core, and the simulation, synthesis and implementation steps that are specific to this IP core. More detailed information about the standard Vivado® design flows and the Vivado IP integrator can be found in the following Vivado Design Suite user guides:

Customizing and Generating the Core

This section includes information about using Xilinx® tools to customize and generate the core in the Vivado Design Suite.


Constraining the Core

This section contains information about constraining the core in the Vivado Design Suite.

Required Constraints

Loc constrains and IO Standard depends on module and usage.

Device, Package, and Speed Grade Selections

This section is not applicable for this IP core.

Clock Frequencies

Maximum RGPIO output CLK depends on Master and Slave device implementation. In the most cases maximum frequency of 25MHz is always allowed.

Clock Management

This section is not applicable for this IP core.

Clock Placement

This section is not applicable for this IP core.

Banking

This section is not applicable for this IP core.

Transceiver Placement

This section is not applicable for this IP core.

I/O Standard and Placement

This section is not applicable for this IP core.

Simulation

This core does not support simulation.

Synthesis and Implementation

This section contains information about synthesis and implementation in the Vivado Design Suite. For details about synthesis and implementation, see the Vivado Design Suite User Guide:

Example Design

There is no example Design for this IP core release.


Use Master Slave loopback over RGPIO_EXT interface to test IP Master and Slave Interface together.

Vivado Block Design:

VIO HW Manager:

Test Bench

There is no test bench for this IP core release.

Appx. A: Change History and Legal Notices

Document Change History

DateDocument RevisionIP RevisionAuthorsDescription

v1.0

  • initial release with Vivado 2017.4

Legal Notices