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.
For data communication, the devices provide various typical industrial interfaces for connection to surrounding devices. This PHYTEC standard gateway is supplied exclusively as an OEM device by PHYTEC Messtechnik GmbH and requires an adaptation of the operating software for the intended application by the distributor of the device.
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.
Page 19
OS in order to operate the software and hardware All necessary information, software, and other downloads for quick commissioning can be found on the phyGATE Tauri-L product page online at www.phytec.de. Requirements You'll need the following components to get started quickly with this installation guide: •...
Page 24
L-1028e.A3 phyGATE-Tauri-L (i.MX 8M Mini) Kit Hardware and BSP Manual host$ ifconfig <eth-interface> 192.168.3.10 host$ ssh root@192.168.3.11 Yogurt Vendor (Phytec Vendor Distribution) 2.6.2 phygate-tauri-l-imx8mm-2 ttymxc2 phygate-tauri-l-imx8mm-2 login: 5.6 Setup Device Interfaces 5.6.1 Connecting to CAN The CAN configuration is automatically done by the daemon systemd. You can send messages with cansend or receive messages with candump:...
Page 25
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:...
It contains all BSP files in correctly preformatted partitions and can be copied to the SD card easily using the single Linux command dd. The created file phytec-headless-image-phygate-tauri-l-imx8mm-2.sdcard is only a link to a file like phytec- headless-image-phygate-tauri-l-imx8mm-2-<BUILD-TIME>.rootfs.sdcard. Warning To create your bootable SD card with the dd command, you must have root privileges.
Page 28
After having unmounted all devices with an appended number (<your_device><number>), you can create your bootable SD card with: host$ sudo dd of=/dev/<your_device> if=phytec-headless-image-phygate-tauri-l-imx8mm-2. sdcard bs=1MB conv=fsync status=progress Using the device name (<your_device>) without appended number (e.g. sde) which stands for the whole device. The parameter conv=fsync forces a sync operation on the device before dd returns.
Page 31
Resizing ext4 Root Filesystem. 8.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 32
L-1028e.A3 phyGATE-Tauri-L (i.MX 8M Mini) Kit Hardware and BSP Manual RAUC The Robust Auto-Update Controller (RAUC) mechanism is a new addition to Yogurt. PHYTEC has written an online manual on how we have integrated RAUC into our BSPs (L-1006e.A0 RAUC Update & Device Management Manual).
Page 33
10.2 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 35
L-1028e.A3 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 39
If it does not contain one, the whole device can be used as a file system (”floppy” like handling). In this case, /dev/mmcblk1 must be used for formatting and mounting. The cards are always mounted as being writable. DT configuration for the MMC (SD card slot) interface in arch/arm64/boot/dts/freescale/phytec-imx8mm-phyGATE- Tauri.dtsi: […] ...
Page 42
11.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 47
It lists all MTD devices and the corresponding partition names. The flash node is defined inside the SPI master node in the module DTS. The SPI node contains all devices connected to this SPI bus which is in this case only the SPI NOR Flash. Definition of the SPI master node in imx6qdl-phytec-phycore-som.dtsi : &flexspi { pinctrl-names = "default";...
Page 50
L-1028e.A3 phyGATE-Tauri-L (i.MX 8M Mini) Kit Hardware and BSP Manual • To toggle OFF: target$ echo > /sys/class/leds/led-red/brightness • User I/O configuration in device tree file arch/arm64/boot/dts/freescale/phytec-imx8mm-phyGATE-Tauri.dtsi: leds { compatible = "gpio-leds"; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_leds>; led-red { label = "red-emmc";...
Page 51
11.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 52
To fill the whole EEPROM with zeros, use: target$ dd if=/dev/zero of=/sys/class/i2c-dev/i2c-0/device/0-0051/eeprom bs=4096 count=1 This operation takes some time because the EEPROM is relatively slow. DT representation, e.g. in phyCORE-i.MX 8M Mini file phytec-imx8mm-phycore-som.dtsi: &i2c1 { clock-frequency = <400000>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_i2c1>;...
Page 56
>; [...] 11.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: […] ...
USB OTG Most PHYTEC boards provide a USB OTG interface. USB OTG ports automatically act as a USB device or USB host. The mode depends on the USB hardware attached to the USB OTG port. If, for example, a USB mass storage device is attached to the USB OTG port, the device will show up as /dev/sda.
Page 59
If your system has more than one USB Device or OTG port, you can pass the right one to the USB Device Controller (UDC). • To stop the USB gadget and unbind the used functions execute: target$ echo "" > /sys/kernel/config/usb_gadget/g1/UDC User USB OTG configuration in the kernel device tree phytec-imx8mm-phyGATE-Tauri.dtsi: [...] reg_usb_otg1_vbus: regulator-usb-otg1-vbus { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_usbotg1pwrgrp>;...
Page 60
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: /* TPM */ &ecspi2 { #address-cells = <1>;...
Need help?
Do you have a question about the phyGATE-Tauri-L L-1028e.A3 and is the answer not in the manual?
Questions and answers