Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Scroll Title
anchorTable_AHW
titleAdditional Hardware

Scroll Table Layout
orientationportrait
sortDirectionASC
repeatTableHeadersdefault
style
widths
sortByColumn1
sortEnabledfalse
cellHighlightingtrue

Additional HardwareNotes
Micro USB Cable for JTAG/UART
CoolerIt's recommended to use cooler on Zynqmp RFSoC  device
SMA male connector cableSome ADC inputs/DAC outouts have the SMA connector
SMT UFL female connector cableSome ADC inputs/DAC outouts have the SMT UFL connector
Ethernet cable
SD card16GB
Signal generator (optional)
Oscilloscope (optional)
12V power supplyIt is recommended to use a power supply with 3A output current capability 


...

Scroll Title
anchorTable_PF
titlePrebuilt files (only on ZIP with prebult content)

Scroll Table Layout
orientationportrait
sortDirectionASC
repeatTableHeadersdefault
style
widths
sortByColumn1
sortEnabledfalse
cellHighlightingtrue

File

File-Extension

Description

BIF-File*.bifFile with description to generate Bin-File
BIN-File*.binFlash Configuration File with Boot-Image (Zynqmp RFSoC-FPGAs)
BIT-File*.bitFPGA (PL Part) Configuration File
DebugProbes-File*.ltxDefinition 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*.xsaExported Vivado Hardware Specification for Vitis and PetaLinux
LabTools Project-File*.lprVivado 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)
OS-Image*.ubImage with Linux Kernel (On Petalinux optional with Devicetree and RAM-Disk)
Software-Application-File*.elfSoftware Application for Zynqmp RFSoC or MicroBlaze Processor Systems

SREC-File

*.srec

Converted Software Application for MicroBlaze Processor Systems
Clock Builder Pro project file*.slabtimeprojDefines the necessary clock frequencies for the PLLs on the RFSoC module and carrier board


...

Software Setup

Download RF Analyzer GUI from the following link and install it.

Hardware Setup

The Hardware contains of a TE0835 module and TEB0835 carrier board and has 8 ADC inputs and 8 DAC outputs.

  1. Plug the TE0835 module on the TEB0835 carrier board
  2. Install the cooler on the RFSoC
  3. Connect the micro USB cable to the J29 connector
  4. Plug the 12V power supply cable to the J19 connector
  5. Plug the prepared SD card on the SD card socket (J28)
  6. Connect a cable with SMA or SMT connector to one of the DAC connector( for example DAC0 J9) and feed it back to the related ADC input (for example ADC0 J1)
  7. (optional) A signal generator can be used to feed desired sinal to ADC input.
  8. (optional) An oscilloscope can be used to monitor the output signal of DAC.

...

DAC6_OUT

...


Design Flow

Page properties
hiddentrue
idComments
Notes :
  • Basic Design Steps

  • Add/ Remove project specific description


Note

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

  1. _create_win_setup.cmd/_create_linux_setup.sh and follow instructions on shell:
    Image Added
  2. Press 0 and enter to start "Module Selection Guide"
  3. (optional Win OS) Generate Virtual Drive or use short directory  for the reference design (for example x:\<design name>)
  4. Create Project (follow instruction of the product selection guide), settings file will be configured automatically during this process)
    1. (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 alsoTE Board Part Files
  5. Create XSA and export to prebuilt folder
    1. Run on Vivado TCL: TE::hw_build_design -export_prebuilt
      Note: Script generate design and export files into \prebuilt\hardware\<short dir>. Use GUI is the same, except file export to prebuilt folder
  6. Create Linux (bl31.elf, uboot.elf and image.ub) with exported XSA
    1. XSA is exported to "prebuilt\hardware\<short name>"
      Note: HW Export from Vivado GUI create another path as default workspace.
    2. Create Linux images on VM, see PetaLinux KICKstart
      1. Use TE Template from /os/petalinux
  7. Add Linux files (bl31.elf, uboot.elf and image.ub) to prebuilt folder
    1. "prebuilt\os\petalinux\<ddr size>" or "prebuilt\os\petalinux\<short name>"
  8. Generate Programming Files with Vitis
    1. Run on Vivado TCL: TE::sw_run_vitis -all
      Note: Scripts generate applications and bootable files, which are defined in "sw_lib\apps_list.csv"
    2. (alternative) Start SDK with Vivado GUI or start with TE Scripts on Vivado TCL: TE::sw_run_vitis
      Note:  TCL scripts generate also platform project, this must be done manuelly in case GUI is used. See Vitis

Launch

...

Page properties
hiddentrue
idComments
Notes

Note:

  • Basic Design Steps

  • Add/ Remove project specific description
    • Programming and Startup procedure

    Programming

    Note

    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 Xilinx Design Flow.

    See also:

    ...

    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

    Get prebuilt boot binaries

    1. _create_win_setup.cmd

    ...

    1. /_create_linux_setup.sh

    ...

    1. 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 foler>/_binaries_<Artikel Name>) with subfolder (boot_<app name>) for different applications will be generated

    QSPI

    Optional for Boot.bin on QSPI Flash and image.ub on SD.

    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"
    3. Type on Vivado TCL Console: TE::pr_program_flash -swapp u-boot
      Note: To program with SDK/Vivado GUI, use special FSBL (zynqmp_fsbl_flash) on setup
                optional "TE::pr_program_flash -swapp hello_te0835" possible
    4. Copy image.ub on SD-Card
      • use files from (<project foler>/_binaries_<Articel Name>)/boot_linux from generated binary folder,see: Get prebuilt boot binaries
      • or use prebuilt file location, see <design_name>/prebuilt/readme_file_location.txt
    5. Insert SD-Card

    SD

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

    JTAG

    Not used on this Example.

    Usage

    1. Prepare HW like described on section TE0835 Test Board#Hardware Setup
    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.
    4. Power On PCB
      Note: 1. Zynqmp RFSoC Boot ROM loads FSBL from SD into OCM, 2. FSBL loads U-boot from SD into DDR, 3. U-boot load Linux from SD into DDR

    Linux

    1. Open Serial Console (e.g. putty)
      1. Speed: 115200
      2. 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 For Linux Login use:
      1. User Name: root
      2. Password: root
    3. You can use Linux shell now.
      1. I2C 0 Bus type: i2cdetect -y -r 0
      2. I2C 1 Bus type: i2cdetect -y -r 1
      3. RTC check: dmesg | grep rtc
      4. ETH0 works with udhcpc
      5. USB type  "lsusb" or connect USB2.0 device
    4. Option Features
      1. Webserver to get access to Zynqmp RFSoC
        1. insert IP on web browser to start web interface
      2. init.sh scripts
        1. add init.sh script on SD, content will be load automatically on startup (template included in ./misc/SD)

    Vivado HW Manager

    Page properties
    hiddentrue
    idComments

    Note:

    • Add picture of HW Manager

    • add notes for the signal either groups or topics, for example:

      Control:

      • add controllable IOs with short notes..

      Monitoring:

      • add short notes for signals which will be monitored only
      • SI5338 CLKs:
        • Set radix from VIO signals to unsigned integer. Note: Frequency Counter is inaccurate and displayed unit is Hz
        • expected CLK Frequ:...

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

    • Monitoring:
      • The output frequency  of MMCM blocks can be monitored.
        • Set radix from VIO signals to unsigned integer.
        • The tempreature of ARM processor and FPGA can be measured too.
    Scroll Title
    anchorFigure_VHM
    titleVivado Hardware Manager
    Image Added

    Software Setup

    Download RF Analyzer GUI from the following link and install it.

    Hardware Setup

    The Hardware contains of a TE0835 module and TEB0835 carrier board and has 8 ADC inputs and 8 DAC outputs.

    1. Plug the TE0835 module on the TEB0835 carrier board
    2. Install the cooler on the RFSoC
    3. Connect the micro USB cable to the J29 connector
    4. Plug the 12V power supply cable to the J19 connector
    5. Plug the prepared SD card on the SD card socket (J28)
    6. Connect a cable with SMA or UFL connector to one of the DAC connector( for example DAC0 J9) and feed it back to the related ADC input (for example ADC0 J1)
    7. (optional) A signal generator can be used to feed desired sinal to ADC input.
    8. (optional) An oscilloscope can be used to monitor the output signal of DAC.
    RF Analyzer GUIADC/DACBoardDesignatorPin NamePin NumberConnected withBoardPin NameDesignatorFootprint
    ADC Tile 0ADC 01TE0835U1ADC0_P/ADC0_NAK2/AK1B2BTEB0835ADC0_P/ADC0_NJ1SMA
    ADC Tile 0ADC 23TE0835U1ADC1_P/ADC1_NAH2/AH1B2BTEB0835ADC1_P/ADC1_NJ2UFL
    ADC Tile 1ADC 01TE0835U1ADC2_P/ADC2_NAF2/AF1B2BTEB0835ADC2_P/ADC2_NJ3SMA
    ADC Tile 1ADC 23TE0835U1ADC3_P/ADC3_NAD2/AD1B2BTEB0835ADC3_P/ADC3_NJ4UFL
    ADC Tile 2ADC 01TE0835U1ADC4_P/ADC4_NAB2/AB1B2BTEB0835ADC4_P/ADC4_NJ5SMA
    ADC Tile 2ADC 23TE0835U1ADC5_P/ADC5_NY2/Y1B2BTEB0835ADC5_P/ADC5_NJ6UFL
    ADC Tile 3ADC 01TE0835U1ADC6_P/ADC6_NV2/V1B2BTEB0835ADC6_P/ADC6_NJ7SMA
    ADC Tile 3ADC 23TE0835U1ADC7_P/ADC7_NT2/T1B2BTEB0835ADC7_P/ADC7_NJ8UFL
    DAC Tile 0DAC 0TE0835U1DAC0_P/DAC0_NN2/N1B2BTEB0835DAC0_P/DAC0_NJ9SMA
    DAC Tile 0DAC 1TE0835U1DAC1_P/DAC1_NL2/L1B2BTEB0835DAC1_P/DAC1_NJ10UFL
    DAC Tile 0DAC 2TE0835U1DAC2_P/DAC2_NJ2/J1B2BTEB0835DAC2_P/DAC2_NJ11SMA
    DAC Tile 0DAC 3TE0835U1DAC3_P/DAC3_NG2/G1B2BTEB0835DAC3_P/DAC3_NJ12UFL
    DAC Tile 1DAC 0TE0835U1DAC4_P/DAC4_NE2/E1B2BTEB0835DAC4_P/DAC4_NJ13UFL
    DAC Tile 1DAC 1TE0835U1DAC5_P/DAC5_NC2/C1B2BTEB0835DAC5_P/DAC5_NJ14UFL
    DAC Tile 1DAC 2TE0835U1DAC6_P/DAC6_NB4/A4B2BTEB0835DAC6_P/DAC6_NJ15UFL
    DAC Tile 1DAC 3TE0835U1DAC7_P/DAC7_NB6/A6B2BTEB0835DAC7_P/DAC7_NJ16UFL


    RF Analyzer

    1. Open the RF Analyzer GUI
    2. Click on Connect
    3. Adjust the desired JTAG frequency (for example 30MHZ)
    4. Give the generated bitstream file path
    5. Click on Download Bitstream on the FPGA
    6. When downloading is finished, click on Select Target
    7. After the initilalisation, all ADCs/DACs tiles are visible
    8. Click on desired DAC tile and choose a DAC (for example DAC0)
    9. Adjust the desired DAC properties (for example output frequency)
    10. Click on Generate to generate the signal in output of DAC
    11. Click on the related ADC tile and choose the related ADC (for example ADC0)
    12. Click on Acquire to aqcuire the input signal
    13. The spectum of the DAC output signal can be seen now. The signal can be visible in time domain too.
      1. Tip: In menu Window click on Multiview to see all of DACs and ADCs simultaneously.


    Expand
    titleexample

    Image Added


    Expand
    titleDACs

    Image Added


    Expand
    titleADCs

    Image Added

    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

    1. _create_win_setup.cmd/_create_linux_setup.sh and follow instructions on shell:
      Image Removed
    2. Press 0 and enter to start "Module Selection Guide"
    3. (optional Win OS) Generate Virtual Drive or use short directory  for the reference design (for example x:\<design name>)
    4. Create Project (follow instruction of the product selection guide), settings file will be configured automatically during this process)
      1. (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 alsoTE Board Part Files
    5. Create XSA and export to prebuilt folder
      1. Run on Vivado TCL: TE::hw_build_design -export_prebuilt
        Note: Script generate design and export files into \prebuilt\hardware\<short dir>. Use GUI is the same, except file export to prebuilt folder
    6. Create Linux (bl31.elf, uboot.elf and image.ub) with exported XSA
      1. XSA is exported to "prebuilt\hardware\<short name>"
        Note: HW Export from Vivado GUI create another path as default workspace.
      2. Create Linux images on VM, see PetaLinux KICKstart
        1. Use TE Template from /os/petalinux
    7. Add Linux files (bl31.elf, uboot.elf and image.ub) to prebuilt folder
      1. "prebuilt\os\petalinux\<ddr size>" or "prebuilt\os\petalinux\<short name>"
    8. Generate Programming Files with Vitis
      1. Run on Vivado TCL: TE::sw_run_vitis -all
        Note: Scripts generate applications and bootable files, which are defined in "sw_lib\apps_list.csv"
      2. (alternative) Start SDK with Vivado GUI or start with TE Scripts on Vivado TCL: TE::sw_run_vitis
        Note:  TCL scripts generate also platform project, this must be done manuelly in case GUI is used. See Vitis

    Launch

    Page properties
    hiddentrue
    idComments

    Note:

    • Programming and Startup procedure

    Programming

    Note

    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

    Get prebuilt boot binaries

    1. _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 foler>/_binaries_<Artikel Name>) with subfolder (boot_<app name>) for different applications will be generated

    QSPI

    Optional for Boot.bin on QSPI Flash and image.ub on SD.

    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"
    3. Type on Vivado TCL Console: TE::pr_program_flash -swapp u-boot
      Note: To program with SDK/Vivado GUI, use special FSBL (zynqmp_fsbl_flash) on setup
                optional "TE::pr_program_flash -swapp hello_te0835" possible
    4. Copy image.ub on SD-Card
      • use files from (<project foler>/_binaries_<Articel Name>)/boot_linux from generated binary folder,see: Get prebuilt boot binaries
      • or use prebuilt file location, see <design_name>/prebuilt/readme_file_location.txt
    5. Insert SD-Card

    SD

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

    JTAG

    Not used on this Example.

    Usage

    1. Prepare HW like described on section TE0835 Test Board#Hardware Setup
    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.
    4. Power On PCB
      Note: 1. Zynqmp RFSoC Boot ROM loads FSBL from SD into OCM, 2. FSBL loads U-boot from SD into DDR, 3. U-boot load Linux from SD into DDR
    5. Open the RF Analyzer GUI
    6. Click on Connect
    7. Adjust the desired JTAG frequency (for example 30MHZ)
    8. Give the generated bitstream file path
    9. Click on Download Bitstream on the FPGA
    10. When downloading is finished, click on Select Target
    11. After the initilalisation, all ADCs/DACs tiles are visible
    12. Click on desired DAC tile and choose a DAC (for example DAC0)
    13. Adjust the desired DAC properties (for example output frequency)
    14. Click on Generate to generate the signal in output of DAC
    15. Click on the related ADC tile and choose the related ADC (for example ADC0)
    16. Click on Acquire to aqcuire the input signal
    17. The spectum of the DAC output signal can be seen now. The signal can be visible in time domain too.
      1. Tip: In menu Window click on Multiview to see all of DACs and ADCs simultaneously.
    Expand
    titleexample

    Image Removed

    Expand
    titleDACs

    Image Removed

    Expand
    titleADCs

    Image Removed

    Linux

    1. Open Serial Console (e.g. putty)
      1. Speed: 115200
      2. 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 For Linux Login use:
      1. User Name: root
      2. Password: root
    3. You can use Linux shell now.
      1. I2C 0 Bus type: i2cdetect -y -r 0
      2. I2C 1 Bus type: i2cdetect -y -r 1
      3. RTC check: dmesg | grep rtc
      4. ETH0 works with udhcpc
      5. USB type  "lsusb" or connect USB2.0 device
    4. Option Features
      1. Webserver to get access to Zynqmp RFSoC
        1. insert IP on web browser to start web interface
      2. init.sh scripts
        1. add init.sh script on SD, content will be load automatically on startup (template included in ./misc/SD)

    Vivado HW Manager

    Page properties
    hiddentrue
    idComments

    Note:

    • Add picture of HW Manager

    • add notes for the signal either groups or topics, for example:

      Control:

      • add controllable IOs with short notes..

      Monitoring:

      • add short notes for signals which will be monitored only
      • SI5338 CLKs:
        • Set radix from VIO signals to unsigned integer. Note: Frequency Counter is inaccurate and displayed unit is Hz
        • expected CLK Frequ:...

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

    • Monitoring:
      • The output frequency  of MMCM blocks can be monitored.
        • Set radix from VIO signals to unsigned integer.
        • The tempreature of ARM processor and FPGA can be measured too.
    Scroll Title
    anchorFigure_VHM
    titleVivado Hardware Manager
    Image Removed


    System Design - Vivado

    Page properties
    hiddentrue
    idComments

    Note:

    • Description of Block Design, Constrains... BD Pictures from Export...

    ...