Overview


This example contains a simple MicroBlaze V (RISC-V) design for the Spartan UltraScale+ module TE0873. The processor runs an endless loop application, which prints "Hello Trenz Module TE0873" on the MDM JTAG UART and lets the user LED blink. The 64 MByte SDR-SDRAM on the module is accessible over an AXI4 SDRAM controller.

Refer to http://trenz.org/te0873-info for the current online version of this manual and other available documentation.

Key Features

  • Vitis/Vivado 2025.2
  • MicroBlaze V (RISC-V)
  • MDM JTAG UART
  • SDR-SDRAM 64 MByte (AXI4 SDRAM controller, 50 MHz)
  • QSPI Flash (boot from PDI)
  • LED
  • VIO

Revision History

DateVivadoProject BuiltAuthorsDescription
2026-xx-xx2025.2

TE0873-test_board-vivado_2025.2-build_x_xxxxxxxxxxxxxx.zip
TE0873-test_board_noprebuilt-vivado_2025.2-build_x_xxxxxxxxxxxxxx.zip

Waldemar Hanemann
  • initial release
Design Revision History

Release Notes and Know Issues

IssuesDescriptionWorkaroundTo be fixed version
No known issues---------
Known Issues

Requirements

Software

SoftwareVersionNote
Vitis2025.2needed, Vivado is included into Vitis installation
Software

Hardware

Basic description of TE Board Part Files is available on TE Board Part Files.

Complete List is available on "<project folder>\board_files\*_board_files.csv"

Design supports following modules:

Module ModelBoard Part Short NamePCB Revision SupportDDRQSPI FlashEMMCOthersNotes
TE0873-01-P00135_1eREV0164MB SDRAM16MBNANANA
TE0873-01-P1E12-A*35_1eREV0164MB SDRAM16MBNANANA

*used as reference

Hardware Modules

Design supports following carriers:

Carrier ModelNotes
TE0701*

*used as reference

Hardware Carrier

Additional HW Requirements:

Additional HardwareNotes
USB Cable for JTAG/UARTCheck Carrier Board and Programmer for correct type
XMOD ProgrammerCarrier Board dependent, only if carrier has no own FTDI
Additional Hardware

Content

For general structure and usage of the reference design, see Project Delivery - AMD devices

Design Sources

TypeLocationNotes
Vivado<project folder>\block_design
<project folder>\constraints
<project folder>\ip_lib
<project folder>\board_files
Vivado Project will be generated by TE Scripts
Vitis<project folder>\sw_libAdditional Software Template for Vitis and apps_list.csv with settings automatically for Vitis app generation
Design sources

Additional Sources

TypeLocationNotes
---------
Additional design sources

Prebuilt

File

File-Extension

Description

BIF-File*.bifFile with description to generate Bin-File
BIT-File*.bitFPGA Configuration File (with *.elf content in programming_files folder)
DebugProbes-File*.ltxDefinition File for Vivado/Vivado Labtools Debugging Interface
Diverse Reports---Report files in different formats
Hardware-Platform-Description-File*.xsaExported Vivado hardware description file for Vitis
LabTools Project-File*.lprVivado Labtools Project File
MCS-File*.mcsFlash Configuration File with Boot-Image (MicroBlaze or FPGA part only)
MMI-File*.mmiFile with BRAM-Location to generate MCS or BIT-File with *.elf content (MicroBlaze only)
PDI-File*.pdiProgrammable Device Image with Boot-Image (Spartan UltraScale+ configuration file)
PRM-File*.prmMemory configuration checksum file for flash programming
Software-Application-File*.elfSoftware Application for MicroBlaze Processor Systems (plm.elf: Platform Loader and Manager)
Prebuilt files (only on ZIP with prebuilt content)

Download

Reference Design is only usable with the specified Vivado/Vitis version. Do never use different Versions of Xilinx Software for the same Project.

Reference Design is available on:

Design Flow


Reference Design is available with and without prebuilt files. It's recommended to use TE prebuilt files for first launch.

Trenz Electronic provides a tcl based built environment based on Xilinx Design Flow.

See also:

The Trenz Electronic FPGA Reference Designs are TCL-script based project. Command files for execution will be generated with "_create_win_setup.cmd" on Windows OS and "_create_linux_setup.sh" on Linux OS.

TE Scripts are only needed to generate the vivado project, all other additional steps are optional and can also executed by Xilinx Vivado/Vitis GUI. For currently Scripts limitations on Win and Linux OS see: Project Delivery Currently limitations of functionality

Caution! Win OS has a 260 character limit for path lengths which can affect the Vivado tools. To avoid this issue, use Virtual Drive or the shortest possible names and directory locations for the reference design (for example "x:\<project folder>")

  1. Run _create_win_setup.cmd/_create_linux_setup.sh and follow instructions on shell:

    _create_win_setup.cmd/_create_linux_setup.sh
    ------------------------Set design paths----------------------------
    -- Run Design with: _create_win_setup
    -- Use Design Path: <absolute project path>
    --------------------------------------------------------------------
    -------------------------TE Reference Design---------------------------
    --------------------------------------------------------------------
    -- (0)  Module selection guide, project creation...prebuilt export...
    -- (1)  Create minimum setup of CMD-Files and exit Batch
    -- (2)  Create maximum setup of CMD-Files and exit Batch
    -- (3)  (internal only) Dev
    -- (4)  (internal only) Prod
    -- (c)  Go to CMD-File Generation (Manual setup)
    -- (d)  Go to Documentation (Web Documentation)
    -- (g)  Install Board Files from Xilinx Board Store (beta)
    -- (a)  Start design with unsupported Vivado Version (beta)
    -- (x)  Exit Batch (nothing is done!)
    ----
    Select (ex.:'0' for module selection guide):
  2. Press 0 and enter to start "Module Selection Guide"
  3. Create project and follow instructions of the product selection guide, settings file will be configured automatically during this process.
    • optional for manual changes: Select correct device and Xilinx install path on "design_basic_settings.cmd" and create Vivado project with "vivado_create_project_guimode.cmd"

      Note: Select correct one, see also Vivado Board Part Flow

  4. Create hardware description file (.xsa file) and export to prebuilt folder

    run on Vivado TCL (Script generates design and export files into "<project folder>\prebuilt\hardware\<short name>")
    TE::hw_build_design -export_prebuilt

    Using Vivado GUI is the same, except file export to prebuilt folder.

  5. Generate Programming Files (*.pdi and *.mcs file for QSPI Flash) with Vitis

    run on Vivado TCL (Script generates applications and bootable files, which are defined in "<project folder>\sw_lib\apps_list.csv")
    TE::sw_run_vitis -all
    TE::sw_run_vitis (optional; Start Vitis from Vivado GUI or start with TE Scripts on Vivado TCL)

    TCL scripts generate also platform project, this must be done manually in case GUI is used. See Vitis

    • latest "hello_te0873.elf" application should reside in "<project folder>\firmware\microblaze_riscv_0\" now
    • Regenerate Vivado Project or update Bitfile only, with new "hello_te0873.elf" associated to the MicroBlaze V processor

Launch


Programming

Check Module and Carrier TRMs for proper HW configuration before you try any design.

Reference Design is also available with prebuilt files. It's recommended to use TE prebuilt files for first launch.

Xilinx documentation for programming and debugging: Vivado/Vitis/SDSoC-Xilinx Software Programming and Debugging

Get prebuilt boot binaries

  1. Run _create_win_setup.cmd/_create_linux_setup.sh and follow instructions on shell
  2. Press 0 and enter to start "Module Selection Guide"
    1. Select assembly version
    2. Validate selection
    3. Select create and open delivery binary folder

      Note: Folder "<project folder>\_binaries_<Article Name>" with subfolder "boot_<app name>" for different applications will be generated

QSPI-Boot mode

  1. Connect JTAG and power on carrier with module
  2. Open Vivado Project with "vivado_open_existing_project_guimode.cmd" or if not created, create with "vivado_create_project_guimode.cmd"

    run on Vivado TCL (Script programs boot image *.pdi on QSPI flash)
    TE::pr_program_flash -swapp hello_te0873
  3. Power your board OFF and ON to start the application and see the output on the JTAG UART console

JTAG

Not used on this example.

Usage

  1. Prepare HW like described on section Programming
  2. Connect JTAG USB
  3. Select QSPI as Boot Mode

    Note: See TRM of the Carrier, which is used.

  4. Power On PCB

    1. Spartan UltraScale+ loads the boot image (*.pdi) from QSPI Flash, the PLM configures the FPGA with the bitstream including the "hello_te0873.elf" application in local BRAM

    2. hello_te0873.elf application starts on MicroBlaze V

    3. "Hello Trenz Module TE0873" will be printed on the JTAG UART console and the user LED blinks

JTAG UART

The design has no physical UART. Console output (stdin/stdout) is routed over the UART of the MicroBlaze Debug Module (MDM) and is available on the JTAG connection.

  1. Start XSDB (Vitis installation) and open the JTAG terminal:

    run on XSDB
    connect
    targets -set -filter {name =~ "MicroBlaze*#0"}
    jtagterminal
  2. Alternatively use the JTAG UART console of the Vitis debugger.

Note: Do not reboot, if Bitfile programming over JTAG is used as programming method.

Vivado HW Manager

Open Vivado HW-Manager and add VIO signal to dashboard (*.ltx located on prebuilt folder)

  • Control:
    • probe_out0: Active Low External Reset of the processor system and SDRAM controller (default: 1)
  • Monitoring:
    • probe_in0: AXI GPIO bit 0, toggles with the LED of the hello_te0873 application



Vivado Hardware Manager

System Design - Vivado


Block Design


The block design contains a MicroBlaze V (RISC-V) processor with 128 KByte local memory, MicroBlaze Debug Module with JTAG UART, AXI Interrupt Controller, AXI Timer, AXI GPIO for the user LED, VIO for reset control and the Trenz AXI4 SDRAM controller ("<project folder>\ip_lib\sdram_axi_te") for the 64 MByte SDR-SDRAM.

The 100 MHz reference clock is used by a clocking wizard to generate 100 MHz for the processor system and 50 MHz for the SDRAM controller. The AXI SmartConnect bridges between both clock domains.

Address Map

Base AddressRangeSlave
0x0000_0000128KLocal memory (LMB BRAM)
0x4000_000064Kaxi_gpio_0
0x4120_000064Kmicroblaze_riscv_0_axi_intc
0x41C0_000064Kaxi_timer_0
0x44A0_000064Kmdm_1
0x8000_000064Msdram_axi_0 (SDR-SDRAM)
Address Map

Constraints

Basic module constraints

_i_bitgen_common.xdc
set_property BITSTREAM.GENERAL.COMPRESS TRUE [current_design]
set_property BITSTREAM.CONFIG.CONFIGRATE 63 [current_design]
set_property CONFIG_VOLTAGE 1.8 [current_design]
#set_property CFGBVS VCCO [current_design]
set_property CONFIG_MODE SPIx4 [current_design]
#set_property BITSTREAM.CONFIG.SPI_32BIT_ADDR YES [current_design]
#set_property BITSTREAM.CONFIG.SPI_BUSWIDTH 4 [current_design]
set_property BITSTREAM.CONFIG.M1PIN PULLNONE [current_design]
set_property BITSTREAM.CONFIG.M2PIN PULLNONE [current_design]
set_property BITSTREAM.CONFIG.M0PIN PULLNONE [current_design]

set_property BITSTREAM.CONFIG.USR_ACCESS TIMESTAMP [current_design]
_i_bitgen.xdc
set_property BITSTREAM.CONFIG.UNUSEDPIN PULLDOWN [current_design]

#
#
#

Design specific constraints

_i_io.xdc
set_property PACKAGE_PIN AC17 [get_ports clk_100MHz]
set_property IOSTANDARD LVCMOS33 [get_ports clk_100MHz]

set_property PACKAGE_PIN AB21 [get_ports B45_LED1]
set_property IOSTANDARD LVCMOS33 [get_ports B45_LED1]

# =====================================================================================================
# IS42S16320F-6BL  SDR-SDRAM  (512Mbit, 32M x16, 4 Banks)
# -----------------------------------------------------------------------------------------------------
#   * 3.3V device, connected banks use VCCO 3.3V.
#   * A13 is not connected on this SDRAM density and therefore not constrained.
#   * Controller and SDRAM run at 50 MHz (CL2), no additional I/O timing constraints are used.
# -----------------------------------------------------------------------------------------------------

# ---- Address ----
set_property PACKAGE_PIN T22  [get_ports {sdram_a[0]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[0]}]
set_property PACKAGE_PIN U23   [get_ports {sdram_a[1]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[1]}]
set_property PACKAGE_PIN AE24 [get_ports {sdram_a[2]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[2]}]
set_property PACKAGE_PIN AD24 [get_ports {sdram_a[3]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[3]}]
set_property PACKAGE_PIN V24  [get_ports {sdram_a[4]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[4]}]
set_property PACKAGE_PIN U24  [get_ports {sdram_a[5]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[5]}]
set_property PACKAGE_PIN W25  [get_ports {sdram_a[6]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[6]}]
set_property PACKAGE_PIN P20  [get_ports {sdram_a[7]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[7]}]
set_property PACKAGE_PIN P23  [get_ports {sdram_a[8]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[8]}]
set_property PACKAGE_PIN W23  [get_ports {sdram_a[9]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[9]}]
set_property PACKAGE_PIN V23   [get_ports {sdram_a[10]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[10]}]
set_property PACKAGE_PIN N21  [get_ports {sdram_a[11]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[11]}]
set_property PACKAGE_PIN U25  [get_ports {sdram_a[12]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_a[12]}]

# ---- Bank address ----
set_property PACKAGE_PIN AD25 [get_ports {sdram_ba[0]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_ba[0]}]
set_property PACKAGE_PIN T20  [get_ports {sdram_ba[1]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_ba[1]}]

# ---- Clock / control ----
set_property PACKAGE_PIN V25  [get_ports sdram_clk]
set_property IOSTANDARD LVCMOS33 [get_ports sdram_clk]
set_property PACKAGE_PIN Y25  [get_ports sdram_cke]
set_property IOSTANDARD LVCMOS33 [get_ports sdram_cke]
set_property PACKAGE_PIN R20  [get_ports sdram_csn]
set_property IOSTANDARD LVCMOS33 [get_ports sdram_csn]
set_property PACKAGE_PIN R22  [get_ports sdram_rasn]
set_property IOSTANDARD LVCMOS33 [get_ports sdram_rasn]
set_property PACKAGE_PIN AC25 [get_ports sdram_casn]
set_property IOSTANDARD LVCMOS33 [get_ports sdram_casn]
set_property PACKAGE_PIN U22  [get_ports sdram_wen]
set_property IOSTANDARD LVCMOS33 [get_ports sdram_wen]

# ---- Data mask ----
set_property PACKAGE_PIN AB23 [get_ports {sdram_dqm[0]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dqm[0]}]
set_property PACKAGE_PIN T23  [get_ports {sdram_dqm[1]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dqm[1]}]

# ---- Data ----
set_property PACKAGE_PIN AA24 [get_ports {sdram_dq[0]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[0]}]
set_property PACKAGE_PIN AE22 [get_ports {sdram_dq[1]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[1]}]
set_property PACKAGE_PIN AA25 [get_ports {sdram_dq[2]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[2]}]
set_property PACKAGE_PIN AA23 [get_ports {sdram_dq[3]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[3]}]
set_property PACKAGE_PIN AB24 [get_ports {sdram_dq[4]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[4]}]
set_property PACKAGE_PIN AE23 [get_ports {sdram_dq[5]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[5]}]
set_property PACKAGE_PIN AB25 [get_ports {sdram_dq[6]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[6]}]
set_property PACKAGE_PIN Y23  [get_ports {sdram_dq[7]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[7]}]
set_property PACKAGE_PIN R23  [get_ports {sdram_dq[8]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[8]}]
set_property PACKAGE_PIN R25  [get_ports {sdram_dq[9]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[9]}]
set_property PACKAGE_PIN P24  [get_ports {sdram_dq[10]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[10]}]
set_property PACKAGE_PIN P25  [get_ports {sdram_dq[11]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[11]}]
set_property PACKAGE_PIN N24  [get_ports {sdram_dq[12]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[12]}]
set_property PACKAGE_PIN N25  [get_ports {sdram_dq[13]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[13]}]
set_property PACKAGE_PIN N23  [get_ports {sdram_dq[14]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[14]}]
set_property PACKAGE_PIN N22  [get_ports {sdram_dq[15]}]
set_property IOSTANDARD LVCMOS33 [get_ports {sdram_dq[15]}]

Software Design - Vitis


For Vitis project creation, follow instructions from:

Vitis

Application

Template location: "<project folder>\sw_lib\sw_apps\"

hello_te0873

Trenz Hello World example as endless loop. The application prints "Hello Trenz Module TE0873 (Loop: <n>)" on the JTAG UART and toggles the user LED every second over the AXI GPIO IP core.

Template location: "<project folder>\sw_lib\sw_apps\hello_te0873"

Additional Software


No additional software is needed.

App. A: Change History and Legal Notices


Document Change History

To get content of older revision go to "Change History" of this page and select older document revision number.

DateDocument Revision

Authors

Description

  • 2025.2 release
  • initial release
--all--
Document change history.

Legal Notices

Data Privacy

Please also note our data protection declaration at https://www.trenz-electronic.de/en/Data-protection-Privacy

Document Warranty

The material contained in this document is provided “as is” and is subject to being changed at any time without notice. Trenz Electronic does not warrant the accuracy and completeness of the materials in this document. Further, to the maximum extent permitted by applicable law, Trenz Electronic disclaims all warranties, either express or implied, with regard to this document and any information contained herein, including but not limited to the implied warranties of merchantability, fitness for a particular purpose or non infringement of intellectual property. Trenz Electronic shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein.

Limitation of Liability

In no event will Trenz Electronic, its suppliers, or other third parties mentioned in this document be liable for any damages whatsoever (including, without limitation, those resulting from lost profits, lost data or business interruption) arising out of the use, inability to use, or the results of use of this document, any documents linked to this document, or the materials or information contained at any or all such documents. If your use of the materials or information from this document results in the need for servicing, repair or correction of equipment or data, you assume all costs thereof.

Product Disclaimer

Products (incl. Software and Firmware) are exclusively designed, manufactured, and distributed for industrial applications. They are not intended, authorized, or certified for use in critical safety applications, medical devices, aerospace, nuclear, life-support, traffic-control, military, or other environments where malfunction or failure could result in personal injury, death, or significant property or environmental damage.

Trenz Electronic GmbH (“Manufacturer”) excludes any liability for inappropriate use in such contexts. The Customer bears all responsibility for verifying suitability and compliance with applicable regulations when deploying in any critical-use scenario. The Customer also agrees to indemnify and hold harmless the Manufacturer from any third-party claims or liabilities arising from such use.

Copyright Notice

No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Trenz Electronic.

Technology Licenses

The hardware / firmware / software described in this document are furnished under a license and may be used /modified / copied only in accordance with the terms of such license.

Environmental Protection

To confront directly with the responsibility toward the environment, the global community and eventually also oneself. Such a resolution should be integral part not only of everybody's life. Also enterprises shall be conscious of their social responsibility and contribute to the preservation of our common living space. That is why Trenz Electronic invests in the protection of our Environment.

REACH, RoHS and WEEE

REACH

Trenz Electronic is a manufacturer and a distributor of electronic products. It is therefore a so called downstream user in the sense of REACH. The products we supply to you are solely non-chemical products (goods). Moreover and under normal and reasonably foreseeable circumstances of application, the goods supplied to you shall not release any substance. For that, Trenz Electronic is obliged to neither register nor to provide safety data sheet. According to present knowledge and to best of our knowledge, no SVHC (Substances of Very High Concern) on the Candidate List are contained in our products. Furthermore, we will immediately and unsolicited inform our customers in compliance with REACH - Article 33 if any substance present in our goods (above a concentration of 0,1 % weight by weight) will be classified as SVHC by the European Chemicals Agency (ECHA).

RoHS

Trenz Electronic GmbH herewith declares that all its products are developed, manufactured and distributed RoHS compliant.

WEEE

Information for users within the European Union in accordance with Directive 2002/96/EC of the European Parliament and of the Council of 27 January 2003 on waste electrical and electronic equipment (WEEE).

Users of electrical and electronic equipment in private households are required not to dispose of waste electrical and electronic equipment as unsorted municipal waste and to collect such waste electrical and electronic equipment separately. By the 13 August 2005, Member States shall have ensured that systems are set up allowing final holders and distributors to return waste electrical and electronic equipment at least free of charge. Member States shall ensure the availability and accessibility of the necessary collection facilities. Separate collection is the precondition to ensure specific treatment and recycling of waste electrical and electronic equipment and is necessary to achieve the chosen level of protection of human health and the environment in the European Union. Consumers have to actively contribute to the success of such collection and the return of waste electrical and electronic equipment. Presence of hazardous substances in electrical and electronic equipment results in potential effects on the environment and human health. The symbol consisting of the crossed-out wheeled bin indicates separate collection for waste electrical and electronic equipment.

Trenz Electronic is registered under WEEE-Reg.-Nr. DE97922676.




Table of contents