Eurotech DynaGATE 10-14 Owner's manual

Type
Owner's manual
DynaGATE 10-14
Multi-service IoT Gateway
ITxPT, AI Accelerated, LTE 5G Ready
EN EL Software Manual
Original instructions
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
FOR SAFE AND PROPER USE,
FOLLOW THESE INSTRUCTIONS.
KEEP THEM FOR FUTURE REFERENCE.
DynaGATE 10-14 EL Software Manual EN
Intended audience of this document
This document is intended for system integrators. System integrator is a term applied to skilled
persons who are specialized in linking together, physically or functionally, different computing systems
and software applications to operate as a coordinated whole in compliance with the applicable
regulations.
Skilled person is a term applied to persons who have training or experience in the equipment
technology, particularly in knowing the various energies and energy magnitudes used in the equipment.
Skilled persons are expected to use their training and experience to recognize energy sources capable
of causing pain or injury and to take action for protection from injury from those energies. Skilled persons
should also be protected against unintentional contact or exposure to energy sources capable of
causing injury.
How to get technical support
To get technical support, refer to: https://www.eurotech.com/support
The following resources are available:
lSupport Portal: https://support.eurotech.com
lDownload Area: https://www.eurotech.com/download
lRMA (Return Merchandise Authorization): https://www.eurotech.com/support/rma
Trademarks
All trademarks, registered trademarks, logos, trade names, products names contained in this document
are the property of their respective owners.
Revision history
Revision Description Date of Issue
1-0 First release 2023.08.02
1-1 Updated ITxPT information 2023.10.30
1-2 Updated sections:
l3.8 Internal Cellular Modem
l3.11 CAN Ports
l3.14 Ignition Key Sense
l3.23 Power monitoring device
2023.11.28
2 / 47 © 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
DynaGATE 10-14 EL Software Manual EN Getting started
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
3 / 47
GETTING STARTED
To get started with the DynaGATE 10-14 and Eurotech Everyware Linux (EL):
1. Obey the instructions and warnings contained in the manuals.
To safely interact with the product and to lower the risk of personal injury, electric shock, fire, or
damage to equipment, obey the instructions and warnings contained in this manual and in the
DynaGATE 10-14 Hardware Manual.
To download the latest DynaGATE 10-14 Hardware Manual go to the Eurotech Download Area:
https://www.eurotech.com/download
2. Understand how to log in and how to manage the Everyware Linux (EL) interfaces.
For more information, refer to:
l"The Software (EL 33)" on page6
l"Administration Console login (EL 33)" on page14
l"Linux interfaces (EL 33)" on page18
l"System decommissioning" on page42
If you have questions about these instructions, refer to: https://www.eurotech.com/en/support.
DynaGATE 10-14 EL Software Manual EN Contents
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
4 / 47
CONTENTS
Intended audience of this document 2
How to get technical support 2
Trademarks 2
Revision history 2
Getting started 3
Contents 4
1 The Software (EL 33) 6
1.1 Eurotech Everyware Linux (EL) 7
1.1.1 Installation and update recommendations 7
1.1.2 Docker 7
1.2 Eurotech Everyware IoT 7
1.2.1 Installation and update recommendations 7
1.3 System Firewall 8
1.4 Partition layout 8
1.5 Failover and recovery scheme 9
1.5.1 What is the failover and recovery scheme 9
1.5.2 Limitations in failover and recovery 10
1.5.3 Additional information 11
1.6 USER LEDs status reporting 11
1.6.1 Symbols used for USER LEDs status 12
1.6.2 USER LEDs status for power and boot actions 12
1.6.3 USER LEDs status for the recovery actions 12
1.6.4 USER LEDs status for the restore action 12
1.6.5 USER LEDs status for the decommissioning action 13
1.6.6 USER LEDs status for generic status error 13
2 Administration Console login (EL 33) 14
2.1 Introduction 15
2.2 Default credentials 15
2.2.1 Logging into EL 15
2.3 Changing the password 15
2.4 Login Messages 16
2.5 Login through the Serial Console 16
2.6 Login through SSH (Secure Shell) 17
2.6.1 The default network configuration 17
2.6.2 Login through eth0 17
2.6.3 Login through eth1 17
3 Linux interfaces (EL 33) 18
3.1 Introduction 19
3.2 Getting the installed Linux version 19
3.3 General Purpose I/O lines (GPIOs) 20
3.3.1 Using the GPIOs with the GPIO utility 20
3.3.2 Using the GPIOs with the “cat” and “echo” utilities 20
3.4 LED Indicators 21
3.5 Digital I/Os 22
3.6 Analog Inputs 23
3.7 Wi-Fi Regulatory Domain 24
3.8 Internal Cellular Modem 25
3.8.1 How to initialize the modem 25
3.8.2 How to connect the modem 25
Contents DynaGATE 10-14 EL Software Manual EN
3.8.3 How to set the operating mode of the modem 26
3.8.4 How to set the diversity (CELL DIV) mode 26
3.9 Internal GNSS 27
3.9.1 Getting the GPS coordinates 27
3.10 Ethernet Ports 28
3.11 CAN Ports 28
3.11.1 How to setup a CAN port 28
3.11.2 How to send / receive a message via a CAN port 28
3.11.3 CAN termination 28
3.11.4 CAN-FD 29
3.12 Console 29
3.13 Serial Ports 30
3.13.1 Configuring the serial COMport mode 30
3.14 Ignition Key Sense 34
3.14.1 The ignition monitoring function 35
3.15 Accelerometer and Gyroscope 35
3.15.1 How to get the accelerometer 3D values 35
3.15.2 How to get the gyroscope 3D values 35
3.16 Storage memory 36
3.17 TPM and tpm2-tools package 36
3.18 Watchdog 36
3.18.1 Using the Watchdog 36
3.18.2 For more information 36
3.19 RTC 37
3.19.1 How to read the RTC1 device 37
3.19.2 How to read the timestamp registers 37
3.20 Internal temperature sensors 37
3.21 User-programmable button and factory restore 38
3.21.1 User-programmable button functions 38
3.21.2 The "Other applications" function 38
3.21.3 The "Factory restore" function 38
3.21.4 How to view the current restore policy 38
3.21.5 How to set a specific restore policy 38
3.22 CPU Unique ID 38
3.23 Power monitoring device 39
3.23.1 Power Failure Detector and Power Monitoring Service 40
3.24 ITxPT services 41
3.24.1 ITxPT Inventory Service 41
4 System decommissioning 42
4.1 What is the decommissioning process 43
4.2 Decommissioning 43
5 Eurotech Everyware IoT 44
5.1 Everyware IoT 45
5.2 Everyware Software Framework (ESF) 45
5.3 Everyware Cloud (EC) 45
Notes 46
5 / 47 © 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
DynaGATE 10-14 EL Software Manual EN 1 The Software (EL 33)
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
6 / 47
1 THE SOFTWARE (EL 33)
This chapter gives the following information:
1.1 Eurotech Everyware Linux (EL) 7
1.2 Eurotech Everyware IoT 7
1.3 System Firewall 8
1.4 Partition layout 8
1.5 Failover and recovery scheme 9
1.6 USER LEDs status reporting 11
1 The Software (EL 33) DynaGATE 10-14 EL Software Manual EN
1.1 Eurotech Everyware Linux (EL)
The Eurotech Everyware Linux (EL) is a Linux distribution based on a Yocto framework,
www.yoctoproject.org, as well as an SDK for application development. For more information, refer to:
www.yoctoproject.org/documentation.
1.1.1 Installation and update recommendations
NOTICE
If the power supply is interrupted prematurely, this may result in a file corruption (this failure
will not be covered under warranty).
During installation and update, ensure a reliable source of power for the duration of the
install process and for a period of 30 seconds after the first boot.
1.1.2 Docker
Docker is installed in the default Linux image and can be used to create, manage and launch containers.
Once installed, the data partition is mounted on /var/lib/docker and this is where the docker
containers are stored. For more information, refer to: https://docs.docker.com/get-started/
The docker service is disabled by default
To enable the docker service use the systemd service controls:
systemctl enable docker
The docker service will run after a reboot.
1.2 Eurotech Everyware IoT
Eurotech provides hardware and software IoT solutions under the brand name of Everyware IoT.
For more information, refer to: "Everyware IoT" on page45.
1.2.1 Installation and update recommendations
NOTICE
If the power supply is interrupted prematurely, this may result in a file corruption (this failure
will not be covered under warranty).
During installation and update, ensure a reliable source of power for the duration of the
install process and for a period of 3 minutes after the first boot.
7 / 47 © 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
DynaGATE 10-14 EL Software Manual EN 1 The Software (EL 33)
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
8 / 47
1.3 System Firewall
NOTICE
For a better security, Eurotech recommends that you run the system with a firewall service
enabled.
By default, the system firewall is enabled.
The rules will block all in-bound connections on all ports but LAN port (eth0).
On this interface, the following IP ports are allowed for incoming connections:
ludp:67
ludp:53
ltcp:22
ludp:5353
For more information, refer to: "The default network configuration" on page17.
To disable the system firewall service:
1. Execute the command:
systemctl disable iptables
2. Reboot the system to apply the setting.
1.4 Partition layout
Partition Node Size
Boot /dev/mmcblk0p1 130.5 MB
Rootfs1 /dev/mmcblk0p2 8 GB
Rootfs2 /dev/mmcblk0p3 8 GB
Extended /dev/mmcblk0p4 N/A
Log /dev/mmcblk0p5 1.5 GB
Restore /dev/mmcblk0p6 4 GB
Data /dev/mmcblk0p7 8 GB
Total 32 GB (approx)
1 The Software (EL 33) DynaGATE 10-14 EL Software Manual EN
1.5 Failover and recovery scheme
1.5.1 What is the failover and recovery scheme
The failover and recovery scheme is invoked when a fail to boot scenario occurs.
The scheme is divided into two flows:
lBootloader scheme and
lRescue image.
1.5.1.1 Bootloader scheme
The bootloader scheme is the following:
1. The system boots
2. The bootloader selects which partition to boot (2 or 3) based on its environment settings.
Partition 2 is the default active and primary partition
3. The kernel is retrieved from the active partition and launched
4. The kernel and kernel arguments determine which root file system to be used: this is usually the
same partition from where the kernel was retrieved. Under normal circumstances, this never
changes
5. The bootloader keeps a count of if the system booted OK or if the system failed to boot
6. The LEDs report the boot status
7. If an error is detected:
a.a. The bootloader reports the detected error with a LEDs pattern
b. The bootloader launches the rescue image.
The communication between the rescue image and the bootloader is done through bootloader
environment variables.
For more information, refer to: "USER LEDs status reporting" on page11.
1.5.1.2 Rescue image
The rescue image is a kernel with an initial RAM disk that is configured to try to correct a fail to boot
scenario.
The scheme for the file system recovery attempt is the following:
1. The fsck utility is launched on the affected partition. This corrects the most likely reason for fail
to boot, which typically is a corruption in the file system or a corruption of the EXT4 journal
2. The system records the event in the journal and reboots:
lIf the recovery is successful, the system continues with normal operation.
lIf the system detects another failure, the recovery did not work as expected. In this case
the system will switch to boot from the secondary partition:
oIf the secondary partition boots successfully, the system continues with normal
operation.
oIf the secondary partition fails to boot:
a.a. The rescue image will be invoked and initiate a system restore operation
b. The System Restore wipes the secondary partition replacing it with a pre-set
image stored in the restore partition (this image is typically a factory reset
image but it could be a custom-captured image).
9 / 47 © 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
DynaGATE 10-14 EL Software Manual EN 1 The Software (EL 33)
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
10 / 47
1.5.1.3 Factory restore
The factory restore is a function that makes an entry in the boot environment to instruct the system to
reboot, and to force the system to do a restore.
By default, after the restore is completed:
1. The system shows a flashing LED sequence to indicate that the process is completed.
2. The system automatically boots with the restored image .
To support multiple scenarios, and to provide flexibility for new ones, the restore mechanism can use
some “policies” to support the use case in the best way.
The system currently supports these restore policies:
Restore Policy Description
0The system boots from the Rescue image and restores both file-systems to factory default
1The system boots from the Rescue image and restores the primary file-system to factory default
2 (default) The system boots from the Rescue image and restores the secondary file-systems to factory default
To start the factory restore, keep the User-programmable button pushed for at least 10 seconds.
For more information, refer to:
l"User-programmable button and factory restore" on page38
l"USER LEDs status reporting" on the next page.
1.5.2 Limitations in failover and recovery
Handling failure conditions can be complex so the failover and recovery scheme has been designed to
be as simple as possible and to solve the most likely kinds of problem that can occur in normal system
use. It cannot solve all potential problems.
The following is a list of issues that are not covered and are outside of the scope of the current
implementation. Should these issues occur, user intervention may be required for the system to be re-
installed using an SD card installer, or returned to Eurotech if the SD card install is prohibited due to
security restrictions:
lIf the recovery image is corrupted, renamed, or missing, the recovery cannot occur.
In these conditions, the system may get stuck in an endless reboot loop.
To clear this loop, a solution, depending on the type of failure that has occurred, is to execute
stop at the bootloader prompt and set restore_policy to 0.
At this time, the system should be able to boot from the primary file system and you can rename
or re-install the missing recovery image file
lAlthough fstab will perform an fsck check of the log and data partitions before mounting them, if
the log partition is damaged or wiped, the recovery scheme is not designed to detect or correct
this kind of issue.
In this scenario, the system is likely to encounter boot issues because the start-up service that
launches journald may fail to run. The default scheme is not configured to re-format the log
partition, favoring to preserve the logs that may still exist to aid diagnosis of the root cause.
Should this issue occur, the system will drop to emergency mode with the following message:
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, " systemctl default" or ^D to try again to boot into default mode.
Cannot open access to console, the root account is locked.
See sulogin(8)man page for more details.
Press Enter to continue.
1 The Software (EL 33) DynaGATE 10-14 EL Software Manual EN
1.5.3 Additional information
lRegardless of the state of the file system being rescued, when recovery is invoked, it generates a
kernel panic. This is normal behavior, and the kernel panic has no abnormal consequences.
The kernel panic is due to a reboot that is forced by the watchdog. It is safe to do this because the
system runs from a RAM file system. All other filesystems are safely unmounted at the time of the
reboot
lThe USER LEDs report the progression of the failover and recovery process. For more
information, refer to: "USER LEDs status reporting" below.
1.6 USER LEDs status reporting
Some pre-configured actions can be performed on the system: power and boot, recovery, restore,
decommissioning.
Specific USER LEDs sequences indicate the status for these actions.
NOTE: Outside of these actions, the USER LEDs remain available for customer use.
The USER LEDs are as follows:
Fig. 1 - USER LEDs layout
Label Color Description
USER1 Bi-color Green / Yellow General purpose LEDs
USER2
USER3 Bi-color Green / Red
USER4
Fig. 2 - USER LEDs description
For more information, refer to: "LED Indicators" on page21.
11 / 47 © 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
DynaGATE 10-14 EL Software Manual EN 1 The Software (EL 33)
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
12 / 47
1.6.1 Symbols used for USER LEDs status
In the tables of the following sections, these symbols are used to indicate the corresponding USER
LEDs status:
OFF
x Not relevant. Do not consider. Previous state maybe preserved
Green, solid ON
1Hz Green, blinking at 1 Hz
2Hz Green, blinking at 2 Hz
Red, solid ON
1Hz Red, blinking at 1 Hz
2Hz Red, blinking at 2 Hz
1.6.2 USER LEDs status for power and boot actions
LED Power ON / RESET
USER1
USER2
USER3
USER4
1.6.3 USER LEDs status for the recovery actions
LED Recovery triggered Recovery running Recovery accomplished Recovery failed
USER1 x 2Hz
USER2 x
USER3 2Hz
USER4 x 2Hz
1.6.4 USER LEDs status for the restore action
LED Restore running Restore accomplished Restore failed
USER1 2Hz
USER2 2Hz
USER3 2Hz
USER4 2Hz
1 The Software (EL 33) DynaGATE 10-14 EL Software Manual EN
1.6.5 USER LEDs status for the decommissioning action
LED Decommissioning started Decommissioning accomplished
USER1 x x
USER2 x x
USER3 3x 1Hz then
USER4 3x 1Hz then
1.6.6 USER LEDs status for generic status error
LED Recovery triggered
USER1 x
USER2 x
USER3 x
USER4 1Hz
13 / 47 © 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
DynaGATE 10-14 EL Software Manual EN 2 Administration Console login (EL 33)
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
14 / 47
2 ADMINISTRATION CONSOLE LOGIN (EL 33)
This chapter gives the following information:
2.1 Introduction 15
2.2 Default credentials 15
2.3 Changing the password 15
2.4 Login Messages 16
2.5 Login through the Serial Console 16
2.6 Login through SSH (Secure Shell) 17
2 Administration Console login (EL 33) DynaGATE 10-14 EL Software Manual EN
2.1 Introduction
This section describes how to have access the Linux Operating System by logging into the
Administration Console.
To log in to the Administration Console, use one of the following methods:
lLog in through the Serial Console
lLog in through Secure Shell (SSH)
2.2 Default credentials
NOTICE
For security reasons, Eurotech recommends that you change the password of the "guest"
account after your initial setup.
For more information, refer to: "Changing the password" below.
2.2.1 Logging into EL
The following table shows the available users and passwords:
User* Password Note
guest Set by default to the serial number of the device The guest user is a member of the sudo group
*root user is disabled
Note: Most users, once logged in as a guest, will elevate to root by running the command su
While this will get users to root, it will not run some of the environment scripts that are typically
associated with the root user. Specifically, the .bashrc file in the root folder sets up various
environment variables and paths. To overcome this, elevate to root using this command:
sudo su -l
where -l means log in as root. This will run the scripts associated with the root user.
2.3 Changing the password
To change the password:
1. Log in to the Administration Console
2. Run the command passwd. Enter your old password for verification
3. Enter the new password.
15 / 47 © 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
DynaGATE 10-14 EL Software Manual EN 2 Administration Console login (EL 33)
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
16 / 47
2.4 Login Messages
The Login Messages discourage unauthorized access. They can be displayed before and after attempts
to access the system, either through the serial console or through ssh:
lThe text to be displayed before any access through the serial console is contained in
/etc/issue
lThe text to be displayed before any ac cess through ssh (including scp) is contained in
/etc/issue.net
lThe text to be displayed after a successful access through ssh or through the serial console is
contained in /etc/motd.
The Login Messages can be changed to suite other scenarios.
2.5 Login through the Serial Console
The Serial Console is available via the USB C connector of the system, behind the service panel, and
appears as a USB to Serial device on the host system.
To log in through the Serial Console:
1. Setup a Development PC (for example: a laptop) with a free USB port
2. Make sure that the system is turned OFF
3. Connect the USB C Cable between the USB port (of the Development PC) and the Serial
Console (of the system)
4. Turn ON the system
5. Use the Development PC to login the Administration Console:
a.a. Run a terminal emulator such as Tera Term (Windows) or Minicom (Linux)
b. Configure the serial port connection with these parameters: 115200, 8 bits, 1 stop bit, no
parity, no flow control
c. Enter the case-sensitive credentials when the prompt appears (refer to "Default
credentials" on the previous page). You should see the following output:
guest
Password:
guest@productname...:~#
2 Administration Console login (EL 33) DynaGATE 10-14 EL Software Manual EN
2.6 Login through SSH (Secure Shell)
2.6.1 The default network configuration
The default (out-of-the-box) network configuration of the system is as follows:
leth0
oStatus: Enabled for LAN
oConfigure: Manually (Static IP)
oIP Address: 172.16.0.1
oSubnet Mask: 255.255.255.0
oDHCP Server Enabled
leth1
oStatus: Enabled for WAN
oConfigure: DHCP (DHCP client)
lwlan0
oStatus: Disabled
You can log in via SSH through eth0 or through eth1.
2.6.2 Login through eth0
To log in through eth0:
1. Ensure that the client PC uses an IP address on the same subnet as eth0 (e.g. 172.16.0.2)
2. Enter the command ssh [email protected]
3. At the prompt, execute the password.
2.6.3 Login through eth1
To log in through eth1, you need to know its IP address. By default, the system runs a zeroconf
implementation. To remotely detect the IP address of the system, run the following command on your
host device: avahi-discover
Example:
1. Run the command: avahi-discover. A dialog box pops-up and reports all the devices on your
network that support this scheme
2. In "eth1 IPv4" > "local" > "Workstation", you should see your system’s hostname (example:
systemname_serialnumber)
3. By default, SSH login via eth1 is blocked by the iptables firewall.
To allow SSH connections on this interface, execute the following command:
iptables -A INPUT -i eth1 -p tcp --dport 22 -j ACCEPT
To preserve that, add it to the rules that run on start-up: /etc/iptables/iptables.rules
Note:
lIf you are running ESF, then it disables the iptables firewall in favor of its own, so you
should adjust the firewall in ESF if required
lThe information in the example above gives you SSH access for development and other
useful purposes; consider carefully whether making such a change is a sensible default
in a field deployed system.
17 / 47 © 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
DynaGATE 10-14 EL Software Manual EN 3 Linux interfaces (EL 33)
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
18 / 47
3 LINUX INTERFACES (EL 33)
This chapter gives the following information:
3.1 Introduction 19
3.2 Getting the installed Linux version 19
3.3 General Purpose I/O lines (GPIOs) 20
3.4 LED Indicators 21
3.5 Digital I/Os 22
3.6 Analog Inputs 23
3.7 Wi-Fi Regulatory Domain 24
3.8 Internal Cellular Modem 25
3.9 Internal GNSS 27
3.10 Ethernet Ports 28
3.11 CAN Ports 28
3.12 Console 29
3.13 Serial Ports 30
3.14 Ignition Key Sense 34
3.15 Accelerometer and Gyroscope 35
3.16 Storage memory 36
3.17 TPM and tpm2-tools package 36
3.18 Watchdog 36
3.19 RTC 37
3.20 Internal temperature sensors 37
3.21 User-programmable button and factory restore 38
3.22 CPU Unique ID 38
3.23 Power monitoring device 39
3.24 ITxPT services 41
3 Linux interfaces (EL 33) DynaGATE 10-14 EL Software Manual EN
3.1 Introduction
This section describes how to drive the interfaces of the system through the Eurotech Everyware Linux
Operating System (EL).
NOTICE
Some interfaces are available only for specific system variants. For more information, refer to
the system's Hardware Manual.
3.2 Getting the installed Linux version
To get the installed Linux version, execute the following command:
eurotech_versions
Example output:
root@dynagate-10-14::~# eurotech_versions -v
eth_model ............. DynaGATE 10-14
eth_serial_number ..... A1234567890
eth_vers_os ........... EL_33.x.x
eth_release ........... DEVELOPMENT_BUILD
eth_name_bsp .......... DynaGATE 10-14
eth_vers_bsp .......... 33.x.x
eth_date_bsp .......... 202304260915
eth_state_bsp ......... develop
eth_vers_cpu .......... ARM Cortex-A53 (v4) i.MX8MP
eth_arch_bsp .......... aarch64
eth_vers_uboot ........ U-Boot SPL 2021.04-5.10.35-2.0.0+g263b27e076 (Nov 22 2021 -
01:39:23 +0000)
eth_vers_linux ........ 5.10.72+g521a5aae687d #1 SMP PREEMPT Tue Nov 23 06:02:20 UTC
2021
eth_vers_yocto ........ 3.3.3
eth_vers_java ......... OpenJDK Zulu17.42+20-SA build 17.0.7+7-LTS
eth_vers_esf .......... ESF_x.x.x build x
eth_vers_docker ....... Docker version v19.03.15-ce, build 99e3ed8919
19 / 47 © 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
DynaGATE 10-14 EL Software Manual EN 3 Linux interfaces (EL 33)
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-2
Document revision: 1-2 (2023.11.28)
20 / 47
3.3 General Purpose I/O lines (GPIOs)
The general purpose I/O lines (GPIOs) provide functions such as the opto-isolated I/O channels and the
user LEDs which are available for use in application programs. The GPIOs provide also additional
support for interfaces such as expansion connector and power supply control.
These GPIOs are controlled using the sysfs filesystem which associates filenames with the various
GPIOs functions.
The GPIOs are represented by the following directories: /sys/class/gpio/gpioxxx, where xxx is
the number of the associated GPIO:
Filename Functions
value Get or set the value of the GPIO line (can be “0” or “1”)
direction Get or set the direction (can be “in” or “out”)
active_low Inverts the GPIO, when set to 1 writing 1 to value sets the GPIO pin to a low voltage level (can be “0” or “1”)
3.3.1 Using the GPIOs with the GPIO utility
The gpio_utility is a utility that builds upon the standard sysfs scheme to provide a more convenient
way to use many of the GPIOs functions from the command line:
gpio_utility pin_name function
pin_name It is the required GPIO line in the format gpioN or gpioBank_Pin.
function It can be set as follows:
0 or 1 to set the state of a GPIO output
in or out to set the direction of a GPIO
unexport to release the GPIO from sysfs(not normally required)
The GPIOs are exported by default at start-up.
3.3.2 Using the GPIOs with the “cat” and “echo” utilities
NOTICE
Appropriate values for direction and active_low are set during system initialization for each
GPIO and should not require further alteration.
To read and write to the GPIOs from the command line, use the “cat” and “echo” utilities, and execute the
following commands:
echo 1 >/sys/class/gpio/gpio504/value
cat /sys/class/gpio/gpio504/value
For details of the other files and sub-directories consult the Linux documentation at:
https://www.kernel.org/doc/Documentation/gpio/sysfs.txt
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47

Eurotech DynaGATE 10-14 Owner's manual

Type
Owner's manual

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI