<!-- Template Revision 1.0 Basic Notes - export PDF to download, if vivado revision is changed! - Template is for different design and SDSoC and examples, remove unused or wrong description! --> |
Online version of this manual and other related documents can be found at https://wiki.trenz-electronic.de/display/PD/Trenz+Electronic+Documentation |
Table of contents |
<!-- General Design description --> |
<!-- Add Basic Key Features of the design (should be tested) --> |
<!-- - Add changes from design - Export PDF to download, if vivado revision is changed! --> |
Date | Vivado | Project Built | Authors | Description |
---|---|---|---|---|
2017-09-11 | 2017.1 | te0803-SK0803_zusys_SDSoC-vivado_2017.1-build_05_20170911131522 | John Hartfiel | initial release |
<!-- - add known Design issues and general Notes for the current revision --> |
Issues | Description | Workaround | To be fixed version |
---|---|---|---|
UBoot ETH PHY Address | PHY Address is not set correctly for UBoot | --- | --- |
Linux Message: "macb ... .ethernet eth...: unable to generate target frequency: 25000000 Hz" | This can be ignored, ETH works. |
<!-- Add needed external Software --> |
Software | Version | Note |
---|---|---|
Vivado | 2017.2 | needed |
SDK | 2017.2 | needed |
PetaLinux | 2017.2 | needed |
<!-- Hardware Support --> |
Basic description of TE Board Part Files is available on TE Board Part Files.
Complete List is available on <design name>/board_files/*_board_files.csv
Design supports following modules:
Module Model | Board Part Short Name | PCB Revision Support | Notes |
---|---|---|---|
TE0728-03-1Q | 03_1q | 01,02,03 | |
TE0728-04-1Q | 04_1q | 04 |
Design supports following carriers:
Carrier Model | Notes |
---|---|
TEB0728 |
Additional HW Requirements:
Additional Hardware | Notes |
---|---|
USB Cable for JTAG/UART | |
XMOD Programmer |
<!-- Remove unused content --> |
For general structure and of the reference design, see Project Delivery
Type | Location | Notes |
---|---|---|
Vivado | <design name>/block_design <design name>/constraints <design name>/ip_lib | Vivado Project will be generated by TE Scripts |
SDK/HSI | <design name>/sw_lib | Additional Software Template for SDK/HSI and apps_list.csv with settings for HSI |
PetaLinux | <design name>/os/petalinux | PetaLinux template with current configuration |
Type | Location | Notes |
---|---|---|
<!-- <table width="100%"> <tr> <th>File </th> <th>File-Extension</th> <th>Description </th> </tr> <tr> <td>BIF-File </td> <td>*.bif </td> <td>File with description to generate Bin-File </td> </tr> <tr> <td>BIN-File </td> <td>*.bin </td> <td>Flash Configuration File with Boot-Image (Zynq-FPGAs) </td> </tr> <tr> <td>BIT-File </td> <td>*.bit </td> <td>FPGA Configuration File </td> </tr> <tr> <td>DebugProbes-File </td> <td>*.ltx </td> <td>Definition File for Vivado/Vivado Labtools Debugging Interface </td> </tr> <tr> <td>Debian SD-Image </td> <td>*.img </td> <td>Debian Image for SD-Card </td> </tr> <tr> <td>Diverse Reports </td> <td> --- </td> <td>Report files in different formats </td> </tr> <tr> <td>Hardware-Platform-Specification-Files</td> <td>*.hdf </td> <td>Exported Vivado Hardware Specification for SDK/HSI </td> </tr> <tr> <td>LabTools Project-File </td> <td>*.lpr </td> <td>Vivado Labtools Project File </td> </tr> <tr> <td>MCS-File </td> <td>*.mcs </td> <td>Flash Configuration File with Boot-Image (MicroBlaze or FPGA part only) </td> </tr> <tr> <td>MMI-File </td> <td>*.mmi </td> <td>File with BRAM-Location to generate MCS or BIT-File with *.elf content (MicroBlaze only) </td> </tr> <tr> <td>OS-Image </td> <td>*.ub </td> <td>Image with Linux Kernel (On Petalinux optional with Devicetree and RAM-Disk) </td> </tr> <tr> <td>Software-Application-File </td> <td>*.elf </td> <td>Software Application for Zynq or MicroBlaze Processor Systems </td> </tr> <tr> <td>SREC-File </td> <td>*.srec </td> <td>Converted Software Application for MicroBlaze Processor Systems </td> </tr> </table> --> |
File | File-Extension | Description |
---|---|---|
BIF-File | *.bif | File with description to generate Bin-File |
BIN-File | *.bin | Flash Configuration File with Boot-Image (Zynq-FPGAs) |
BIT-File | *.bit | FPGA (PL Part) Configuration File |
Diverse Reports | --- | Report files in different formats |
Hardware-Platform-Specification-Files | *.hdf | Exported Vivado Hardware Specification for SDK/HSI and PetaLinux |
LabTools Project-File | *.lpr | Vivado Labtools Project File |
OS-Image | *.ub | Image with Linux Kernel (On Petalinux optional with Devicetree and RAM-Disk) |
Software-Application-File | *.elf | Software Application for Zynq or MicroBlaze Processor Systems |
Reference Design is only usable with the specified Vivado/SDK/PetaLinux/SDx version. Do never use different Versions of Xilinx Software for the same Project.
<!-- Add correct path:https://shop.trenz-electronic.de/en/Download/?path=Trenz_Electronic/TE0803/Reference_Design/2017.1/Starterkit --> |
Reference Design is available on:
<!-- Basic Design Steps Add/ Remove project specific --> |
Reference Design is available with and without prebuilt files. It's recommended to use TE prebuilt files for first lunch. MIO Bank 501 Power is Carrier depends and set to 3.3V. Please check Settings, if you use a own carrier. |
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/SDK GUI. For currently Scripts limitations on Win and Linux OS see: Project Delivery Currently limitations of functionality
<!-- Description of Block Design, Constrains... BD Pictures from Export... --> |
Check Module and Carrier TRMs for proper HW configuration before you try any design. |
Xilinx documentation for programming and debugging: Vivado/SDK/SDSoC-Xilinx Software Programming and Debugging
Not used on this Example.
Not used on this Example.
<!-- Description of Block Design, Constrains... BD Pictures from Export... --> |
Type | Note |
---|---|
DDR | --- |
QSPI | MIO |
CAN1 | MIO |
ETH0 | EMIO |
ETH1 | EMIO |
SD0 | MIO |
UART1 | MIO |
I2C0 | MIO |
SPI1 | MIO |
GPIO | MIO/EMIO |
TIMER0 | EMIO |
# # Common bitgen related settings # set_property BITSTREAM.GENERAL.COMPRESS TRUE [current_design] set_property CONFIG_VOLTAGE 3.3 [current_design] set_property CFGBVS VCCO [current_design] set_property BITSTREAM.CONFIG.USR_ACCESS TIMESTAMP [current_design] |
############# #ETH0/ETH1 ##### #pwr_down set_property PACKAGE_PIN L21 [get_ports {PHY_PD[0]}] set_property PACKAGE_PIN R20 [get_ports {PHY_PD[1]}] #rst_n set_property PACKAGE_PIN M15 [get_ports {PHY_RSTN[0]}] set_property PACKAGE_PIN R16 [get_ports {PHY_RSTN[1]}] #io standard set_property IOSTANDARD LVCMOS33 [get_ports {PHY*}] set_property IOSTANDARD LVCMOS33 [get_ports mdio_*] set_property IOSTANDARD LVCMOS33 [get_ports MDIO_*] set_property IOSTANDARD LVCMOS33 [get_ports {MII_*}] #pullup/down for PHY address 1 set_property PULLUP true [get_ports MII_col] set_property PULLDOWN true [get_ports {MII_rxd[0]}] set_property PULLDOWN true [get_ports {MII_rxd[1]}] set_property PULLDOWN true [get_ports {MII_rxd[2]}] set_property PULLDOWN true [get_ports {MII_rxd[3]}] #pullup/down for PHY address 2 set_property PULLDOWN true [get_ports MII_1_col] set_property PULLUP true [get_ports {MII_1_rxd[0]}] set_property PULLDOWN true [get_ports {MII_1_rxd[1]}] set_property PULLDOWN true [get_ports {MII_1_rxd[2]}] set_property PULLDOWN true [get_ports {MII_1_rxd[3]}] ############# #ETH0 ##### set_property PACKAGE_PIN M16 [get_ports mdio_ethernet_0_mdio_io] set_property PACKAGE_PIN P16 [get_ports MDIO_ETHERNET_0_mdc] set_property PACKAGE_PIN M22 [get_ports {MII_txd[3]}] set_property PACKAGE_PIN K21 [get_ports {MII_txd[2]}] set_property PACKAGE_PIN M17 [get_ports {MII_txd[1]}] set_property PACKAGE_PIN J22 [get_ports {MII_txd[0]}] set_property PACKAGE_PIN J20 [get_ports {MII_rxd[3]}] set_property PACKAGE_PIN J18 [get_ports {MII_rxd[2]}] set_property PACKAGE_PIN K18 [get_ports {MII_rxd[1]}] set_property PACKAGE_PIN L17 [get_ports {MII_rxd[0]}] set_property PACKAGE_PIN L16 [get_ports MII_col] set_property PACKAGE_PIN N15 [get_ports MII_crs] set_property PACKAGE_PIN L18 [get_ports MII_rx_clk] set_property PACKAGE_PIN P15 [get_ports MII_rx_dv] set_property PACKAGE_PIN P17 [get_ports MII_rx_er] set_property PACKAGE_PIN K19 [get_ports MII_tx_clk] set_property PACKAGE_PIN J21 [get_ports MII_tx_en] ############# #ETH1 ##### set_property PACKAGE_PIN T16 [get_ports mdio_ethernet_1_mdio_io] set_property PACKAGE_PIN T17 [get_ports MDIO_ETHERNET_1_mdc] set_property PACKAGE_PIN R21 [get_ports {MII_1_txd[3]}] set_property PACKAGE_PIN P22 [get_ports {MII_1_txd[2]}] set_property PACKAGE_PIN P21 [get_ports {MII_1_txd[1]}] set_property PACKAGE_PIN N22 [get_ports {MII_1_txd[0]}] set_property PACKAGE_PIN T19 [get_ports {MII_1_rxd[3]}] set_property PACKAGE_PIN T18 [get_ports {MII_1_rxd[2]}] set_property PACKAGE_PIN R19 [get_ports {MII_1_rxd[1]}] set_property PACKAGE_PIN R18 [get_ports {MII_1_rxd[0]}] set_property PACKAGE_PIN P20 [get_ports MII_1_col] set_property PACKAGE_PIN N18 [get_ports MII_1_crs] set_property PACKAGE_PIN M19 [get_ports MII_1_rx_clk] set_property PACKAGE_PIN N17 [get_ports MII_1_rx_dv] set_property PACKAGE_PIN P18 [get_ports MII_1_rx_er] set_property PACKAGE_PIN N19 [get_ports MII_1_tx_clk] set_property PACKAGE_PIN M21 [get_ports MII_1_tx_en] |
<!-- optional chapter separate sections for different apps --> |
For SDK project creation, follow instructions from:
Xilinx default FSBL
U-Boot.elf is generated with PetaLinux. SDK/HSI is used to generate Boot.bin.
<!-- optional chapter --> |
Description currently not available.
No changes.
No changes.
/include/ "system-conf.dtsi" / { }; /* ETH PHY */ &gem0 { phy-mode = "mii"; status = "okay"; ethernet_phy0: ethernet-phy@0 { // compatible = "marvell,88e1510"; device_type = "ethernet-phy"; reg = <1>; }; }; &gem1 { phy-mode = "mii"; status = "okay"; local-mac-address = [00 0a 35 00 1e 01]; ethernet_phy1: ethernet-phy@1 { // compatible = "marvell,88e1510"; device_type = "ethernet-phy"; reg = <2>; }; }; /* RTC */ &i2c0 { rtc@56 { // Real Time Clock compatible = "rv3029c2"; reg = <0x56>; }; }; |
Activate:
Activate:
Script App to load init.sh from SD Card if available.
See: \os\petalinux\project-spec\meta-user\recipes-apps\startup\files
<!-- Add Description for other Software, for example SI CLK Builder ... --> |
No additional software is needed.
<!-- optional chapter for SDSoC only -remove sections, if not supported --> |
Description currently not available.
SDSoC platform includes 21 demo projects demonstrating optimization techniques for Standalone and Linux targets with HW acceleration or in SW for fast compilation and debug. These projects have been downloaded and installed into the SDSoC platform from https://github.com/Xilinx/SDSoC_Examples
There are 3 larger Linux demo projects demonstrating video processing with data I/O from file to file. Source code of these projects have been installed into this platform from the Xilinx SDSoC 2016.4 release:
These larger Linux demo projects demonstrate video processing with data I/O from file to file. Source code of these projects have been installed into this platform from demos present in the Xilinx SDSoC 2016.4 release.
Compilation steps in the SDSoC 2017.1 is identical to above described examples. File I/O demos support only the Linux target.
These three files use as an input larger video files. These files have to be present on the SD card as an input. Algorithms write output file to the SD card. These files can be visualized by YUV Player Deluxe and other players. To reduce size of the project, the video data files are not included.
Video input files can be found in the Xilinx SDSoC 2016.4 distribution:
This example shows how to use array partitioning to improve performance of a hardware function.
Key Concepts:
Keywords:
This is a simple vector increment example which demonstrates usage of AXI4-master interface for burst read and write.
Key Concepts:
This is a simple example of RGB to HSV conversion to demonstrate Custom Data Type usage in hardware accelerator. Xilinx HLS compiler supports custom data type to operate within the hardware function and also it acts as a memory interface between PL to DDR.
Key Concepts:
Keywords:
This is a simple example of matrix multiplication (Row x Col) to demonstrate random data access pattern.
Key Concepts:
Keywords:
This is a simple example to demonstrate inter dependence attribute using vertical convolution example. Using inter dependence attribute user can provide additional dependency details to compiler which allow compiler to perform unrolling/pipelining to get better performance.
Key Concepts:
Keywords:
This is a simple example of matrix multiplication with matrix addition (Out = (A x B) + C) to demonstrate direct connection which helps to achieve increasing in system parallelism and concurrency.
Key Concepts:
Keywords:
This example demonstrates how to use Scatter-Gather DMAs for data transfer to/from hardware accelerator.
Key Concepts:
Keywords:
This example demonstrates how to insert Simple DMAs for data transfer between User program and hardware accelerator.
Key Concepts:
Keywords:
This is a simple example of accessing full data from 2D array.
Key Concepts:
----------
This is a basic hello world kind of example which demonstrates how to achieve vector addition using hardware function.
Key Concepts:
Keywords:
This is a simple example of vector addition to demonstrate how to utilize both ports of Local Memory.
Key Concepts:
Keywords:
This example will demonstrate how to fuse two loops into one to improve the performance of a C/C++ hardware function.
Key Concepts:
Keywords:
This nearest neighbor example is to demonstrate how to achieve better performance using perfect loop.
Key Concepts:
Keywords:
This example demonstrates how loop pipelining can be used to improve the performance of a hardware function.
Key Concepts:
Keywords:
This is a simple example of matrix multiplication (Row x Col) to demonstrate how to achieve better pipeline II factor by loop reordering.
Key Concepts:
Keywords:
This is a simple example of accessing each row of data from 2D array.
Key Concepts:
Keywords:
This example demonstrates how to shift values in each clock cycle.
Key Concepts:
Keywords:
This is a simple example of matrix multiplication (Row x Col) to help developers learn systolic array based algorithm design. Note : Systolic array based algorithm design is well suited for FPGA.
Key Concepts:
Keywords:
This is a simple example which demonstrates sys_port usage.
Key Concepts:
Keywords:
This is a simple example of vector addition to demonstrate Wide Memory Access using structure data type of 128bit wide. Based on input argument type, sds++ compiler will figure out the memory interface datawidth of hardware accelerator.
Key Concepts:
Keywords:
This is a simple example of accessing window of data from 2D array.
Key Concepts:
Keywords:
Linux video processing application that reads input video from a file and writes out the output video to a file. Video processing includes Motion Adaptive Noise Reduction (MANR) followed by a Sobel filter for edge detection. You can run it by supplying a 1080p YUV422 file as input with limiting number of frames to a maximum of 20 frames.
Key Concepts:
Select the "File IO Video Processing" template an compile for Linux target as project te22. Copy result to root of SD card. Copy also the input file input.yuv (82 944 000 bytes) to the root of the SD card. Login and cd to /media Run demo from terminal or from display+keyboard by comman ./te22.elf ./input.yuv 20 3 ./output.yuv
The output.yuv file contains 20 frames of 1080p vido in YUV422 format with computed edges. Copy output.yuv file to PC and visualise it in yuvplayer (size 1920x1080 colour YUV422).
Linux video processing application that reads input video from a file and writes out the output video to a file. Video processing performs LK Dense Optical Flow over two Full HD frames video file. You can run it by supplying a 1080p YUV422 file route85_1920x1080.yuv as input.
Key Concept:s
Select the "File IO Dense Optical Flow" template an compile for Linux target as project te23. Copy result to root of SD card. Copy also the input file route85_1920x1080.yuv (8 294 400 bytes) to the root of the SD card. Login and cd to /media Run demo from terminal or from display+keyboard by command ./te23.elf
The OptFlow_1920x1080.yuv file is generated and stored on the SD card. It contains one 1080p frame in YUV422 format with computed dense optical flow vectors. Copy OptFlow_1920x1080.yuv file to PC and visualise it in yuvplayer (size 1920x1080 colour YUV422).
Linux video processing application that reads input video from a file and writes out the output video to a file. Video processing performs Stereo Block Matching to calculate depth in a single sample stereo video file desk_1280x720.yuv in YUV422 format as input and single frame Disparity_640x720.yuv in YUV422 format as output, indicating the depth of objects.
Key Concepts:
Select the "File IO Stereo Block Matching" template an compile for Linux target as project te24. Copy result to root of SD card. Copy also the input file desk_1280x720.yuv (1 843 200 bytes) to the root of the SD card. Login and cd to /media Run demo from terminal or from display+keyboard by command ./te24.elf
The Disparity_640x720.yuv file is generated and stored on the SD card. It contains one 640x720 frame in YUV422 format indicating the depth of objects. Copy Disparity_640x720.yuv file to PC and visualise it in yuvplayer (size 640x720 colour YUV422) The input file desk_1280x720.yuv can be visualised by yuvplayer (size 1280x720 colour YUV422). It contains side by side two colour frames from a stereo camera.
To get content of older revision got to "Change History" of this page and select older document revision number.
<!-- Generate new entry: 1:add new row below first 2:Copy Page Information Macro(date+user) Preview, Page Information Macro Preview 3.Update Metadate =Page Information Macro Preview+1 --> |
Date | Document Revision | Authors | Description |
---|---|---|---|
| Work in progress | ||
2017-09-11 | v.1 | Initial release | |
All |