You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »



Module TE0802

Figure 1: Module TE0802

1 Overview


This guide shows the main components of the TE0802 module and introduces the available script-based reference design to get the board up and running.

1.1 Prerequisites

HardwareSoftware
  • TE00802 module
  • Micro-USB cable

1.2 Getting Started with the TE0802

The module TE00802 has a Xilinx Spartan-7 FPGA onboard that allows you to create extensive digital hardware and software designs.

Most of the FPGA IOs are spread around the carrier. The TE0717 is assembled with HyperRAM (64 Mbit), QSPI non-volatile Flash memory (64 Mbit) and plenty of IOs which enable great hardware expandability. For communication and configuration the module board offers a JTAG/UART Interface.

This Getting Started Guide shows how to set up the board, attach the jumpers, wire it up and connect it with the software. The TE0802 Test Board description goes into "how to use the provided reference design" and in here we touch the aspect of how to add your own IP to the design. This includes changing the Vivado Block Design, regenerating the bitstream and using the hardware export(.xsa file) in Vitis to develop software that runs on the MicroBlaze.


1.3 Official Documentation

1.4 Hardware Features


TE0802-02-1AEV2-ATE0802-02-2AEV2-A
MPSoCXilinx Zynq UltraScale+
  • XCZU1CG-1SBVA484E
  • Speed Grade: -1
  • Temperature Grade: Extended (0 to +100 °C)
Xilinx Zynq UltraScale+
  • XCZU2CG-1SBVA484E
  • Speed Grade: -1
  • Temperature Grade: Extended (0 to +100 °C)
Storage
  • 1 GByte LPDDR4
  • 32 MByte SPI Flash
  • MicroSD-Karte
  • M2 PCIe SSD support
  • EEPROM
Display
  • DisplayPort
  • VGA
  • 4-digit 7-segment LED
  • 8 LEDs
Audio
  • 3.5 mm earphone jack (PWM output)
Connectors
  • 2x Pmod
Communication & Debug
  • USB 3.0 Host (type A connector)
  • USB JTAG/UART Micro-USB
  • 1GB Ethernet RJ45
Input
  • 5 push buttons
  • 8 bit slide switches
  • Reset button




Firgure 2: TE0717+TEB0717 Hardware Blockdiagram

Basic IOs<->FPGA connections are as following, Table 1:


ColorSignal

FPGA Pin

Function
LED D1(on carrier)redB14_L24_PP10general purpose
LED D2(on carrier)greenB14_L24_NP11"
LED D1(on module)redLED1D14"
LED D2(on module)greenLED2C14"
Clock --CLK_100MG11singled ended 100MHz clock


Information on IO routing and FPGA pin connections can be found in the schematics.


2 Board Power-Up


2.1 TE0802 Hardware Setup and Power up

  1. Check the Jumper setting

    Figure 3: Jumper setting

    The Voltage set with Jumper J1 determines the source of the input voltage for the voltages regulator chip U1 to the left of J1. Either 5V from the MicroUSB port(VUSB) or 5V from pin header J4.

    With the shown setting of Jumper J2 the voltage VADJ is set to 3.3V that comes from the carriers voltage regulator chip U1. The 1.8V comes from the module. The Voltage VADJ is wired to the module and is used as the BANK34 supply voltage.

  2. Use a MicroUSB cable to connect your board to the PC.cc
  3. All the LEDs are simply routed to the FPGA, hence none of them should be turned on. If the qspi flash on the module is preloaded with a design though, it might be that some LEDs are blinking.

  4. In case the QSPI Flash is loaded with the reference design, you can connect to the board with a program like PuTTY. Just open up a serial session with baud-rate of 9600 and the right COM-port(visible in Device Manager).
    You may need to press the RESET-button.

    Figure 4: Terminal(MicroBlaze output)

2.2 Reference Design - Introduction

We provide a reference design that interacts with most of the peripheral on the module. The provided design "TE0717 test board" shows how to connect the different parts of the module to simplify the development of your own application. You can use it for your own design but keep in mind the overall FPGA resources and power consumption before deployment.

The reference design we are introducing in this guide is "TE0717 test board". The most important steps to get it up and running are explained on TE0717 Test Board. The Download is available here.

The reference design is only usable with the specified Vivado/Vitis version. Always use the same version of Xilinx Software for one Project. (e.g. use reference design 2021.2 with vitis installation 2021.2)

The components of the reference design are illustrated in the following figure:

Figure 5: Blockdiagram of the Reference Design

The Cores are connected via the AXI Interface with the MicroBlaze Processor. How they are mapped into the address space can be seen in the address editor:

Figure 6: Vivado Address Editor - Address Mapping

For example the AXI GPIO IP Core which has a LED1 connected to it, can be controlled with software(C/C++) by raising the bits mapped to the address 0x4000 0000.

The VIO Core enables you to control connected IOs via the Vivado Hardware Manager(like LED2).

3 Notes



Document Revision History

DateVersionDescription

Authors

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy241.$Proxy3496#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject]

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy241.$Proxy3496#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject]

  • initial release

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy241.$Proxy3496#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject]

--all

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy241.$Proxy3496#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject]

Revision history.







Table of contents

  • No labels