Skip to end of metadata
Go to start of metadata


ZynqMP PS Design with Linux Example and simple frequency counter to measure SI5338 Reference CLK with Vivado HW-Manager.
Wiki Resources page:

Key Features

  • Vitis/Vivado 2021.2.1
  • PetaLinux
  • SD
  • ETH
  • USB
  • I2C
  • RTC
  • FMeter
  • MAC from EEPROM
  • User LED (PCB REV03 only)
  • Modified FSBL for SI5338 programming
  • Special FSBL for QSPI programming

Revision History

DateVivadoProject BuiltAuthorsDescription
Manuela Strücker
  • bugfix fsbl generation
  • new assembly variants
Manuela Strücker
  • update board part files compatible to Vivado 2021.2.1
  • new assembly variants
Manuela Strücker
  • new assembly variants
John Hartfiel
  • adding missing u-boot device tree to the boot.bin
John Hartfiel
  • 2021.2 release
  • new assembly variants
  • remove  alle PCB Revision 02 variante with 1GB DDR
John Hartfiel
  • 2020.2 release
  • new assembly variants
John Hartfiel
  • script update
  • new assembly variants
John Hartfiel
  • script update
  • Board Part update (minor changes)
John Hartfiel
  • script update for linux user
John Hartfiel
  • add fsbl_flash binary
  • Vitis script updates (include linux domain and prebuilt linux files for vitis)
  • prebuilt binary export on selection guide
John Hartfiel
  • 2019.2 update
  • Vitis support
John Hartfiel
  • new assembly variants
John Hartfiel
  • bugfix fsbl (removed second PSU init)
John Hartfiel
  • new assembly variants
  • USB2 only (change PS IP and device tree)
  • FSBL changes
John Hartfiel
  • renamed ...D variants to ...A

John Hartfiel
  • TE Script update
  • rework of the FSBLs
  • SI5338 CLKBuilder Pro Project
  • some additional Linux features
  • MAC from EEPROM
  • new assembly variants
  • remove special compiler flags, which was needed in 2018.2

John Hartfiel
  • new assembly variants
  • update optional petalinux startup init script
John Hartfiel
  • correction:
    • TE0820-03-4EV-1EA has 2GB DDR, now 2GB instead of 1GB is initialised
    • small changes on DDR setup of TE0820-02-2EG-1EE
John Hartfiel
  • different design for REV03
  • small petalinux changes
  • IO renaming
  • additional notes for FSBL generated with Win SDK
  • changed *.bif
John Hartfiel
  • bugfix board part files BANK1 MIO voltages
  • Add "dummy" PS USB3 parameter so solve problems with some USB2 devices

John Hartfiel
  • solved Linux Flash issue
  • new assembly variant
John Hartfiel
  • new assembly variants
John Hartfiel
  • solved JTAG/Linux issue
John Hartfiel
  • board part csv update
John Hartfiel
  • rework board part files
  • solved USB, QSPI and PHY issue
John Hartfiel
  • solved SD SDX Cards Problem
  • Separate csv name for all assembly variants
John Hartfiel
  • solved SD WP Problem
John Hartfiel
  • initial release
Design Revision History

Release Notes and Know Issues

IssuesDescriptionWorkaroundTo be fixed version
Xilinx SoftwareIncompatibility of board files for ZynqMP with eMMC activated between 2021.2 and 2021.2.1 patch, see Xilinx Forum Requestuse corresponding board files for the Vivado versions--
Uboot did not startEffected Design:
Use older version, this will be fixed as soon as possibleSolved with 2220124 update
Flash access on LinuxDevice tree is not correct on Linuxadd compatibility to "compatible “jedec,spi-nor”"Solved with 20180524 update
USB UART Terminal is blocked / SDK Debugging is blockedThis happens only with 2017.4 Linux , when JTAG connection is established on Vivado HW Manager.

Do not use HW Manager connection, or if debugging is necessary:

  1. Boot linux with usb terminal
  2. From the terminal: root root mount ifconfig eth0
  3. Open two new SSH terminals via ethernet: root root , run user application ...
  4. Exit and close the usb terminal
Solved with 20180206 update
Known Issues



Vitis2021.2.1needed, Vivado is included into Vitis installation
SI ClockBuilder Pro---optional


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
TE0820-ES1           es1            REV01     1GB      64MB      4GB        NA                     Not longer supported by vivado   
TE0820-02-02EG-1E2eg_1e_1gbREV021GB64MB4GBNA Not longer supported use 2020.2 or older    
TE0820-02-02EG-1E32eg_1e_1gbREV021GB64MB4GB2.5 mm connectorsNot longer supported use 2020.2 or older    
TE0820-02-02CG-1E2cg_1e_1gbREV021GB64MB4GBNA Not longer supported use 2020.2 or older    
TE0820-02-03EG-1E3eg_1e_1gbREV021GB64MB4GBNA Not longer supported use 2020.2 or older    
TE0820-02-03EG-1E33eg_1e_1gbREV021GB64MB4GB2.5 mm connectorsNot longer supported use 2020.2 or older    
TE0820-02-03CG-1E3cg_1e_1gbREV021GB64MB4GBNA Not longer supported use 2020.2 or older    
TE0820-02-02EG-1EA2eg_1e_1gbREV021GB128MB4GBNA Not longer supported use 2020.2 or older    
TE0820-02-02EG-1EL2eg_1e_1gbREV021GB128MB4GB2.5 mm connectorsNot longer supported use 2020.2 or older    
TE0820-02-02CG-1EA2cg_1e_1gbREV021GB128MB4GBNA Not longer supported use 2020.2 or older    
TE0820-02-03EG-1EA3eg_1e_1gbREV021GB128MB4GBNA Not longer supported use 2020.2 or older    
TE0820-02-03EG-1EL3eg_1e_1gbREV021GB128MB4GB2.5 mm connectorsNot longer supported use 2020.2 or older    
TE0820-02-03CG-1EA3cg_1e_1gbREV021GB128MB4GBNA Not longer supported use 2020.2 or older    
TE0820-02-04CG-1EA4cg_1e_1gbREV021GB128MB4GBNA Not longer supported use 2020.2 or older    
TE0820-03-02EG-1EL2eg_1e_2gbREV032GB128MB4GB2.5 mm connectorsNA
TE0820-03-03EG-1EL3eg_1e_2gbREV032GB128MB4GB2.5 mm connectorsNA
TE0820-03-2BE21FL*2eg_1e_2gbREV032GB128MB8GB2.5 mm connectorsNA
TE0820-03-3BE21FL3eg_1e_2gbREV032GB128MB8GB2.5 mm connectorsNA
TE0820-03-4DE21FL4ev_1e_2gbREV032GB128MB8GB2.5 mm connectorsNA
TE0820-03-4DE21FC4ev_1e_2gbREV032GB128MB8GBwithout encryption NCNRNA
TE0820-03-4AI21FI4cg_1i_x_2gbREV032GB128MB8GBwithout ETH PHYNA
TE0820-03-2BI21FL2eg_1i_2gbREV032GB128MB8GB2.5 mm connectorsNA
TE0820-04-2BE21FAJ2eg_1e_2gbREV042GB128MB8GBwithout spacersNA
TE0820-04-2BE21FL2eg_1e_2gbREV042GB128MB8GB2.5 mm connectorsNA
TE0820-04-2BI21FL2eg_1i_2gbREV042GB128MB8GB2.5 mm connectorsNA
TE0820-04-3AI21FAT3cg_1i_2gbREV042GB128MB8GBNACustomer supplied
TE0820-04-3BE21FL3eg_1e_2gbREV042GB128MB8GB2.5 mm connectorsNA
TE0820-04-4AI21FI4cg_1i_x_2gbREV042GB128MB8GBwithout ETH PHYNA
TE0820-04-4BI21KL4eg_1i_2gbREV042GB128MB64GB2.5 mm connectorsNA
TE0820-04-4DE21FL4ev_1e_2gbREV042GB128MB8GB2.5 mm connectorsNA
TE0820-04-3BE21ML3eg_1e_2gbREV042GB128MB8GB2.5 mm connectorsOther EMMC mfr
TE0820-04-4DE21MA4ev_1e_2gbREV042GB128MB8GBNAOther EMMC mfr
TE0820-04-4DI21MA4ev_1i_2gbREV042GB128MB8GBNAOther EMMC mfr
TE0820-04-S0023eg_1e_2gbREV042GB128MB8GBNAOther EMMC mfr|Custom supplied TE0820-04-3BE21MA
TE0820-04-S0054cg_1e_2gbREV042GB128MB8GBNAOther EMMC mfr|Custom supplied TE0820-04-4AE21MA
TE0820-04-S0064ev_1e_2gbREV042GB128MB8GBNACAO:Other EMMC mfr
TE0820-04-S0033eg_1e_2gbREV042GB128MB8GB2.5 mm connectorsOther EMMC mfr
TE0820-04-S0093eg_1e_2gbREV042GB128MB8GB2.5 mm connectorsOther EMMC mfr
TE0820-04-S0104ev_1e_2gbREV042GB128MB8GBNAOther EMMC mfr

*used as reference

Hardware Modules

Design supports following carriers:

Carrier ModelNotes
  • Important: See restrictions on usage with 7 Serie Carriers: 4 x 5 SoM Carriers
  • No SD Slot available, pins goes to Pin Header
  • For TEBA0841 REV01, please contact TE support

*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
CoolerIt's recommended to use cooler on ZynqMP device
Additional Hardware


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

Design Sources

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
PetaLinux<project folder>\os\petalinuxPetaLinux template with current configuration
Design sources

Additional Sources

SI5338<project folder>\misc\Si5338SI5338 Project with current PLL Configuration<project folder>\sd\Additional Initialization Script for Linux
Additional design sources





BIF-File*.bifFile with description to generate Bin-File
BIN-File*.binFlash Configuration File with Boot-Image (Zynq-FPGAs)
BIT-File*.bitFPGA (PL Part) Configuration File
Boot Script-File*.scr

Distro Boot Script file

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 and PetaLinux
LabTools Project-File*.lprVivado Labtools Project File
OS-Image*.ubImage with Linux Kernel (On Petalinux optional with Devicetree and RAM-Disk)
Software-Application-File*.elfSoftware Application for Zynq or MicroBlaze Processor Systems
Prebuilt files (only on ZIP with prebuilt content)


Reference Design is only usable with the specified Vivado/Vitis/PetaLinux 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 "" 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. _create_win_setup.cmd/ and follow instructions on shell:

    ------------------------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) for PetaLinux project 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. Create and configure your PetaLinux project with exported .xsa-file, see PetaLinux KICKstart
    • use TE Template from "<project folder>\os\petalinux"
    • use exported .xsa file from "<project folder>\prebuilt\hardware\<short name>" . Note: HW Export from Vivado GUI creates another path as default workspace.

  6. Configure the boot.scr file as needed, see Distro Boot with Boot.scr
  7. Copy PetaLinux build image files to prebuilt folder
    • copy u-boot.elf, u-boot.dtb,system.dtb , bl31.elf, image.ub, z and boot.scr from "<plnx-proj-root>/images/linux" to prebuilt folder

      "<project folder>\prebuilt\os\petalinux\<ddr size>" or "<project folder>\prebuilt\os\petalinux\<short name>"

  8. Generate Programming Files with Vitis

    run on Vivado TCL (Script generates applications and bootable files, which are defined in "test_board\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



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

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

Note: Depending on CPLD Firmware and Boot Mode settings, QSPI boot with Linux image on SD or complete SD Boot is possible.

Get prebuilt boot binaries

  1. _create_win_setup.cmd/ 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

Option for Boot.bin on QSPI Flash and image.ub, and boot.scr on SD or USB.

  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.bin on QSPI flash)
    TE::pr_program_flash -swapp u-boot
    TE::pr_program_flash -swapp hello_te0820 (optional)

    To program with Vitis/Vivado GUI, use special FSBL (fsbl_flash) on setup

  3. Copy image.ub, and boot.scr on SD or USB
    • use files from "<project folder>\_binaries_<Article Name>\boot_linux" from generated binary folder,see: Get prebuilt boot binaries
    • or use prebuilt file location, see "<project folder>\prebuilt\file_location.txt"
  4. Set Boot Mode to QSPI-Boot and insert SD or USB.
    • Depends on Carrier, see carrier TRM.

SD-Boot mode

  1. Copy image.ub, boot.src and Boot.bin on SD
    • use files from "<project folder>\_binaries_<Article Name>\boot_linux" from generated binary folder, see: Get prebuilt boot binaries
    • or use prebuilt file location, see "<project folder>\prebuilt\file_location.txt"
  2. Set Boot Mode to SD-Boot.
    • Depends on Carrier, see carrier TRM.
  3. Insert SD-Card in SD-Slot.


Not used on this example.


  1. Prepare HW like described on section Programming
  2. Connect UART USB (most cases same as JTAG)
  3. Select SD Card as Boot Mode (or QSPI - depending on step 1)

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

    Starting with Petalinux version 2020.1, the industry standard "Distro-Boot" boot flow for U-Boot was introduced, which significantly expands the possibilities of the boot process and has the primary goal of making booting much more standardised and predictable.
    The boot options described above describe the common boot processes for this hardware; other boot options are possible.
    For more information see Distro Boot with Boot.scr

  4. Power On PCB

    1. ZynqMP Boot ROM loads FSBL from SD/QSPI into OCM,

    2. FSBL init the PS, programs the PL using the bitstream and loads PMU, ATF and U-boot from SD/QSPI into DDR,

    3. U-boot loads Linux (image.ub) from SD/QSPI/... into DDR


  1. Open Serial Console (e.g. putty)
    • Speed: 115200
    • select COM Port

      Win OS, see device manager, Linux OS see dmesg |grep tty (UART is *USB1)

  2. Linux Console:

    Note: Wait until Linux boot finished

  3. You can use Linux shell now.

    i2cdetect -y -r 0	(check I2C 0 Bus)
    dmesg | grep rtc	(RTC check)
    udhcpc				(ETH0 check)
    lsusb				(USB check)
  4. Option Features

    • Webserver to get access to Zynq
      • insert IP on web browser to start web interface
    • scripts
      • add script on SD, content will be load automatically on startup (template included in "<project folder>\misc\SD")

Vivado HW Manager

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

  • Control:
    • User LED (PCB REV03 and newer)
  • Monitoring:
    • SI5338_CLK0 Counter: 
      • Set radix from VIO signals to unsigned integer.
        Note: Frequency Counter is inaccurate and displayed unit is Hz
      • SI5338 CLK is configured to 200MHz by default.

PCB REV03 Design:

Vivado Hardware Manager

System Design - Vivado

Block Design


Block Design PCB REV03

PS Interfaces

Activated interfaces:

USB0MIO, USB2 only


Basic module constrains

set_property BITSTREAM.GENERAL.COMPRESS TRUE [current_design]
set_property BITSTREAM.CONFIG.UNUSEDPIN PULLNONE [current_design

Design specific constrain

set_property PACKAGE_PIN K9 [get_ports {SI5338_CLK0_D_clk_p[0]}]
set_property IOSTANDARD LVDS [get_ports {SI5338_CLK0_D_clk_p[0]}]
set_property DIFF_TERM TRUE [get_ports {SI5338_CLK0_D_clk_p[0]}]

set_property PACKAGE_PIN H1 [get_ports {x0[0]}]
set_property IOSTANDARD LVCMOS18 [get_ports {x0[0]}]
set_property PACKAGE_PIN J1 [get_ports {x1[0]}]
set_property IOSTANDARD LVCMOS18 [get_ports {x1[0]}]

Software Design - Vitis

For Vitis project creation, follow instructions from:



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


TE modified 2021.2 FSBL


  • Modified Files: xfsbl_main.c, xfsbl_hooks.h/.c, xfsbl_board.h/.c (search for 'TE Mod' on source code)
  • Add Files: te_xfsbl_hooks.h/.c (for hooks and board)
  • General Changes: 
    • Display FSBL Banner and Device Name

Module Specific:

  • Add Files: all TE Files start with te_*
    • Si5338 Configuration
    • ETH+OTG Reset over MIO

zynqmp_fsbl_flash (seems to be obsolete and will be removed in one of the next revisions)

TE modified 2021.2 FSBL


  • Modified Files: xfsbl_initialisation.c, xfsbl_hw.h, xfsbl_handoff.c, xfsbl_main.c
  • General Changes:
    • Display FSBL Banner
    • Set FSBL Boot Mode to JTAG
    • Disable Memory initialisation


Xilinx default PMU firmware.


Hello TE0820 is a Xilinx Hello World example as endless loop instead of one console output.


U-Boot.elf is generated with PetaLinux. Vitis is used to generate Boot.bin.

Software Design - PetaLinux

For PetaLinux installation and project creation, follow instructions from:


Start with petalinux-config or petalinux-config --get-hw-description


  • select SD default instead of eMMC:
  •  MAC from eeprom together with uboot and device tree settings:
  • generate u-boot.dtb:


Start with petalinux-config -c u-boot

  •  MAC from eeprom together with uboot and device tree settings:
  • Boot Modes:

Change platform-top.h:

#include <configs/xilinx_zynqmp.h>#no changes

Device Tree

/include/ "system-conf.dtsi"
/ {
  chosen {
    xlnx,eeprom = &eeprom;
/*------------------ QSPI -------------------- */
&qspi {
    #address-cells = <1>;
    #size-cells = <0>;
    status = "okay";
    flash0: flash@0 {
        //compatible = "flash name, "micron,m25p80";
        compatible = "jedec,spi-nor";
        reg = <0x0>;
        #address-cells = <1>;
        #size-cells = <1>;

/*-------------------- SD0 eMMC ----------------*/
&sdhci0 {
    // disable-wp;

/*-------------------- SD1 sd2.0 ----------------*/
&sdhci1 {

/*-------------------- ETH ----------------*/
&gem3 {
    status = "okay";
  ethernet_phy0: ethernet-phy@0 {
        compatible = "marvell,88e1510";
        device_type = "ethernet-phy";
            reg = <1>;
/*-------------------- USB 2.0 only ----------------*/
&dwc3_0 {
    status = "okay";
    dr_mode = "host";
    maximum-speed = "high-speed";
&usb0 {
    status = "okay";
    /delete-property/ clocks;
    /delete-property/ clock-names;
    clocks = <0x3 0x20>;
    clock-names = "bus_clk";
/*-------------------- I2C ----------------*/
&i2c0 {
  eeprom: eeprom@50 {
     compatible = "atmel,24c08";
     reg = <0x50>;

/include/ "system-conf.dtsi"
/ {
  chosen {
    xlnx,eeprom = &eeprom;
/*------------------ QSPI -------------------- */
&qspi {
    #address-cells = <1>;
    #size-cells = <0>;
    status = "okay";
    flash0: flash@0 {
        //compatible = "flash name, "micron,m25p80";
        compatible = "jedec,spi-nor";
        reg = <0x0>;
        #address-cells = <1>;
        #size-cells = <1>;

/*-------------------- SD0 eMMC ----------------*/
&sdhci0 {
    // disable-wp;

/*-------------------- SD1 sd2.0 ----------------*/
&sdhci1 {

/*-------------------- ETH ----------------*/
&gem3 {
    status = "okay";
  ethernet_phy0: ethernet-phy@0 {
        compatible = "marvell,88e1510";
        device_type = "ethernet-phy";
            reg = <1>;
/*-------------------- USB 2.0 only ----------------*/
&dwc3_0 {
    status = "okay";
    dr_mode = "host";
    maximum-speed = "high-speed";
&usb0 {
    status = "okay";
    /delete-property/ clocks;
    /delete-property/ clock-names;
    clocks = <0x3 0x20>;
    clock-names = "bus_clk";
/*-------------------- I2C ----------------*/
&i2c0 {
  eeprom: eeprom@50 {
     compatible = "atmel,24c08";
     reg = <0x50>;


Start with petalinux-config -c kernel


  • Only needed to fix JTAG Debug issue:

    • CONFIG_CPU_IDLE is not set

    • CONFIG_CPU_FREQ is not set



Start with petalinux-config -c rootfs


  • for web server app:
    • CONFIG_busybox-httpd=y
  • For additional test tools only:
    • CONFIG_i2c-tools=y
    • CONFIG_packagegroup-petalinux-utils(util-linux,cpufrequtils,bridge-utils,mtd-utils,usbutils,pciutils,canutils,i2c-tools,smartmontools,e2fsprogs)


See "<project folder>\os\petalinux\project-spec\meta-user\recipes-apps\"


Script App to load from SD Card if available.


Webserver application suitable for Zynq access. Need busybox-httpd

Additional Software


File location "<project folder>\misc\Si5338\Si5338-*.slabtimeproj"

General documentation how you work with these project will be available on Si5338

Appx. A: Change History and Legal Notices

Document Change History

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

DateDocument RevisionAuthorsDescription

  • bugfix fsbl generation
  • new assembly variants
2022-09-12v.73Manuela Strücker
  • update board part files compatible to Vivado 2021.2.1
  • new assembly variants

Manuela Strücker

  • new assembly variants
2022-01-26v.70John Hartfiel
  • add missing uboot notes
2022-01-24v.68John Hartfiel
  • Add new delivery design with uboot bugfix
2022-01-21v.67John Hartfiel
  • Add Known issues
2022-01-14v.66John Hartfiel
  • 2021.2 release
2021-06-09v.65Manuela Strücker
  • document style update
2021-06-01v.64John Hartfiel
  • 2020.2 update
  • new assembly variants
  • document style update
2020-05-07v.62John Hartfiel
  • update programming section
2020-04-08v.61John Hartfiel
  • script update
  • new assembly variants
2020-03-25v.60John Hartfiel
  • script update
2020-01-21v.59John Hartfiel
  • Script update for linux user
2020-01-14v.58John Hartfiel
  • Script update, new features
  • doc update
  • add missing binary files
2019-12-19v.57John Hartfiel
  • 2019.2 release
2019-10-29v.56John Hartfiel
  • new assembly variants
2019-08-09v.55John Hartfiel
  • bugfix fsbl
2019-06-19v.54John Hartfiel
  • design changes
  • new variants
2019-04-01v.53John Hartfiel
  • some notes
  • renamed ..D variants to ...A


v.47John Hartfiel
  • 2018.3 release finished (include design reworks)


v.43John Hartfiel
  • Update Design files for 2GB variants
  • rebuilt petalinux for optional init script


v.41John Hartfiel
  • Update Design files for 2GB variants


v.40John Hartfiel
  • add notes to ES1


v.38John Hartfiel
  • 2018.2 release finished


v.34John Hartfiel
  • Design Files Update


v.29John Hartfiel
  • Design Files Update
2018-02-06v.27John Hartfiel
  • Design Files Update
2018-01-29v.26John Hartfiel
  • Update Known Issues
2018-01-24v.25John Hartfiel
  • Release 2017.4
2018-01-10v.24John Hartfiel
  • Update Known Issues
2017-12-20v.23John Hartfiel
  • Typo correction
  • Update HW Module Table Description


John Hartfiel
  • Design Update
2017-11-20v.18John Hartfiel
  • Design Update
  • Add Variants with 128MB Flash
2017-11-13v.16John Hartfiel
  • Update Carrier sections
2017-11-06v.15John Hartfiel
  • Typo corrected
2017-10-23v.13John Hartfiel
  • Update Key Features section
  • Style Update Additional Software section
John Hartfiel
  • Release 2017.2
2017-09-11v.1Initial release

Document change history.

Legal Notices

Data Privacy

Please also note our data protection declaration at

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.

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.



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).


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


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

  • No labels