Design Name is always "TE Series Name" + Design name, for example "TE0720 Test Board"
|
Important General Note:
|
Notes :
|
Refer to http://trenz.org/te0782-info for the current online version of this manual and other available documentation.
Notes :
|
|
Notes :
|
|
Notes :
|
|
Notes :
|
|
Notes :
|
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:
|
Design supports following carriers:
*used as reference |
Additional HW Requirements:
*used as reference |
Notes :
|
For general structure and usage of the reference design, see Project Delivery - AMD devices
|
|
Notes :
|
|
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:
Notes :
|
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>") |
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 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 |
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. |
use exported .xsa file from "<project folder>\prebuilt\hardware\<short name>" . Note: HW Export from Vivado GUI creates another path as default workspace.
The build images are located in the "<plnx-proj-root>/images/linux" directory
Configure the boot.scr file as needed, see Distro Boot with Boot.scr
copy u-boot.elf, system.dtb, image.ub 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>" |
This step depends on Xilinx Device/Hardware for Zynq-7000 series
for ZynqMP
for Microblaze
|
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 |
Note:
|
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
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 Boot.bin 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 u-boot TE::pr_program_flash -swapp hello_te0820 (optional) |
Note: Linux image will be included into Boot.bin with
Not used on this example.
Select QSPI as Boot Mode
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. |
Power On PCB
1. Zynq Boot ROM loads FSBL from SD/QSPI into OCM, 2. FSBL init PS, programs PL using the bitstream and loads U-boot from QSPI into DDR, 3. U-boot loads Linux (image.ub) from QSPI/... into DDR |
This step depends on Xilinx Device/Hardware for Zynq-7000 series 1. Zynq Boot ROM loads FSBL from SD/QSPI into OCM, 2. FSBL init the PS, programs the PL using the bitstream and loads U-boot from SD/QSPI into DDR, 3. U-boot loads Linux (image.ub) from SD/QSPI/... into DDR for ZynqMP??? 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 for Microblaze with Linux 1. FPGA Loads Bitfile from Flash, 2. MCS Firmware configure SI5338 and starts Microblaze, (only if mcs is available) 3. SREC Bootloader from Bitfile Firmware loads U-Boot into DDR (This takes a while), 4. U-boot loads Linux from QSPI Flash into DDR for native FPGA ... |
select COM Port
Win OS, see device manager, Linux OS see dmesg |grep tty (UART is *USB1) |
Linux Console shows up after boot up
Note: Wait until Linux boot finished |
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) |
Note:
|
Open Vivado HW-Manager and add VIO signal to dashboard (*.ltx located on prebuilt folder)
Note:
|
Note:
|
Activated interfaces:
|
set_property BITSTREAM.GENERAL.COMPRESS TRUE [current_design] set_property CONFIG_VOLTAGE 3.3 [current_design] set_property CFGBVS VCCO [current_design] |
################################################################################# # Eternet2 set_property PACKAGE_PIN C17 [get_ports ETH2_PHY_mdc] set_property PACKAGE_PIN B17 [get_ports ETH2_PHY_mdio_io] set_property PACKAGE_PIN AD20 [get_ports {ETH2_RGMII_rd[0]}] set_property PACKAGE_PIN AD19 [get_ports {ETH2_RGMII_rd[1]}] set_property PACKAGE_PIN AB20 [get_ports {ETH2_RGMII_rd[2]}] set_property PACKAGE_PIN AB19 [get_ports {ETH2_RGMII_rd[3]}] set_property PACKAGE_PIN AE20 [get_ports ETH2_RGMII_rx_ctl] set_property PACKAGE_PIN AD18 [get_ports ETH2_RGMII_rxc] set_property PACKAGE_PIN AA20 [get_ports {ETH2_RGMII_td[0]}] set_property PACKAGE_PIN Y20 [get_ports {ETH2_RGMII_td[1]}] set_property PACKAGE_PIN AA19 [get_ports {ETH2_RGMII_td[2]}] set_property PACKAGE_PIN AA18 [get_ports {ETH2_RGMII_td[3]}] set_property PACKAGE_PIN AC18 [get_ports ETH2_RGMII_tx_ctl] set_property PACKAGE_PIN AC19 [get_ports ETH2_RGMII_txc] set_property IOSTANDARD LVCMOS18 [get_ports ETH2*] set_property IOSTANDARD LVCMOS18 [get_ports ETH2_PHY_mdio_io] ################################################################################# set_property PACKAGE_PIN B12 [get_ports {ETH1_LED[0]}] set_property PACKAGE_PIN C12 [get_ports {ETH1_LED[1]}] set_property PACKAGE_PIN A15 [get_ports {ETH1_LED[2]}] set_property PACKAGE_PIN K15 [get_ports {ETH2_LED[0]}] set_property PACKAGE_PIN B16 [get_ports {ETH2_LED[1]}] set_property PACKAGE_PIN A17 [get_ports {ETH2_LED[2]}] set_property IOSTANDARD LVCMOS18 [get_ports ETH1*] #set_property IOSTANDARD LVCMOS18 [get_ports ETH2*] ################################################################################# set_property IOSTANDARD LVCMOS18 [get_ports SYS_eth1_clk125] set_property IOSTANDARD LVCMOS18 [get_ports SYS_eth1_config] set_property IOSTANDARD LVCMOS18 [get_ports SYS_eth2_clk125] set_property IOSTANDARD LVCMOS18 [get_ports SYS_eth2_config] set_property PACKAGE_PIN E16 [get_ports SYS_eth1_clk125] set_property PACKAGE_PIN F14 [get_ports SYS_eth1_config] set_property PACKAGE_PIN F15 [get_ports SYS_eth2_clk125] set_property PACKAGE_PIN E15 [get_ports SYS_eth2_config] #------------------------------------------------------------------------------- #set_property IDELAY_VALUE "20" [get_cells -hier -filter {name =~ *gmii_to_rgmii/*delay_rgmii_rx_ctl }] #set_property IDELAY_VALUE "20" [get_cells -hier -filter {name =~ *gmii_to_rgmii/*delay_rgmii_rxd* }] #------------------------------------------------------------------------------- #set_property IODELAY_GROUP "grp1" [get_cells -hier -filter {name =~ *gmii_to_rgmii/*delay_rgmii_rx_ctl }] #set_property IODELAY_GROUP "grp1" [get_cells -hier -filter {name =~ *gmii_to_rgmii/*delay_rgmii_rxd* }] create_clock -add -name rgmii_rxc -period 8.000 [get_ports ETH2_RGMII_rxc] ################################################################################# # VIO false path #set_false_path -from [get_pins zsys_i/gmii_to_rgmii_0/U0/i_gmii_to_rgmii_block/zsys_gmii_to_rgmii_0_0_core/i_gmii_to_rgmii/i_gmii_to_rgmii/link_status_reg/C] -to [get_pins {zsys_i/vio_0/inst/PROBE_IN_INST/probe_in_reg_reg[7]/D}] #set_false_path -from [get_pins {zsys_i/gmii_to_rgmii_0/U0/i_gmii_to_rgmii_block/zsys_gmii_to_rgmii_0_0_core/i_gmii_to_rgmii/i_gmii_to_rgmii/clock_speed_reg[0]/C}] -to [get_pins {zsys_i/vio_0/inst/PROBE_IN_INST/probe_in_reg_reg[8]/D}] #set_false_path -from [get_pins zsys_i/gmii_to_rgmii_0/U0/i_gmii_to_rgmii_block/zsys_gmii_to_rgmii_0_0_core/i_gmii_to_rgmii/i_gmii_to_rgmii/duplex_status_reg/C] -to [get_pins {zsys_i/vio_0/inst/PROBE_IN_INST/probe_in_reg_reg[10]/D}] #set_false_path -from [get_pins {zsys_i/gmii_to_rgmii_0/U0/i_gmii_to_rgmii_block/zsys_gmii_to_rgmii_0_0_core/i_gmii_to_rgmii/i_gmii_to_rgmii/clock_speed_reg[1]/C}] -to [get_pins {zsys_i/vio_0/inst/PROBE_IN_INST/probe_in_reg_reg[9]/D}] ################################################################################# set_false_path -from [get_pins zsys_i/gmii_to_rgmii_0/U0/i_gmii_to_rgmii_block/zsys_gmii_to_rgmii_0_0_core/i_gmii_to_rgmii/gmii_to_rgmii_core_non_versal.i_gmii_to_rgmii/duplex_status_reg/C] -to [get_pins {zsys_i/vio_0/inst/PROBE_IN_INST/probe_in_reg_reg[10]/D}] set_false_path -from [get_pins zsys_i/gmii_to_rgmii_0/U0/i_gmii_to_rgmii_block/zsys_gmii_to_rgmii_0_0_core/i_gmii_to_rgmii/gmii_to_rgmii_core_non_versal.i_gmii_to_rgmii/link_status_reg/C] -to [get_pins {zsys_i/vio_0/inst/PROBE_IN_INST/probe_in_reg_reg[7]/D}] set_false_path -from [get_pins {zsys_i/gmii_to_rgmii_0/U0/i_gmii_to_rgmii_block/zsys_gmii_to_rgmii_0_0_core/i_gmii_to_rgmii/gmii_to_rgmii_core_non_versal.i_gmii_to_rgmii/clock_speed_reg[0]/C}] -to [get_pins {zsys_i/vio_0/inst/PROBE_IN_INST/probe_in_reg_reg[8]/D}] set_false_path -from [get_pins {zsys_i/gmii_to_rgmii_0/U0/i_gmii_to_rgmii_block/zsys_gmii_to_rgmii_0_0_core/i_gmii_to_rgmii/gmii_to_rgmii_core_non_versal.i_gmii_to_rgmii/clock_speed_reg[1]/C}] -to [get_pins {zsys_i/vio_0/inst/PROBE_IN_INST/probe_in_reg_reg[9]/D}] |
Note:
|
For Vitis project creation, follow instructions from:
---------------------------------------------------------- FPGA Example ---------------------------------------------------------- scuMCS Firmware to configure SI5338 and Reset System. srec_spi_bootloaderTE modified 2022.2 SREC Bootloader to load app or second bootloader from flash into DDR Descriptions:
xilisf_v5_11TE modified 2022.2 xilisf_v5_11
---------------------------------------------------------- Zynq Example: ---------------------------------------------------------- fsblTE modified 2022.2 FSBL General:
Module Specific:
---------------------------------------------------------- ZynqMP Example: ---------------------------------------------------------- zynqmp_fsblTE modified 2022.2 FSBL General:
Module Specific:
zynqmp_pmufwXilinx default PMU firmware. ---------------------------------------------------------- General Example: ---------------------------------------------------------- hello_te0820Hello TE0820 is a Xilinx Hello World example as endless loop instead of one console output. u-bootU-Boot.elf is generated with PetaLinux. Vitis is used to generate Boot.bin. |
Template location: "<project folder>\sw_lib\sw_apps\"
TE modified 2020.2 FSBL
Changes:
TE modified 2020.2 FSBL
Changes:
Hello TE0782 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.
Note:
|
For PetaLinux installation and project creation, follow instructions from:
Start with petalinux-config or petalinux-config --get-hw-description
Changes:
Start with petalinux-config -c u-boot
Changes:
Change bsp.cfg in path <.. petalinux\project-spec\meta-user\recipes-bsp\u-boot\files>:
CONFIG_SYS_CONFIG_NAME="platform-top" CONFIG_BOOT_SCRIPT_OFFSET=0x520000 |
Change system-user.dtsi in path < .. petalinux\project-spec\meta-user\recipes-bsp\device-tree\files>:
/include/ "system-conf.dtsi" / { }; /* QSPI PHY */ &qspi { #address-cells = <1>; #size-cells = <0>; status = "okay"; flash0: flash@0 { compatible = "jedec,spi-nor"; reg = <0x0>; #address-cells = <1>; #size-cells = <1>; }; }; /* ETH PHY ETH0 */ &gem0{ status = "okay"; phy-handle = <&phy0>; xlnx,has-mdio = <0x1>; nvmem-cells = <ð0_addr>; nvmem-cell-names = "mac-address"; mdio { #address-cells = <1>; #size-cells = <0>; phy0: phy@1 { compatible = "marvell,88e1510"; device_type = "ethernet-phy"; reg = <1>; marvell,reg-init = <0x3 0x10 0x0000 0x0501 0x3 0x11 0x0000 0x4415>; }; }; }; /* ETH PHY ETH1 RGMII over PL */ &gem1 { reg = <0xe000c000 0x1000>; phy-handle = <&phy1>; gmii2rgmii-phy-handle = <&gmii_to_rgmii_0>; nvmem-cells = <ð1_addr>; nvmem-cell-names = "mac-address"; compatible = "cdns,zynq-gem", "cdns,gem"; clock-names = "pclk", "hclk", "tx_clk"; clocks = <&clkc 31>, <&clkc 31>, <&clkc 14>; phy-mode = "gmii"; status = "okay"; ps7_ethernet_1_mdio: mdio { #address-cells = <1>; #size-cells = <0>; gmii_to_rgmii_0: gmii_to_rgmii_0@8 { compatible = "xlnx,gmii-to-rgmii-1.0"; phy-handle = <&phy1>; reg = <8>; }; phy1: ethernet-phy@0 { compatible = "marvell,88e1510"; device_type = "ethernet-phy"; reg = <1>; marvell,reg-init = <0x3 0x10 0x0000 0x0501 0x3 0x11 0x0000 0x4415>; } ; }; }; /* USB 0 PHY */ /{ usb_phy0: usb_phy@0 { compatible = "ulpi-phy"; #phy-cells = <0>; reg = <0xe0002000 0x1000>; view-port = <0x0170>; drv-vbus; }; }; &usb0 { dr_mode = "host"; usb-phy = <&usb_phy0>; } ; /* USB 1 PHY */ /{ usb_phy1: usb_phy@0 { compatible = "ulpi-phy"; #phy-cells = <0>; reg = <0xe0003000 0x1000>; view-port = <0x0170>; drv-vbus; }; }; &usb1 { dr_mode = "host"; usb-phy = <&usb_phy1>; } ; /* RTC over I2C1 */ &i2c1 { rtc@6F { // Real Time Clock compatible = "isl12022"; reg = <0x6F>; }; //MAC EEPROM U24 eeprom: eeprom@51 { compatible = "microchip,24aa025", "atmel,24c02"; reg = <0x51>; #address-cells = <1>; #size-cells = <1>; eth0_addr: eth-mac-addr@FA { reg = <0xFA 0x06>; }; }; //MAC EEPROM U22 eeprom50: eeprom@50 { compatible = "microchip,24aa025", "atmel,24c02"; reg = <0x50>; #address-cells = <1>; #size-cells = <1>; eth1_addr: eth-mac-addr@FA { reg = <0xFA 0x06>; }; }; }; |
Start with petalinux-config -c kernel
Changes:
Start with petalinux-config -c rootfs
Changes:
CONFIG_i2c-tools=y
CONFIG_auto-login=y
CONFIG_RTC_DRV_ISL12022=y
for Zynq-7000 series
for ZynqMP???
for Microblaze with Linux
|
See "<project folder>\os\petalinux\project-spec\meta-user\recipes-bsp\embeddedsw"
te_* files are identical to files in "<project folder>\sw_lib\sw_apps\zynqmp_fsbl\src" except for the PLL files (SI5345) which depend on PLL revision. The PLL files may have to be copied again manually into the appropriate petalinux folder "<project folder>\os\petalinux\project-spec\meta-user\recipes-bsp\embeddedsw\fsbl-firmware\git\lib\sw_apps\zynqmp_fsbl\src" |
Note: |
No additional software is needed.
File location "<project folder>\misc\Si5338\Si5338-*.slabtimeproj"
General documentation how you work with this project will be available on Si5338
To get content of older revision go to "Change History" of this page and select older document revision number.
|
|
|
|