Notes about this Manual Usage The information in this manual is valid for all standard variants of the phyGATE Tauri-L industrial gateway from PHYTEC Messtechnik GmbH. An overview of all devices and variants to which the descriptions apply can be found in Product Information.
L-1028e.A4 phyGATE-Tauri-L (i.MX 8M Mini) Kit Hardware and BSP Manual Safety Instructions and Liability Intended Use The phyGATE Tauri-L gateway is designed for monitoring, processing, and communicating machine and sensor data in industrial environments. For data communication, the devices provide various typical industrial interfaces for connection to surrounding devices.
3.1 Product Names and Variants The phyGATE Tauri-L gateway is available in different variants and expansion stages, which differ in the scope of performance and functions. The following table gives an overview of available variants of the gateway and an explanation for the identification of the article number.
(14.) internal miniPCIe slot (USB only) (15.) SIM card socket 3.3 Nameplate The nameplate of the phyGATE Tauri-L gateway is located on the side of the housing. Here you will find essential information about your device. Technical Data TABLE 3: Technical Data Information Electrical Data min.
1x LAN cable 2m 3.6 Certification The phyGATE Tauri-L has been approved for sale and use on the European market and meets the criteria for CE marking according to: • DIN EN 61000-6-2:2019-11 EMV Interference immunity for industrial areas •...
Page 14
3.7 Technical Documentation and Support Technical documentation for the product can be found on our product page online at www.phytec.de. If you have any questions or suggestions regarding the product, we look forward to hearing from you.
Mechanical Connection The phyGATE Tauri-L gateway housing is designed to be mounted on a top-hat rail in the control cabinet. For mounting on the top-hat rail, there is a mounting device on the housing which allows a tool-free and safe mounting on a 35 mm top-hat rail.
Page 19
5 Getting Started with the phyGATE Tauri-L Gateway Introduction To easily get started with your phyGATE Tauri-L device, you'll find a description with the necessary tools and provision of the know-how to work with the Linux Board Support Package (BSP) for the phyCORE-i.MX 8M Mini below.
Page 20
If you have a prepared SD card from the phyGATE Tauri-L Kit, this section can be skipped. If you are using your own SD Card, you'll have to download the prebuilt image file and burn it to the SD card first: Download the Image file located at https://download.phytec.de/Software/Linux/BSP-Yocto-i.MX8MM/BSP-...
5.4.2 Set Boot Switch The phyGATE Tauri-L provides a boot switch to choose the boot source of the device. You can choose either eMMC (DIP at position '1') or SD Card (DIP at position 'ON') as a boot source. ...
Page 22
Do not make any electrical changes to the interfaces and cables while the board is connected to power. This is to avoid damage to the device! Be aware that as soon as the phyGATE Tauri-L is supplied with power, the SD Card boot sequence will begin. Ensure that all cables are connected on the board! ...
Page 24
Finding the Right Software Platform The i.MX 8M Mini BSP is a unified BSP, which means, it supports a set of different PHYTEC carrier boards (CB) with different Systems on Module (SOMs). For the Tauri-L there is one machine included:...
Page 28
Resizing ext4 Root Filesystem. 7.2.1 Updating eMMC via SD Card in Linux on Target You can also update the eMMC under Linux. You only need a complete image saved on the SD card (e.q. phytec- headless-image-phygate-tauri-l-imx8mm-2.sdcard). • Show your saved image files on the SD card: target$ ls phytec-headless-image-phygate-tauri-l-imx8mm-2.sdcard...
Page 29
The RAUC (Robust Auto-Update Controller) mechanism support has been added to meta-ampliphy. It controls the procedure of updating a device with new firmware. This includes updating the Linux kernel, Device Tree, and root filesystem. PHYTEC has written an online manual on how we have intergraded RAUC into our BSPs: L-1006e.A3 RAUC Update &...
PHYTEC i.MX 8M Mini BSP Device Tree Concept The following sections explain some rules we have defined on how to set up device trees for our i.MX 8M Mini SoC- based boards.
Page 33
MMC device or from tftp. The main intention of this file is to store the ${overlays} variable. This makes it easy to pre-define the overlays in Yocto depending on the machine used. The content from the file is defined in the Yocto recipe bootenv found in meta-phytec https://git.phytec.de/meta-phytec/tree/recipes-bsp/bootenv? h=hardknott.
Page 34
L-1028e.A4 phyGATE-Tauri-L (i.MX 8M Mini) Kit Hardware and BSP Manual Accessing Peripherals To find out which boards and modules are supported by the release of PHYTEC’s i.MX8 BSP described herein, visit our web page at http://www.phytec.de/produkte/software/yocto/phytec-unified-yocto-bsp-releases/ and click the corresponding BSP release. here you can find all hardware supported in the columns "Hardware Article Number"...
Page 37
10.4 SD / MMC Card phyGATE Tauri-L gateway supports a slot for Secure Digital Cards and MultiMedia Cards to be used as general- purpose block devices. These devices can be used in the same way as any other block device.
Page 38
10.5 eMMC Devices PHYTEC modules like phyCORE-i.MX 8M Mini are populated with an eMMC memory chip as main storage. eMMC devices contain raw MLC memory cells combined with a memory controller that handles ECC and wear leveling. They are connected via an MMC/SD interface to the i.MX 8M Mini and are represented as block devices in the Linux kernel like SD cards, flash drives, or hard disks.
Page 44
10.9 C Bus The i.MX 8M Mini contains three Multimaster fast-mode I²C modules called I2C1, I2C2, I2C3, and I2C4. PHYTEC boards provide plenty of different I²C devices connected to the I²C modules of the i.MX 8M Mini. This chapter will describe the basic device usage and its DT representation of some of the I²C devices integrated on our phyGATE-...
Page 45
The I2C EEPROM, populated on the phyCORE-i.MX 8M Mini/Nano, has a separate ID page that is addressable over I2C address 0x59 on bus 0 and a normal area that is addressable over i2c address 0x51 on bus 0. PHYTEC uses this data area of 32 Bytes to store information about the SoM.
Page 49
10.12 RTCs can be accessed via /dev/rtc*. Because PHYTEC boards have often more than one RTC, there might be more than one RTC device file. • To find the name of the RTC device, you can read its sysfs entry with: target$ cat /sys/class/rtc/rtc*/name •...
Due to udev, all mass storage devices connected get unique IDs and can be found in /dev/disks/by-id. These IDs can be used in /etc/fstab to mount the different USB memory devices in different ways. User USB2 (host) configuration is in the kernel device tree phytec-imx8mm-phyGATE-Tauri.dtsi: […]...
Page 51
TPM 2.0 standard. The TPM is connected over the SPI interface. Currently, we support a basic driver implementation. Bootlog output: tpm_tis_spi spi1.0: TPM (device-id 0x1B, rev-id 16) TPM configuration in the kernel device tree phytec-imx8mm-phyGATE-Tauri.dtsi: https://git.phytec.de/linux-imx/tree/arch/arm64/boot/dts/freescale/imx8mm-phygate-tauri.dts?h=v5.10.72_2.2.0- phy4#n111 10.15 PCIe The phyGATE-Tauri-L has one Mini-PCIe slot. In general, PCIe autodetects new devices on the bus. After connecting the device and booting up the system, you can use the command lspci to see all PCIe devices recognized.
Need help?
Do you have a question about the phyGATE Tauri-L and is the answer not in the manual?
Questions and answers