MicroBlaze Design with Hello TE0725 example in endless loop running in HyperRAM (OpenHBMC IP).
Refer to http://trenz.org/te0725-info for the current online version of this manual and other available documentation.
Date | Vivado | Project Built | Authors | Description |
---|---|---|---|---|
2024-07-03 | 2023.2 | TE0725-test_board_noprebuilt-vivado_2023.2-build_4_20240703150642.zip TE0725-test_board-vivado_2023.2-build_4_20240703150642.zip | Waldemar Hanemann |
|
2022-08-29 | 2021.2 | TE0725-test_board_noprebuilt-vivado_2021.2-build_15_20220829124226.zip TE0725-test_board-vivado_2021.2-build_15_20220829124226.zip | Waldemar Hanemann |
|
2020-04-20 | 2019.2 | TE0725-test_board_noprebuilt-vivado_2019.2-build_10_20200420092827.zip TE0725-test_board-vivado_2019.2-build_10_20200420092815.zip | John Hartfiel |
|
2018-08-09 | 2018.2 | TE0725-test_board_noprebuilt-vivado_2018.2-build_02_20180809122533.zip TE0725-test_board-vivado_2018.2-build_02_20180809122018.zip | John Hartfiel |
|
2018-03-18 | 2017.4 | TE0725-test_board_noprebuilt-vivado_2017.4-build_07_20180319171220.zip TE0725-test_board-vivado_2017.4-build_07_20180319171209.zip | John Hartfiel |
|
2018-03-16 | 2017.4 | TE0725-test_board_noprebuilt-vivado_2017.4-build_07_20180316163402.zip TE0725-test_board-vivado_2017.4-build_07_20180316163351.zip | John Hartfiel |
|
Issues | Description | Workaround | To be fixed version |
---|---|---|---|
No known issues | --- | --- | --- |
Software | Version | Note |
---|---|---|
Vitis | 2023.2 | needed, Vivado is included into Vitis installation |
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 | DDR | QSPI Flash | EMMC | Others | Notes |
---|---|---|---|---|---|---|---|
TE0725-03-15-1C | 15_1c | REV03|REV02|REV01 | NA | 32MB | NA | 8MB HypeRAM | NA |
TE0725-03-35-2C | 35_2c | REV03|REV02|REV01 | NA | 32MB | NA | 8MB HypeRAM | NA |
TE0725-03-100-2C | 100_2c | REV03|REV02|REV01 | NA | 32MB | NA | 8MB HypeRAM | NA |
TE0725-03-100-2CF | 100_2c | REV03|REV02|REV01 | NA | 32MB | NA | 8MB HypeRAM | POF assembled |
TE0725-03-100-2I9 | 100_2i | REV03|REV02|REV01 | NA | 32MB | NA | 8MB HypeRAM | NA |
TE0725-03-35-2I | 35_2i | REV03|REV02|REV01 | NA | 32MB | NA | 8MB HypeRAM | NA |
TE0725-04-21C-1-A | 15_1c | REV04 | NA | 32MB | NA | 8MB HypeRAM | NA |
TE0725-04-42C-1-A | 35_2c | REV04 | NA | 32MB | NA | 8MB HypeRAM | NA |
TE0725-04-72C-1-A | 100_2c | REV04 | NA | 32MB | NA | 8MB HypeRAM | NA |
TE0725-04-72C-1-F | 100_2c | REV04 | NA | 32MB | NA | 8MB HypeRAM | POF assembled |
TE0725-04-72I-1-B | 100_2i | REV04 | NA | 32MB | NA | 8MB HypeRAM | NA |
Design supports following carriers:
Carrier Model | Notes |
---|---|
--- |
*used as reference
Additional HW Requirements:
Additional Hardware | Notes |
---|---|
TE0790 JTAG Programmer | It's not recommended to use TE0790 for power supply( TE0790 TRM#PowerandPower-OnSequence) |
External power supply |
*used as reference
For general structure and of the reference design, see Project Delivery - AMD devices
Type | Location | Notes |
---|---|---|
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_lib | Additional Software Template for Vitis and apps_list.csv with settings automatically for Vitis app generation |
Type | Location | Notes |
---|---|---|
-- | -- | -- |
File | File-Extension | Description |
---|---|---|
BIT-File | *.bit | FPGA (PL Part) Configuration File |
DebugProbes-File | *.ltx | Definition File for Vivado/Vivado Labtools Debugging Interface |
Debian SD-Image | *.img | Debian Image for SD-Card |
Diverse Reports | --- | Report files in different formats |
Hardware-Platform-Specification-Files | *.xsa | Exported Vivado Hardware Specification for Vitis and PetaLinux |
LabTools Project-File | *.lpr | Vivado Labtools Project File |
MCS-File | *.mcs | Flash Configuration File with Boot-Image (MicroBlaze or FPGA part only) |
MMI-File | *.mmi | File with BRAM-Location to generate MCS or BIT-File with *.elf content (MicroBlaze only) |
Software-Application-File | *.elf | Software Application for Zynq or MicroBlaze Processor Systems |
Reference Design is only usable with the specified Vivado/Vitis/PetaLinux version. Do never use different Versions of AMD Software for the same Project.
Reference Design is available on:
Reference Design is available with and without prebuilt files. It's recommended to use TE prebuilt files for first lunch.
Trenz Electronic provides a tcl based built environment based on AMD 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 AMD 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>")
Run _create_win_setup.cmd/_create_linux_setup.sh 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):
optional for manual changes: Select correct device and Vivado 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
Create hardware description file (.xsa file) for PetaLinux project and export to prebuilt folder
TE::hw_build_design -export_prebuilt
Using Vivado GUI is the same, except file export to prebuilt folder.
Generate Programming Files with Vitis
TE::sw_run_vitis -all TE::sw_run_vitis (optional; Start Vitis from Vivado GUI or start with TE Scripts on Vivado TCL)
Note: Scripts generate applications and bootable files, which are defined in "sw_lib\apps_list.csv"
App from Firmware folder will be add into BlockRAM. If you add other app, you must select *.elf
manually on Vivado
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.
Reference Design is also available with prebuilt files. It's recommended to use TE prebuilt files for first launch.
AMD documentation for programming and debugging: Vivado/SDK/SDSoC-Xilinx Software Programming and Debugging
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
Option for *.mcs file on QSPI Flash
Open Vivado Project with "vivado_open_existing_project_guimode.cmd" or if not created, create with "vivado_create_project_guimode.cmd"
TE::pr_program_flash -swapp hello_te0725_bootldr
Not used on this Example.
1. FPGA Loads Bitfile from Flash
3. Hello Trenz will be run on UART console.
info: Do not reboot, if Bitfile programming over JTAG is used as programming method.
Open Serial Console (e.g. putty) Hello TE0725 will run on endless loop.
Power On PCB (Do not restart, if you use Bitfile programming)
set_property BITSTREAM.GENERAL.COMPRESS TRUE [current_design] set_property BITSTREAM.CONFIG.CONFIGRATE 50 [current_design] set_property CONFIG_VOLTAGE 3.3 [current_design] set_property CFGBVS VCCO [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]
set_property PACKAGE_PIN T5 [get_ports clk_crystal_i] set_property IOSTANDARD LVCMOS33 [get_ports clk_crystal_i]
set_property PACKAGE_PIN A13 [get_ports HB_CLK0_0] set_property PACKAGE_PIN A14 [get_ports HB_CLK0n_0] set_property PACKAGE_PIN E17 [get_ports {HB_dq_0[0]}] set_property PACKAGE_PIN B17 [get_ports {HB_dq_0[1]}] set_property PACKAGE_PIN F18 [get_ports {HB_dq_0[2]}] set_property PACKAGE_PIN F16 [get_ports {HB_dq_0[3]}] set_property PACKAGE_PIN G17 [get_ports {HB_dq_0[4]}] set_property PACKAGE_PIN D18 [get_ports {HB_dq_0[5]}] set_property PACKAGE_PIN B18 [get_ports {HB_dq_0[6]}] set_property PACKAGE_PIN A16 [get_ports {HB_dq_0[7]}] set_property PACKAGE_PIN E18 [get_ports HB_RWDS_0] set_property PACKAGE_PIN D17 [get_ports HB_CS1n_0] set_property PACKAGE_PIN J17 [get_ports HB_RSTn_0] #set_property PACKAGE_PIN A18 [get_ports HB_CS0n_0 ] #set_property PACKAGE_PIN J18 [get_ports HB_INTn_0 ] #set_property PACKAGE_PIN C17 [get_ports HB_RSTOn_0] # # FPGA Pin Voltage assignment # set_property IOSTANDARD LVCMOS18 [get_ports HB_CLK0_0] set_property IOSTANDARD LVCMOS18 [get_ports HB_CLK0n_0] set_property IOSTANDARD LVCMOS18 [get_ports {HB_dq_0[*]}] set_property IOSTANDARD LVCMOS18 [get_ports HB_CS1n_0] set_property IOSTANDARD LVCMOS18 [get_ports HB_RSTn_0] set_property IOSTANDARD LVCMOS18 [get_ports HB_RWDS_0] set_property SLEW FAST [get_ports {HB_*}] set_property DRIVE 16 [get_ports {HB_*}] #set_property IOSTANDARD LVCMOS18 [get_ports HB_CS0n_0] #set_property IOSTANDARD LVCMOS18 [get_ports HB_INTn_0] #set_property IOSTANDARD LVCMOS18 [get_ports HB_RSTOn_0] #set_property PULLUP true [get_ports HB_RSTOn_0] #set_property PULLUP true [get_ports HB_INTn_0] set_property PULLUP TRUE [get_ports {HB_CS1n_0}] set_property PULLDOWN TRUE [get_ports {HB_RSTn_0}] # #Hyperbus Clock - change according to clk pin on PLL # create_generated_clock -name clk_0 -source [get_pins msys_i/clk_wiz_1/inst/mmcm_adv_inst/CLKIN1] -master_clock sys_clock [get_pins msys_i/clk_wiz_1/inst/mmcm_adv_inst/CLKOUT0] create_generated_clock -name clk_90 -source [get_pins msys_i/clk_wiz_1/inst/mmcm_adv_inst/CLKIN1] -master_clock sys_clock [get_pins msys_i/clk_wiz_1/inst/mmcm_adv_inst/CLKOUT1] create_generated_clock -name clk_180 -source [get_pins msys_i/clk_wiz_1/inst/mmcm_adv_inst/CLKIN1] -master_clock sys_clock [get_pins msys_i/clk_wiz_1/inst/mmcm_adv_inst/CLKOUT2] # #100Mhz clock freqeuncy - change accordingly # set hbus_freq_ns 10 set dqs_in_min_dly -1 set dqs_in_max_dly 1 set HB_dq_ports [get_ports HB_dq_0[*]] # #Create RDS clock and RDS virtual clock # create_clock -period $hbus_freq_ns -name rwds_clk [get_ports HB_RWDS_0] create_clock -period $hbus_freq_ns -name virt_rwds_clk # #Input Delay Constraint - HB_RWDS-HB_DQ # set_input_delay -clock [get_clocks virt_rwds_clk] -max ${dqs_in_max_dly} ${HB_dq_ports} set_input_delay -clock [get_clocks virt_rwds_clk] -clock_fall -max ${dqs_in_max_dly} ${HB_dq_ports} -add_delay set_input_delay -clock [get_clocks virt_rwds_clk] -min ${dqs_in_min_dly} ${HB_dq_ports} -add_delay set_input_delay -clock [get_clocks virt_rwds_clk] -clock_fall -min ${dqs_in_min_dly} ${HB_dq_ports} -add_delay set_multicycle_path -setup -end -rise_from [get_clocks virt_rwds_clk] -rise_to [get_clocks rwds_clk] 0 set_multicycle_path -setup -end -fall_from [get_clocks virt_rwds_clk] -fall_to [get_clocks rwds_clk] 0 set_false_path -fall_from [get_clocks virt_rwds_clk] -rise_to [get_clocks rwds_clk] -setup set_false_path -rise_from [get_clocks virt_rwds_clk] -fall_to [get_clocks rwds_clk] -setup set_false_path -fall_from [get_clocks virt_rwds_clk] -fall_to [get_clocks rwds_clk] -hold set_false_path -rise_from [get_clocks virt_rwds_clk] -rise_to [get_clocks rwds_clk] -hold #set_false_path -from [get_clocks clk_0] -to [get_clocks rwds_clk] #set_false_path -from [get_clocks rwds_clk] -to [get_clocks clk_0] # #Output Delay Constraint - HB_CLK0-HB_DQ # create_generated_clock -name HB_CLK0_0 -source [get_pins */*/*/U_IO/U_CLK0/dq_idx_[0].ODDR_inst/C] -multiply_by 1 -invert [get_ports HB_CLK0_0] set_output_delay -clock [get_clocks HB_CLK0_0] -min -1.000 ${HB_dq_ports} set_output_delay -clock [get_clocks HB_CLK0_0] -max 1.000 ${HB_dq_ports} set_output_delay -clock [get_clocks HB_CLK0_0] -min -1.000 ${HB_dq_ports} -clock_fall -add_delay set_output_delay -clock [get_clocks HB_CLK0_0] -max 1.000 ${HB_dq_ports} -clock_fall -add_delay set_false_path -from [get_pins */*/*/U_HBC/*/dq_io_tri_reg/C] -to ${HB_dq_ports} #set_false_path -from * -to [get_pins */*/inst/*/i_iavs0_270_rstn_1_reg/CLR] #set_false_path -from * -to [get_pins */*/inst/*/i_iavs0_270_rstn_2_reg/CLR] #set_false_path -from * -to [get_pins */*/inst/*/i_iavs0_270_rstn_3_reg/CLR] set_false_path -from [get_clocks rwds_clk] -to [get_clocks -of_objects [get_pins msys_i/clk_wiz_1/inst/mmcm_adv_inst/CLKOUT0]] set_false_path -from [get_clocks virt_rwds_clk] -to [get_clocks rwds_clk]
For SDK project creation, follow instructions from:
Template location: "<project folder>\sw_lib\sw_apps\"
Trenz Hello TE0725 example as endless loop. Output on console.
Additionally running a Low Level EEPROM IIC example.
Template location: \sw_lib\sw_apps\hello_te0725
The printed Text can be modified.
TE modified SPI Bootloader from Henrik Brix Andersen.
Bootloader to load app or second bootloader from flash into DDR.
Here it loads the hello_te0725.elf from QSPI-Flash to RAM.
Descriptions:
No additional software is needed.
To get content of older revision got to "Change History" of this page and select older document revision number.
Date | Document Revision | Authors | Description |
---|---|---|---|
Error rendering macro 'page-info' Ambiguous method overloading for method jdk.proxy244.$Proxy3578#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.proxy244.$Proxy3578#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.proxy244.$Proxy3578#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] |
|
2022-08-29 | v14 | Waldemar Hanemann |
|
2020-04-27 | v.13 | John Hartfiel |
|
2020-04-20 | v.12 | John Hartfiel |
|
2018-08-09 | v.9 | John Hartfiel |
|
2018.06.05 | v.8 | John Hartfiel |
|
2018-03-16 | v.5 | John Hartfiel |
|
2018-03-12 | v.1 | Error rendering macro 'page-info' Ambiguous method overloading for method jdk.proxy244.$Proxy3578#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.proxy244.$Proxy3578#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] |
Please also note our data protection declaration at https://www.trenz-electronic.de/en/Data-protection-Privacy
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.
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.
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.
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.
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
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.
Error rendering macro 'page-info'
Ambiguous method overloading for method jdk.proxy244.$Proxy3578#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]