TEI1000 Test Board

Overview

Refer to http://trenz.org/tei1000-info for the current online version of this manual and other available documentation.

Key Features

• Quartus Prime Pro 23.4
• Nios V (SG Variant only)
  • UART
  • DDR4
• Yocto (SX Variant only)
  • UART
  • ETH
  • USB
  • SD
  • I2C
  • DDR4

Revision History

Release Notes and Know Issues

Requirements

Software

Hardware

Complete List is available on <project folder>/board_files/*_board_files.csv

Design supports following modules:

Design supports following carriers:

Additional HW Requirements:

Content

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

Design Sources

Prebuilt

Download

Reference Design is only usable with the specified Quartus version. Do never use different versions of Quartus software for the same project.

Reference Design is available on:

• TEI1000 "Test Board" Reference Design

Design Flow

See also:

• Project Delivery - Intel devices

The Trenz Electronic FPGA Reference Designs are TCL-script based projects. To create a project, open a project or program a device execute "create_project_win.cmd" on Windows OS and "create_project_linux.sh" on Linux OS.

TE Scripts are only needed to generate the quartus project, all other additional steps are optional and can also executed by Intel Quartus/SDK GUI. For currently Scripts limitations on Win OS and Linux OS see: Project Delivery - Intel devices → Currently limitations of functionality

1. Open create_project_win.cmd/create_project_linux.sh:
   
2. Select Board in "Board selection"
3. Click on "Create project" button to create project
   
   1. (optional for manual changes) Select correct quartus installation path in "<project folder>/settings/design_basic_settings.tcl"
4. (SX Variant only) Create and configure your Yocto Linux project in LinuxOS
   1. Copy the meta-trenz_altera folder from <project name>/os/yocto/meta-trenz_altera to the path/to/your/yocto/directory
   2. Run following command in the command shell and follow the instructions:
      

      . ./meta-trenz_altera/tei1000_yocto_setup

5. (SX Variant only) Open Nios V command shell and run following command to generate the jic file with this files included:

   • test_board.sof file (generated in quartus project)

   • u-boot-dtb.hex file (generated with Yocto):

     quartus_pfg -c path/to/reference_design/quartus/output_files/test_board.sof path/to/reference_design/quartus/output_files/u-boot-spl-dtb.jic \
        -o device=MT25QU512 \
        -o flash_loader=1SX040HH3 \
        -o hps_path=path/to/yocto/u-boot-spl-dtb.hex \
        -o mode=ASX4

Launch

Programming

Get prebuilt boot binaries

1. Run create_project_win.cmd/create_project_linux.sh
2. Select Module in 'Board selection'
3. Click on 'Export prebuilt files' button
   1. Folder <project folder>/_binaries_<Article Name> with subfolder boot_linux will be generated and opened

SD-Boot mode (SX variant only)

1. Copy  u-boot.itb, Image, tei1000_*.dtb and the extlinux folder on SD
   • use files from "<project folder>\_binaries_<Article Name>\boot_linux" from generated binary folder, see: #Get prebuilt boot binaries
2. Insert SD-Card in the SD-Slot
3. Program configuration flash with the jic file
   1. Set DIP-Switch S5.1-4 to OFF on TEB1000
   2. Connect JTAG and power on carrier with module
   3. Open create_project_win.cmd/create_project_linux.sh
   4. Select correct board in "Board selection"
   5. Click on "Program device" button
      1. if prebuilt files are available: select "Program prebuilt file"
      2. using own generated programming file: select "Program other file" and click on "Browse ..." to open own generated programming file
   6. Click on "Start program device" button

QSPI (SG variant only)

1. Set DIP-Switch S5.1-4 to OFF on TEB1000
2. Connect JTAG and power on carrier with module
3. Open create_project_win.cmd/create_project_linux.sh
4. Select correct board in "Board selection"
5. Click on "Program device" button
   1. if prebuilt files are available: select "Program prebuilt file"
   2. using own generated programming file: select "Program other file" and click on "Browse ..." to open own generated programming file
6. Click on "Start program device" button

JTAG

Not used on this example.

Usage

1. Prepare HW like described on section Programming
2. Set DIP-Switch S5.1=ON on TEB1000
3. Connect UART USB (most cases same as JTAG)
4. Connect your board to the network
5. Power on PCB
6. Open Serial Console (e.g. PuTTY)
   • Speed: 115200

   • select COM Port

     Win OS: see device manager | Linux OS: see ls -l dev/serial/by-id  (UART is *USB1)

Linux (SX variant only)

1. Linux Console:

   Note: Wait until Linux boot finished

2. You can use Linux shell now.

   i2cdetect -y -r 1   (check I2C 1 Bus)
   udhcpc              (ETH check)
   lsusb               (USB check)

3. Optional Features

   • init.sh scripts
     • add init.sh script on SD, content will be load automatically on startup (template included in "<project folder>\misc\sd")

Baremetal (SG variant only)

1. Console output:
   1. 'Hello TEI1000' in endless loop

System Design - Quartus

Block Design

The block designs may differ depending on the assembly variant.

HPS Interfaces (SX variant only)

Activated interfaces:

Software Design - SDK

Application

Used software project depends on board assembly variant. Template location: <project folder>/source_files/software/

hello_tei1000

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

Software Design - Yocto

U-Boot

File location: meta-trenz_altera/recipes-bsp/u-boot/

Changes:

• enable boot from sd

  • CONFIG_SD_BOOT=y

  • CONFIG_BOOTDELAY=3

  • CONFIG_BOOTCOMMAND="setenv fdt_addr_r 0x10000000; run distro_bootcmd"

• set env to nowhere

  • CONFIG_ENV_IS_NOWHERE=y

  • # CONFIG_ENV_IS_IN_FAT is not set

• MAC from eeprom

  • CONFIG_I2C_EEPROM=y

  • CONFIG_SYS_I2C_EEPROM_ADDR=0x50

  • CONFIG_SYS_I2C_EEPROM_BUS=1

  • CONFIG_SYS_EEPROM_SIZE=256

  • CONFIG_SYS_EEPROM_PAGE_WRITE_BITS=0

  • CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS=0

  • CONFIG_SYS_I2C_EEPROM_ADDR_LEN=1

  • CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW=0

• enable spl output

  • CONFIG_SPL_DISPLAY_PRINT=y

• enable misc_init_r function

  • CONFIG_MISC_INIT_R=y

• configure eth

  • CONFIG_PHY_MARVELL=y

  • # CONFIG_DM_ETH_PHY is not set

• Disable NAND/UBI/QSPI related settings from defconfig

  • CONFIG_NAND_BOOT=n

  • CONFIG_SPL_NAND_SUPPORT=n

  • CONFIG_CMD_NAND_TRIMFFS=n

  • CONFIG_CMD_NAND_LOCK_UNLOCK=n

  • CONFIG_NAND_DENALI_DT=n

  • CONFIG_SYS_NAND_U_BOOT_LOCATIONS=n

  • CONFIG_UBIFS_SILENCE_MSG=n

  • CONFIG_QSPI_BOOT=n

  • CONFIG_SPL_NAND_FRAMEWORK=n

  • CONFIG_MTD_RAW_NAND=n

  • CONFIG_CMD_UBI=n

  • CONFIG_CMD_UBIFS=n

  • CONFIG_MTD_UBI=n

  • CONFIG_ENV_IS_IN_UBI=n

Device Tree

U-boot Device Tree

#u-boot device_tree.dts
/ {
  aliases {
    serial0 = &uart0;
    ethernet1 = &gmac1;
    i2c1 = &i2c1;
  };
};

&gmac1 {
  status = "okay";
  phy-mode = "rgmii";
  phy-handle = <&emac1_phy0>;

  mdio {
    #address-cells = <1>;
    #size-cells = <0>;
    compatible = "snps,dwmac-mdio";

    emac1_phy0: ethernet-phy@1 {
      reg = <1>;
    };
  };

};

&gpio0 {
  status = "okay";
};

&i2c1 {
  status = "okay";

  eeprom_mac: eeprom@50 {
    #address-cells = <1>;
    #size-cells = <1>;
    reg = <0x50>;
    compatible = "microchip,24aa025","atmel,24c02";
  };
};

&mmc {
  status = "okay";
  bus-width = <4>;
  cap-sd-highspeed;
  cap-mmc-highspeed;
};

&uart0 {
  status = "okay";
  clock-frequency = <75000000>;
};

&usb1 {
  status = "okay";
};

&watchdog0 {
  status = "okay";
};

#device_tree-u-boot.dts
/ {
  chosen {
    stdout-path = "serial0:115200n8";
    u-boot,spl-boot-order = &mmc;
  };
};

&clkmgr {
  bootph-all;
};

&sysmgr {
  bootph-all;
};

&fdt_0_blob {
  filename = "arch/arm/dts/tei1000_a3i11.dtb";
};

&binman {
  /delete-node/ kernel;
};

Kernel Device Tree

#kernel device_tree.dts
/ {
  aliases {
    serial0 = &uart0;
    ethernet1 = &gmac1;
    i2c1 = &i2c1;
  };

  chosen {
    stdout-path = "serial0:115200n8";
  };

  memory@40000000 {
    device_type = "memory";
    reg = <0 0x00000000 0 0x40000000>;
  };

  soc {
    eccmgr {
      sdmmca-ecc@ff8c8c00 {
        compatible = "altr,socfpga-s10-sdmmc-ecc", "altr,socfpga-sdmmc-ecc";
        reg = <0xff8c8c00 0x100>;
        altr,ecc-parent = <&mmc>;
        interrupts = <14 4>, <15 4>;
      };
    };

    mmcclk_ciu: mmcclk-ciu {
      #clock-cells = <0>;
      compatible = "fixed-clock";
      clock-frequency = <200000000>;
    };
  };
};

&gmac1 {
  status = "okay";
  phy-mode = "rgmii-id";
  phy-handle = <&emac1_phy0>;

  mdio {
    #address-cells = <1>;
    #size-cells = <0>;
    compatible = "snps,dwmac-mdio";

    emac1_phy0: ethernet-phy@1 {
      reg = <1>;
    };
  };
};

&gpio0 {
  status = "okay";
};

&i2c1 {
  status = "okay";

  eeprom: eeprom@50 {
    compatible = "microchip,24aa025","atmel,24c02";
    reg = <0x50>;
    eth1_addr: eth-mac-addr@fa {
      reg = <0xfa 0x06>;
    };
  };
};

&mmc {
  status = "okay";
  cd-gpios = <&porta 6 GPIO_ACTIVE_LOW>;
  bus-width = <4>;
  cap-sd-highspeed;
  cap-mmc-highspeed;
  
  clocks = <&clkmgr STRATIX10_L4_MP_CLK>, <&mmcclk_ciu>;
};

&osc1 {
  clock-frequency = <25000000>;
};

&uart0 {
  status = "okay";
};

&usb1 {
  status = "okay";
};

Kernel

File location: meta-trenz_altera/recipes-kernel/linux/

Changes:

• eth phy
  • CONFIG_MARVELL_PHY=y
  • CONFIG_OF_MDIO=y
• eeprom
  • CONFIG_EEPROM_AT24=y

Images

Image recipe for minimal console image

File location: meta-trenz_altera/recipes-core/images/

Image recipes:

• te-image-minimal.bb: create minimal linux image
• te-image-initramfs.bb: required for building an image with initial RAM Filesystem

Added packages/recipes:

• startup
• ethtool
• i2c-tools
• usbutils
• mtd-utils
• util-linux
• bash
• libgpiod-tools

Rootfs

Used filesystem: Initial RAM Filesystem (initramfs)

Appx. A: Change History and Legal Notices

Document Change History

Legal Notices