Difference between revisions of "Subpart - STM32MP15 - Starter Package"

[quality revision] [quality revision]
m
m (Printing system information)
 

Template:ArticleMainWriter Template:ReviewersList Template:ArticleApprovedVersion

1 Article purpose[edit]

This article gathers the information that applies to any STM32MP15 board.

Warning white.png Warning
To start efficiently the board, it's recommended to go through the Starter Package article relative to your board: Category:Starter Package

That's the reason why the steps 2, 3 and 6 referenced in this article depend on the considered board:


2 Checking the boot sequence[edit]

Assuming you have performed the optional step 6 above, the information (coming successively from the U-Boot and the Linux operating system that is booting on the board), should be displayed on the host PC Terminal.

Info white.png Information
The information displayed below might differ from that on your own application, and should just be considered an example.
First information scrolled on the remote Terminal during boot
Last information scrolled on the remote Terminal during boot

In parallel, a U-Boot splash screen picture is displayed on the DSI display (if one is connected to the board).DSI U-Boot splash screen.png

A user space graphical boot splash screen (PSplash) picture is then briefly displayed on the HDMI monitor if one is connected to the board, or otherwise on the DSI display (if one is connected to the board).DSI user splash screen.png


When the boot process is complete, the Wayland background layer launcher application is shown on the HDMI monitor if one is connected to the board, or otherwise on the DSI display (if one is connected to the board).

File:STM32MP15 wayland background layer.png Wayland background
launcher application layer shown on the HDMI monitor or on the DSI display

More detail about this launcher application in GTK demo launcher page.

3 Mouse, keyboard and Ethernet hot-plugs[edit]

Let's assume that the optional step 2 and step 3 were not achieved when setting up the system above.

When connecting a USB mouse, the following information is displayed by the Terminal program:

[  926.786326] usb 2-1.1: new low-speed USB device number 3 using ehci-platform
[  926.961413] input: Logitech Optical USB Mouse as /devices/platform/soc/5800d000.usbh-ehci/usb2/2-1/2-1.1/2-1.1:1.0/0003:046D:C016.0001/input/input2
[  926.975098] hid-generic 0003:046D:C016.0001: input: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-5800d000.usbh-ehci-1.1/input0


When connecting a USB keyboard, the following information is displayed by the Terminal program:

[ 1009.026567] usb 2-1.3: new low-speed USB device number 4 using ehci-platform
[ 1009.193990] input: Dell Dell USB Keyboard as /devices/platform/soc/5800d000.usbh-ehci/usb2/2-1/2-1.3/2-1.3:1.0/0003:413C:2003.0002/input/input3
[ 1009.280101] hid-generic 0003:413C:2003.0002: input: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-5800d000.usbh-ehci-1.3/input0


When connecting an Ethernet cable, the following information is displayed by the Terminal program:

[ 1215.356377] stm32-dwmac 5800a000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 1215.363377] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1215.391068] Link is Up - 1000/Half

4 Remote and local Terminal programs[edit]

As already explained in the step 6 above, a remote Terminal program can be installed and configured on your host PC in order to communicate with the board through a serial link or an Ethernet link: see How to get Terminal.

The remote Terminal on your host PC can be used to enter command lines, as shown below with the ifconfig command to query the network interface parameters:

Example of command (ifconfig) executed on the remote Terminal program


A local Terminal program can be launched directly on the board. Click on the small icon at the top left corner of the display (see the red arrow on the figure below):

Icon to launch a local Terminal program
Wayland Terminal program


Then the on-board Wayland Terminal can be used to directly enter command lines as shown below, still with the ifconfig ip addr command to query the network interface parameters:

Example of command (ifconfigip addr) executed on the Wayland Terminal program


Consequently, unless an explicit restriction is mentioned, command lines can be run from both Terminals.

Note: in this article, any command executed on the board (through the remote Terminal or the Wayland Terminal) starts with , while any command executed on the host PC starts with .

5 Executing basic commands[edit]

Info white.png Information
The outputs of the commands executed below are examples; the outputs obtained might differ.

5.1 Having a look at the OpenSTLinux directory structure[edit]

The directory structure and directory contents in the OpenSTLinux distribution is standard. Some details are available in the OpenSTLinux directory structure article.

5.2 Identifying the software running on board[edit]

Info white.png Information
Obviously, what you obtain might differ from what is displayed on the Output example column.
5.2.1 For ecosystem release v2.1.0 More info.png[edit]
Software How to get its version Output example
TF-A TF-A Version number

NOTICE: BL2: v2.2-r2.0(debug):v2.

0

2-dirty

U-Boot See the version displayed in the console
U-Boot 2018.09

2020.01-stm32mp-r2 [...]

Linux kernel
 cat /proc/version

Linux version 5.4.

14.48

56 (xxxx@yyyy) (gcc version

7

9.3.0 (GCC)) [...]

GCC
 cat /proc/version

Linux version 5.4.

14.48

56 (xxxx@yyyy) (gcc version

7

9.3.0 (GCC)) [...]

Yocto Project
 
lsb
grep DISTRO_
release -c Codename: rocko
CODENAME /etc/build

DISTRO_CODENAME = dunfell

Weston
 weston --version

weston

2

8.0.0

GStreamer
 gst-play-1.0 --version

GStreamer 1.

12

16.2

GPU
 cat /sys/kernel/debug/gc/version

66.2.4.p3.174315

6.4.3.279124 built [...]

5.2.2 For ecosystem release v2.0.0 More info.png[edit]
Software How to get its version Output example
TF-A TF-A Version number

NOTICE: BL2: v2.2-r1.0(debug):v2.0-r3.0

U-Boot See the version displayed in the console

2020.01-stm32mp-r1 [...]

Linux kernel
 cat /proc/version

Linux version 5.4.31 (xxxx@yyyy) (gcc version 9.3.0 (GCC)) [...]

GCC
 cat /proc/version

Linux version 5.4.31 (xxxx@yyyy) (gcc version 9.3.0 (GCC)) [...]

Yocto Project
 grep DISTRO_CODENAME /etc/build

DISTRO_CODENAME = dunfell

Weston
 weston --version

weston 8.0.0

GStreamer
 gst-play-1.0 --version

GStreamer 1.16.2

GPU
 cat /sys/kernel/debug/gc/version

6.4.1.244507 built [...]

5.3 Configuration tips[edit]

5.4 Getting board IP address[edit]

Prerequisite: your board is connected to your local network through the Ethernet connector (see step 3).

 ip addr show eth0                                                                           
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
    inet 10xx.xx.xx.xx/22xx brd 10xx.xx.xx.xx scope global dynamic eth0
       valid_lft 159045sec preferred_lft 159045sec
    inet6 fe80xxxx::xx:xx:xx:xx/64xx scope link 
       valid_lft forever preferred_lft forever
  • Get the IP address of your board with the ifconfig Linux command line (a deprecated but well-known command):
 ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00xx:xx:xx:xx:xx:xx
          inet addr:10xx.xx.xx.xx  Bcast:10xx.xx.xx.xx  Mask:255.255.252.0
          inet6 addr: fe80xxxx::xx:xx:xx:xx/64xx Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2619 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1311 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:353250 (344.9 KiB)  TX bytes:118305 (115.5 KiB)
          Interrupt:247

5.5 Copying a file from your host PC to your board (and reciprocally)[edit]

5.6 Miscellaneous commands[edit]

Info white.png Information
The outputs of the commands executed below are examples; the outputs that you obtain might differ.

5.6.1 Printing distribution specific information[edit]

 lsb_release -a
LSB Version:    core-4.1-noarch:core-4.1-arm
Distributor ID: openstlinux-weston
Description:    ST OpenSTLinux - Weston - (A Yocto Project Based Distro) 2.4+openstlinux-4.14-rocko-mp1-18-11-26
Release:        2.4+openstlinux-4.14-rocko-mp1-18-11-26
Codename:       rocko

Where:

LSB Version Version of LSB (Linux Standard Base) against which distribution is compliant Distributor ID String identifier of distributor Description Single line text description of distribution Release Release number of distribution Codename Codename according to distribution
cat /etc/os-release 

ID="openstlinux-weston" NAME="ST OpenSTLinux - Weston - (A Yocto Project Based Distro)" VERSION="3.1-openstlinux-20-06-10-internal (dunfell)" VERSION_ID="3.1-openstlinux-20-06-10-internal" PRETTY_NAME="ST OpenSTLinux - Weston - (A Yocto Project Based Distro) 3.1-openstlinux-20-06-10-internal (dunfell)"

Where:

ID A lower-case string identifying the operating system
NAME A string identifying the operating system
VERSION A string identifying the operating system version, including a release code name
VERSION_ID A lower case string identifying the operating system version
PRETTY_NAME A full pretty name of the release

5.6.2 Printing system information[edit]

 uname -a
Linux stm32mp1-boards-rev[b/c] 4.14.48 5.4.56 #1 SMP PREEMPT TueWed NovAug 275 1407:4159:52 UTC 20182020 armv7l armv7l armv7l GNU/Linux

Where:

Linux Kernel name
stm32mp1-boards-rev[b/c] Network node hostname
5.4.14.4856 Kernel release
#1 SMP PREEMPT Tue Nov 27 14:41Wed Aug 5 07:59:52 UTC 20182020 Kernel version
armv7l Machine hardware name
GNU/Linux Operating system

5.6.3 Printing Linux kernel and GCC versions[edit]

 cat /proc/version
Linux version 5.4.14.4831 (xxxx@yyyy) (gcc version 79.3.0 (GCC)) #1 SMP PREEMPT TueWed NovApr 278 1407:4108:5247 UTC 20182020

Where:

Linux Kernel name
version 5.4.14.4831 Kernel release
(xxxx@yyyy) Person (xxxx) who compiled the kernel, and machine (yyyy) where it happened
(gcc version 79.3.0 (GCC) ) Version of the GCC compiler used to compile the kernel
#1 SMP PREEMPT Tue Nov 27 14:41:52 UTC 2018Wed Apr 8 07:08:47 UTC 2020 Kernel version; type of kernel (SMP) and date and time of the kernel compilation

5.6.4 Printing the amount of disk space available on all mounted file systems[edit]

 df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       719M  347M342M  334M339M  52%51% /
devtmpfs        372M     0  372M   0% /dev
tmpfs           436M     0  436M   0% /dev/shm
tmpfs           436M   14M  423M   4% /run
tmpfs           436M     0  436M   0% /sys/fs/cgroup
tmpfs           436M  4.0K  436M   1% /tmp
/dev/mmcblk0p4   58M  78.7M2M   46M  15%16% /boot
tmpfs/dev/mmcblk0p7  6.4G   68M  6.1G   2% 436M/usr/local
tmpfs 160K  436M   1% /var/volatile /dev/mmcblk0p7   15G436M  128K 14G 436M   1% 0 100% /usrvar/localvolatile
/dev/mmcblk0p5   15M  8.7M2M  45.7M3M  65%61% /vendor
tmpfs            88M     0   88M   0% /run/user/0

Where:

Filesystem Source of the mount point, usually a device
Size Total size in human readable format (e.g. 1K, 234M, 2G)
Used Used size in human readable format
Available Available size in human readable format
Use% Percentage of used size divided by the total size
Mounted on Mount point


Note: the user file system (userfs) and the boot file system (bootfs) are accessible respectively through the /usr/local mounting point, and the /boot mounting point (see Flash partitions for a description of the file systems).

<noinclude>
{{ArticleMainWriter | Jean-ChristopheT}}
{{ReviewersList | NathalieS, BernardP, DenisH}}  
{{ArticleApprovedVersion | Jean-ChristopheT | BernardP, DenisH, HuguesF | Jean-ChristopheT - 29Jan'18 | PhilipS - 29Aug'18 - 8426 | 03Sep'18}}

[[Category:Sub-articles]]
==Article purpose==
This article gathers the information that applies to any STM32MP15 board.

{{Warning|To start efficiently the board, it's recommended to go through the Starter Package article relative to your board: [[:Category:Starter Package]]}}

That's the reason why the steps 2, 3 and 6 referenced in this article depend on the considered board:{{UpdateNeededForNewBoard|Point to the steps of the new board Starter Package}}
* <span id{{=}}"step2">'''Step 2'''</span> is either [[STM32MP15 Evaluation boards - Starter Package#step2]] or [[STM32MP15 Discovery kits - Starter Package#step2]]
* <span id{{=}}"step3">'''Step 3'''</span> is either [[STM32MP15 Evaluation boards - Starter Package#step3]] or [[STM32MP15 Discovery kits - Starter Package#step3]]
* <span id{{=}}"step6">'''Step 6'''</span> is either [[STM32MP15 Evaluation boards - Starter Package#step6]] or [[STM32MP15 Discovery kits - Starter Package#step6]]</noinclude>


==Checking the boot sequence==
Assuming you have performed the optional [[#step6|step 6]] above, the information (coming successively from the U-Boot and the Linux operating system that is booting on the board), should be displayed on the host PC Terminal.
{{Info|The information displayed below might differ from that on your own application, and should just be considered an example.}}

[[File: STM32MP15_boot_information_1.png|thumb|upright=4|center|link=|First information scrolled on the remote Terminal during boot]]
[[File: STM32MP15_boot_information_2.png|thumb|upright=4|center|link=|Last information scrolled on the remote Terminal during boot]]

In parallel, a U-Boot splash screen picture is displayed on the DSI display (if one is connected to the board).[[File:DSI_U-Boot_splash_screen.png|link=]]

A user space graphical boot splash screen (PSplash) picture is then briefly displayed on the HDMI monitor if one is connected to the board, or otherwise on the DSI display (if one is connected to the board).[[File:DSI_user_splash_screen.png|link=]]

When the boot process is complete, the Wayland background layer launcher application is shown on the HDMI monitor if one is connected to the board, or otherwise on the DSI display (if one is connected to the board).

[[File: STM32MP15_wayland_background_layerlauncher_main_menu.png|thumb|upright=4|center|link=|Wayland backgroundlauncher application layer shown on the HDMI monitor or on the DSI display]]
More detail about this launcher application in [[GTK demo launcher]] page.
==Mouse, keyboard and Ethernet hot-plugs==
Let's assume that the optional [[#step2|step 2]] and [[#step3|step 3]] were not achieved when setting up the system above.

When connecting a USB mouse, the following information is displayed by the Terminal program:
 [  926.786326] usb 2-1.1: new low-speed USB device number 3 using ehci-platform
 [  926.961413] input: Logitech Optical USB Mouse as /devices/platform/soc/5800d000.usbh-ehci/usb2/2-1/2-1.1/2-1.1:1.0/0003:046D:C016.0001/input/input2
 [  926.975098] hid-generic 0003:046D:C016.0001: input: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-5800d000.usbh-ehci-1.1/input0
<br>

When connecting a USB keyboard, the following information is displayed by the Terminal program:
 [ 1009.026567] usb 2-1.3: new low-speed USB device number 4 using ehci-platform
 [ 1009.193990] input: Dell Dell USB Keyboard as /devices/platform/soc/5800d000.usbh-ehci/usb2/2-1/2-1.3/2-1.3:1.0/0003:413C:2003.0002/input/input3
 [ 1009.280101] hid-generic 0003:413C:2003.0002: input: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-5800d000.usbh-ehci-1.3/input0
<br>

When connecting an Ethernet cable, the following information is displayed by the Terminal program:
 [ 1215.356377] stm32-dwmac 5800a000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
 [ 1215.363377] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [ 1215.391068] Link is Up - 1000/Half

==Remote and local Terminal programs==
As already explained in the [[#step6|step 6]] above, a '''remote Terminal''' program can be installed and configured on your host PC in order to communicate with the board through a serial link or an Ethernet link: see [[How to get Terminal]].

The remote Terminal on your host PC can be used to enter command lines, as shown below with the ''ifconfig'' command to query the network interface parameters:

[[File: STM32MP15_example_command_remote_terminal.png|thumb|upright=4|center|link=|Example of command (''ifconfig'') executed on the remote Terminal program]]<br>


A '''local Terminal''' program can be launched directly on the board. Click on the small icon at the top left corner of the display (see the red arrow on the figure below):

[[File: STM32MP15_local_terminal_icon.png|thumb|upright=4|center|link=|Icon to launch a local Terminal program]]
[[File: STM32MP15_wayland_terminal.png|thumb|upright=4|center|link=|Wayland Terminal program]]<br>


Then the on-board Wayland Terminal can be used to directly enter command lines as shown below, still with the ''ifconfigip addr'' command to query the network interface parameters:

[[File: STM32MP15_example_command_local_terminal.png|thumb|upright=4|center|link=|Example of command (''ifconfigip addr'') executed on the Wayland Terminal program]]<br>


Consequently, unless an explicit restriction is mentioned, command lines can be run from both Terminals. 

Note: in this article, any command executed on the board (through the remote Terminal or the Wayland Terminal) starts with {{Board$}}, while any command executed on the host PC starts with {{PC$}}.

==Executing basic commands==
{{Info|The outputs of the commands executed below are examples; the outputs obtained might differ.}}

===Having a look at the OpenSTLinux directory structure===
The directory structure and directory contents in the OpenSTLinux distribution is standard. Some details are available in the [[OpenSTLinux directory structure]] article.

===Identifying the software running on board===

{{Info|Obviously, what you obtain might differ from what is displayed on the ''Output example'' column.}} {{UpdateNeededForNewRelease|The "Output example" column below shall be updated periodically, even if the information banner specifies that this column might not be up-to-date}}
{| class="wikitable"
! Software !! ======For {{EcosystemRelease | revision=2.1.0 }}======
{| class="st-table"
! style="text-align:center;" |Software !! style="text-align:center;" |How to get its version !! style="text-align:center;" |Output example
|-
| TF-A || [[TF-A - How to debug#TF-A Version number|TF-A Version number]] ||
NOTICE:  BL2: v2.2-r2.0(debug):{{Highlight|v2.02-dirty}}
|-
| U-Boot || See the version displayed in the console ||
{{Highlight|U-Boot 2018.092020.01-stm32mp-r2}} [...]
|-
| Linux kernel ||
 {{Board$}} cat /proc/version
||
{{Highlight|Linux version 5.4.14.4856}} (xxxx@yyyy) (gcc version 79.3.0 (GCC)) [...]
|-
| GCC ||
 {{Board$}} cat /proc/version
||
Linux version 5.4.14.4856 (xxxx@yyyy) ({{Highlight|gcc version 79.3.0 (GCC)}}) [...]
|-
| Yocto Project ||
 {{Board$}} lsb_release -c
||
Codename:       {{Highlight|rocko}}
|-
| grep DISTRO_CODENAME /etc/build
||
DISTRO_CODENAME = {{Highlight|dunfell}}
|-
| Weston ||
 {{Board$}} weston --version
||
{{Highlight|weston 8.0.0}}
|-
| GStreamer ||
 {{Board$}} gst-play-1.0 --version
||
{{Highlight|GStreamer 1.16.2}}
|-
| GPU ||
 {{Board$}} cat /sys/kernel/debug/gc/version
||
{{Highlight|6.4.3.279124}} built [...]
|}

======For {{EcosystemRelease | revision=2.0.0 }}======
{| class="st-table"
! style="text-align:center;" |Software !! style="text-align:center;" |How to get its version !! style="text-align:center;" |Output example
|-
| TF-A || [[TF-A - How to debug#TF-A Version number|TF-A Version number]] ||
NOTICE:  BL2: v2.2-r1.0(debug):{{Highlight|v2.0-r3.0}}
|-
| U-Boot || See the version displayed in the console ||
{{Highlight|2020.01-stm32mp-r1}} [...]
|-
| Linux kernel ||
 {{Board$}} cat /proc/version
||
{{Highlight|Linux version 5.4.31}} (xxxx@yyyy) (gcc version 9.3.0 (GCC)) [...]
|-
| GCC ||
 {{Board$}} cat /proc/version
||
Linux version 5.4.31 (xxxx@yyyy) ({{Highlight|gcc version 9.3.0 (GCC)}}) [...]
|-
| Yocto Project ||
 {{Board$}} grep DISTRO_CODENAME /etc/build
||
DISTRO_CODENAME = {{Highlight|dunfell}}
|-
| Weston ||
 {{Board$}} weston --version
||
{{Highlight|weston 28.0.0}}
|-
| GStreamer ||
 {{Board$}} gst-play-1.0 --version
||
{{Highlight|GStreamer 1.1216.2}}
|-
| GPU ||
 {{Board$}} cat /sys/kernel/debug/gc/version
||
{{Highlight|66.2.6.4.p3.1743151.244507}} built [...]
|}

===Configuration tips===
* [[Wayland Weston overview#Configuration|Configure the keyboard layout (qwerty, azerty...)]]

===Getting board IP address===
Prerequisite: your board is connected to your local network through the Ethernet connector (see [[#step3|step 3]]).

* Get the IP address of your board with the [[IP Linux command line|''ip'' Linux command line]] ({{highlight|recommended method}}):
 {{Board$}} ip addr show eth0                                                                           
 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
     link/ether 00xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
     inet {{highlight|10xx.xx.xx.xx}}/22xx brd 10xx.xx.xx.xx scope global dynamic eth0
        valid_lft 159045sec preferred_lft 159045sec
     inet6 fe80xxxx::xx:xx:xx:xx/64xx scope link 
        valid_lft forever preferred_lft forever

* Get the IP address of your board with the [[Ifconfig|''ifconfig'']] Linux command line (a deprecated but well-known command):
 {{Board$}} ifconfig eth0
 eth0      Link encap:Ethernet  HWaddr 00xx:xx:xx:xx:xx:xx
           inet addr:{{highlight|10xx.xx.xx.xx}}  Bcast:10xx.xx.xx.xx  Mask:255.255.252.0
           inet6 addr: fe80xxxx::xx:xx:xx:xx/64xx Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:2619 errors:0 dropped:0 overruns:0 frame:0
           TX packets:1311 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:353250 (344.9 KiB)  TX bytes:118305 (115.5 KiB)
           Interrupt:247

===Copying a file from your host PC to your board (and reciprocally)===
* [[How to transfer a file over network]] ({{highlight|recommended method}})

* [[How to transfer a file over serial console]]

===Miscellaneous commands===
{{Info|The outputs of the commands executed below are examples; the outputs that you obtain might differ.}}{{UpdateNeededForNewRelease|The outputs of the commands below shall be updated periodically, even if the information banner specifies that these outputs might not be up-to-date}}

====Printing distribution specific information====
 {{Board$}} lsb_release -a
 LSB Version:    core-4.1-noarch:core-4.1-arm
 Distributor ID: openstlinux-weston
 Description:    cat /etc/os-release 
ID="openstlinux-weston"
NAME="ST OpenSTLinux - Weston - (A Yocto Project Based Distro) 2.4+openstlinux-4.14-rocko-mp1-18-11-26
 Release:        2.4+openstlinux-4.14-rocko-mp1-18-11-26
 Codename:       rocko

Where:
{|
| LSB Version || Version of LSB (Linux Standard Base) against which distribution is compliant
|-
| Distributor ID || String identifier of distributor
|-
| Description || Single line text description of distribution
|-
| Release || Release number of distribution
|-
| Codename || Codename according to distribution "
VERSION="3.1-openstlinux-20-06-10-internal (dunfell)"
VERSION_ID="3.1-openstlinux-20-06-10-internal"
PRETTY_NAME="ST OpenSTLinux - Weston - (A Yocto Project Based Distro) 3.1-openstlinux-20-06-10-internal (dunfell)"

Where:
{|
| ID || A lower-case string identifying the operating system
|-
| NAME || A string identifying the operating system
|-
| VERSION || A string identifying the operating system version, including a release code name
|-
| VERSION_ID || A lower case string identifying the operating system version
|-
| PRETTY_NAME || A full pretty name of the release
|}

====Printing system information====
 {{Board$}} uname -a
 Linux stm32mp1-boards-rev[b/c] 4.14.48 #1 SMP PREEMPT Tue Nov 27 14:41:52 UTC 2018 5.4.56 #1 SMP PREEMPT Wed Aug 5 07:59:52 UTC 2020 armv7l armv7l armv7l GNU/Linux

Where:
{|
| Linux || Kernel name
|-
| stm32mp1-boards-rev[b/c] || Network node hostname
|-
| 5.4.14.4856 || Kernel release
|-
| &#35;1 SMP PREEMPT Tue Nov 27 14:41:52 UTC 2018Wed Aug 5 07:59:52 UTC 2020 || Kernel version
|-
| armv7l || Machine hardware name
|-
| GNU/Linux || Operating system 
|}

====Printing Linux kernel and GCC versions====
 {{Board$}} cat /proc/version
 Linux version 5.4.14.4831 (xxxx@yyyy) (gcc version 79.3.0 (GCC)) #1 SMP PREEMPT Tue Nov 27 14:41:52 UTC 2018Wed Apr 8 07:08:47 UTC 2020


Where:
{|
| Linux || Kernel name
|-
| version 5.4.14.4831 ||Kernel release
|-
| (xxxx@yyyy) || Person (xxxx) who compiled the kernel, and machine (yyyy) where it happened
|-
| (gcc version 79.3.0 (GCC) ) || Version of the GCC compiler used to compile the kernel
|-
| &#35;1 SMP PREEMPT Tue Nov 27 14:41:52 UTC 2018Wed Apr 8 07:08:47 UTC 2020 || Kernel version; type of kernel (SMP) and date and time of the kernel compilation
|}

====Printing the amount of disk space available on all mounted file systems====
 {{Board$}} df -h
 Filesystem      Size  Used Avail Use% Mounted on
 /dev/root       719M  347M  334M  52%342M  339M  51% /
 devtmpfs        372M     0  372M   0% /dev
 tmpfs           436M     0  436M   0% /dev/shm
 tmpfs           436M   14M  423M   4% /run
 tmpfs           436M     0  436M   0% /sys/fs/cgroup
 tmpfs           436M  4.0K  436M   1% /tmp
 /dev/mmcblk0p4   58M  7.7M8.2M   46M  15%16% /boottmpfs           436M  160K  436M   1% /var/volatile
 /dev/mmcblk0p7   15G   14G     0 100% /usr/local/dev/mmcblk0p7  6.4G   68M  6.1G   2% /usr/local
 tmpfs           436M  128K  436M   1% /var/volatile

 /dev/mmcblk0p5   15M  8.7M  4.7M  65%2M  5.3M  61% /vendor
 tmpfs            88M     0   88M   0% /run/user/0

Where:
{|
| Filesystem || Source of the mount point, usually a device
|-
| Size || Total size in human readable format (e.g. 1K, 234M, 2G)
|-
| Used ||Used size in human readable format
|-
| Available || Available size in human readable format
|-
| Use% ||Percentage of used size divided by the total size
|-
| Mounted on || Mount point
|}
<br>

Note: the user file system (userfs) and the boot file system (bootfs) are accessible respectively through the ''/usr/local'' mounting point, and the ''/boot'' mounting point (see [[STM32MP15 Flash mapping#Flash partitions|Flash partitions]] for a description of the file systems).

<noinclude>

{{NoIndex}}
[[Category:Sub-articles]]</noinclude>
(20 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
<noinclude>
 
<noinclude>
{{ArticleMainWriter | Jean-ChristopheT}}
 
{{ReviewersList | NathalieS, BernardP, DenisH}} 
 
{{ArticleApprovedVersion | Jean-ChristopheT | BernardP, DenisH, HuguesF | Jean-ChristopheT - 29Jan'18 | PhilipS - 29Aug'18 - 8426 | 03Sep'18}}
 
 
[[Category:Sub-articles]]
 
 
 
==Article purpose==
 
==Article purpose==
 
This article gathers the information that applies to any STM32MP15 board.
 
This article gathers the information that applies to any STM32MP15 board.
Line 29: Line 23:
   
   
When the boot process is complete, the Wayland background layer is shown on the HDMI monitor if one is connected to the board, or otherwise on the DSI display (if one is connected to the board).
+
When the boot process is complete, the launcher application is shown on the HDMI monitor if one is connected to the board, or otherwise on the DSI display (if one is connected to the board).
   
[[File: STM32MP15_wayland_background_layer.png|thumb|upright=4|center|link=|Wayland background layer shown on the HDMI monitor or on the DSI display]]
+
[[File: STM32MP15_launcher_main_menu.png|thumb|upright=4|center|link=|launcher application layer shown on the HDMI monitor or on the DSI display]]
  +
More detail about this launcher application in [[GTK demo launcher]] page.
   
 
==Mouse, keyboard and Ethernet hot-plugs==
 
==Mouse, keyboard and Ethernet hot-plugs==
Line 67: Line 62:
 
<br>
 
<br>
   
Then the on-board Wayland Terminal can be used to directly enter command lines as shown below, still with the ''ifconfig'' command to query the network interface parameters:
+
Then the on-board Wayland Terminal can be used to directly enter command lines as shown below, still with the ''ip addr'' command to query the network interface parameters:
   
[[File: STM32MP15_example_command_local_terminal.png|thumb|upright=4|center|link=|Example of command (''ifconfig'') executed on the Wayland Terminal program]]
+
[[File: STM32MP15_example_command_local_terminal.png|thumb|upright=4|center|link=|Example of command (''ip addr'') executed on the Wayland Terminal program]]
 
<br>
 
<br>
   
Line 86: Line 81:
 
{{Info|Obviously, what you obtain might differ from what is displayed on the ''Output example'' column.}} {{UpdateNeededForNewRelease|The "Output example" column below shall be updated periodically, even if the information banner specifies that this column might not be up-to-date}}
 
{{Info|Obviously, what you obtain might differ from what is displayed on the ''Output example'' column.}} {{UpdateNeededForNewRelease|The "Output example" column below shall be updated periodically, even if the information banner specifies that this column might not be up-to-date}}
   
{| class="wikitable"
+
======For {{EcosystemRelease | revision=2.1.0 }}======
! Software !! How to get its version !! Output example
+
{| class="st-table"
  +
! style="text-align:center;" |Software !! style="text-align:center;" |How to get its version !! style="text-align:center;" |Output example
 
|-
 
|-
 
| TF-A || [[TF-A - How to debug#TF-A Version number|TF-A Version number]] ||
 
| TF-A || [[TF-A - How to debug#TF-A Version number|TF-A Version number]] ||
NOTICE:  BL2: v2.0(debug):{{Highlight|v2.0-dirty}}
+
NOTICE:  BL2: v2.2-r2.0(debug):{{Highlight|v2.2-dirty}}
 
|-
 
|-
 
| U-Boot || See the version displayed in the console ||
 
| U-Boot || See the version displayed in the console ||
{{Highlight|U-Boot 2018.09-stm32mp-r2}} [...]
+
{{Highlight|2020.01-stm32mp-r2}} [...]
 
|-
 
|-
 
| Linux kernel ||
 
| Linux kernel ||
 
  {{Board$}} cat /proc/version
 
  {{Board$}} cat /proc/version
 
||
 
||
{{Highlight|Linux version 4.14.48}} (xxxx@yyyy) (gcc version 7.3.0 (GCC)) [...]
+
{{Highlight|Linux version 5.4.56}} (xxxx@yyyy) (gcc version 9.3.0 (GCC)) [...]
 
|-
 
|-
 
| GCC ||
 
| GCC ||
 
  {{Board$}} cat /proc/version
 
  {{Board$}} cat /proc/version
 
||
 
||
Linux version 4.14.48 (xxxx@yyyy) ({{Highlight|gcc version 7.3.0 (GCC)}}) [...]
+
Linux version 5.4.56 (xxxx@yyyy) ({{Highlight|gcc version 9.3.0 (GCC)}}) [...]
 
|-
 
|-
 
| Yocto Project ||
 
| Yocto Project ||
  {{Board$}} lsb_release -c
+
  {{Board$}} grep DISTRO_CODENAME /etc/build
 
||
 
||
Codename:      {{Highlight|rocko}}
+
DISTRO_CODENAME = {{Highlight|dunfell}}
 
|-
 
|-
 
| Weston ||
 
| Weston ||
 
  {{Board$}} weston --version
 
  {{Board$}} weston --version
 
||
 
||
{{Highlight|weston 2.0.0}}
+
{{Highlight|weston 8.0.0}}
 
|-
 
|-
 
| GStreamer ||
 
| GStreamer ||
 
  {{Board$}} gst-play-1.0 --version
 
  {{Board$}} gst-play-1.0 --version
 
||
 
||
{{Highlight|GStreamer 1.12.2}}
+
{{Highlight|GStreamer 1.16.2}}
 
|-
 
|-
 
| GPU ||
 
| GPU ||
 
  {{Board$}} cat /sys/kernel/debug/gc/version
 
  {{Board$}} cat /sys/kernel/debug/gc/version
 
||
 
||
{{Highlight|66.2.4.p3.174315}} built [...]
+
{{Highlight|6.4.3.279124}} built [...]
  +
|}
  +
 
  +
======For {{EcosystemRelease | revision=2.0.0 }}======
  +
{| class="st-table"
  +
! style="text-align:center;" |Software !! style="text-align:center;" |How to get its version !! style="text-align:center;" |Output example
  +
|-
  +
| TF-A || [[TF-A - How to debug#TF-A Version number|TF-A Version number]] ||
  +
NOTICE:  BL2: v2.2-r1.0(debug):{{Highlight|v2.0-r3.0}}
  +
|-
  +
| U-Boot || See the version displayed in the console ||
  +
{{Highlight|2020.01-stm32mp-r1}} [...]
  +
|-
  +
| Linux kernel ||
  +
{{Board$}} cat /proc/version
  +
||
  +
{{Highlight|Linux version 5.4.31}} (xxxx@yyyy) (gcc version 9.3.0 (GCC)) [...]
  +
|-
  +
| GCC ||
  +
{{Board$}} cat /proc/version
  +
||
  +
Linux version 5.4.31 (xxxx@yyyy) ({{Highlight|gcc version 9.3.0 (GCC)}}) [...]
  +
|-
  +
| Yocto Project ||
  +
{{Board$}} grep DISTRO_CODENAME /etc/build
  +
||
  +
DISTRO_CODENAME = {{Highlight|dunfell}}
  +
|-
  +
| Weston ||
  +
{{Board$}} weston --version
  +
||
  +
{{Highlight|weston 8.0.0}}
  +
|-
  +
| GStreamer ||
  +
{{Board$}} gst-play-1.0 --version
  +
||
  +
{{Highlight|GStreamer 1.16.2}}
  +
|-
  +
| GPU ||
  +
{{Board$}} cat /sys/kernel/debug/gc/version
  +
||
  +
{{Highlight|6.4.1.244507}} built [...]
 
|}
 
|}
   
Line 135: Line 172:
 
  {{Board$}} ip addr show eth0                                                                           
 
  {{Board$}} ip addr show eth0                                                                           
 
  3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
 
  3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
     link/ether 00:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
+
     link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
     inet {{highlight|10.xx.xx.xx}}/22 brd 10.xx.xx.xx scope global dynamic eth0
+
     inet {{highlight|xx.xx.xx.xx}}/xx brd xx.xx.xx.xx scope global dynamic eth0
 
         valid_lft 159045sec preferred_lft 159045sec
 
         valid_lft 159045sec preferred_lft 159045sec
     inet6 fe80::xx:xx:xx:xx/64 scope link  
+
     inet6 xxxx::xx:xx:xx:xx/xx scope link  
 
         valid_lft forever preferred_lft forever
 
         valid_lft forever preferred_lft forever
   
 
* Get the IP address of your board with the [[Ifconfig|''ifconfig'']] Linux command line (a deprecated but well-known command):
 
* Get the IP address of your board with the [[Ifconfig|''ifconfig'']] Linux command line (a deprecated but well-known command):
 
  {{Board$}} ifconfig eth0
 
  {{Board$}} ifconfig eth0
  eth0      Link encap:Ethernet  HWaddr 00:xx:xx:xx:xx:xx
+
  eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
           inet addr:{{highlight|10.xx.xx.xx}}  Bcast:10.xx.xx.xx  Mask:255.255.252.0
+
           inet addr:{{highlight|xx.xx.xx.xx}}  Bcast:xx.xx.xx.xx  Mask:255.255.252.0
           inet6 addr: fe80::xx:xx:xx:xx/64 Scope:Link
+
           inet6 addr: xxxx::xx:xx:xx:xx/xx Scope:Link
 
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
 
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
 
           RX packets:2619 errors:0 dropped:0 overruns:0 frame:0
 
           RX packets:2619 errors:0 dropped:0 overruns:0 frame:0
Line 162: Line 199:
   
 
====Printing distribution specific information====
 
====Printing distribution specific information====
  {{Board$}} lsb_release -a
+
  {{Board$}} cat /etc/os-release
LSB Version:    core-4.1-noarch:core-4.1-arm
+
ID="openstlinux-weston"
Distributor ID: openstlinux-weston
+
NAME="ST OpenSTLinux - Weston - (A Yocto Project Based Distro)"
Description:    ST OpenSTLinux - Weston - (A Yocto Project Based Distro) 2.4+openstlinux-4.14-rocko-mp1-18-11-26
+
VERSION="3.1-openstlinux-20-06-10-internal (dunfell)"
Release:        2.4+openstlinux-4.14-rocko-mp1-18-11-26
+
VERSION_ID="3.1-openstlinux-20-06-10-internal"
Codename:      rocko
+
PRETTY_NAME="ST OpenSTLinux - Weston - (A Yocto Project Based Distro) 3.1-openstlinux-20-06-10-internal (dunfell)"
   
 
Where:
 
Where:
 
{|
 
{|
| LSB Version || Version of LSB (Linux Standard Base) against which distribution is compliant
+
| ID || A lower-case string identifying the operating system
 
|-
 
|-
| Distributor ID || String identifier of distributor
+
| NAME || A string identifying the operating system
 
|-
 
|-
| Description || Single line text description of distribution
+
| VERSION || A string identifying the operating system version, including a release code name
 
|-
 
|-
| Release || Release number of distribution
+
| VERSION_ID || A lower case string identifying the operating system version
 
|-
 
|-
| Codename || Codename according to distribution release
+
| PRETTY_NAME || A full pretty name of the release
 
|}
 
|}
   
 
====Printing system information====
 
====Printing system information====
 
  {{Board$}} uname -a
 
  {{Board$}} uname -a
  Linux stm32mp1-boards-rev[b/c] 4.14.48 #1 SMP PREEMPT Tue Nov 27 14:41:52 UTC 2018 armv7l armv7l armv7l GNU/Linux
+
  Linux stm32mp1 5.4.56 #1 SMP PREEMPT Wed Aug 5 07:59:52 UTC 2020 armv7l armv7l armv7l GNU/Linux
   
 
Where:
 
Where:
Line 190: Line 227:
 
| Linux || Kernel name
 
| Linux || Kernel name
 
|-
 
|-
| stm32mp1-boards-rev[b/c] || Network node hostname
+
| stm32mp1 || Network node hostname
 
|-
 
|-
| 4.14.48 || Kernel release
+
| 5.4.56 || Kernel release
 
|-
 
|-
| &#35;1 SMP PREEMPT Tue Nov 27 14:41:52 UTC 2018 || Kernel version
+
| &#35;1 SMP PREEMPT Wed Aug 5 07:59:52 UTC 2020 || Kernel version
 
|-
 
|-
 
| armv7l || Machine hardware name
 
| armv7l || Machine hardware name
Line 203: Line 240:
 
====Printing Linux kernel and GCC versions====
 
====Printing Linux kernel and GCC versions====
 
  {{Board$}} cat /proc/version
 
  {{Board$}} cat /proc/version
  Linux version 4.14.48 (xxxx@yyyy) (gcc version 7.3.0 (GCC)) #1 SMP PREEMPT Tue Nov 27 14:41:52 UTC 2018
+
  Linux version 5.4.31 (xxxx@yyyy) (gcc version 9.3.0 (GCC)) #1 SMP PREEMPT Wed Apr 8 07:08:47 UTC 2020
   
 
Where:
 
Where:
Line 209: Line 246:
 
| Linux || Kernel name
 
| Linux || Kernel name
 
|-
 
|-
| version 4.14.48 ||Kernel release
+
| version 5.4.31 ||Kernel release
 
|-
 
|-
 
| (xxxx@yyyy) || Person (xxxx) who compiled the kernel, and machine (yyyy) where it happened
 
| (xxxx@yyyy) || Person (xxxx) who compiled the kernel, and machine (yyyy) where it happened
 
|-
 
|-
| (gcc version 7.3.0 (GCC) ) || Version of the GCC compiler used to compile the kernel
+
| (gcc version 9.3.0 (GCC) ) || Version of the GCC compiler used to compile the kernel
 
|-
 
|-
| &#35;1 SMP PREEMPT Tue Nov 27 14:41:52 UTC 2018 || Kernel version; type of kernel (SMP) and date and time of the kernel compilation
+
| &#35;1 SMP PREEMPT Wed Apr 8 07:08:47 UTC 2020 || Kernel version; type of kernel (SMP) and date and time of the kernel compilation
 
|}
 
|}
   
Line 221: Line 258:
 
  {{Board$}} df -h
 
  {{Board$}} df -h
 
  Filesystem      Size  Used Avail Use% Mounted on
 
  Filesystem      Size  Used Avail Use% Mounted on
  /dev/root      719M  347M 334M 52% /
+
  /dev/root      719M  342M 339M 51% /
 
  devtmpfs        372M    0  372M  0% /dev
 
  devtmpfs        372M    0  372M  0% /dev
 
  tmpfs          436M    0  436M  0% /dev/shm
 
  tmpfs          436M    0  436M  0% /dev/shm
Line 227: Line 264:
 
  tmpfs          436M    0  436M  0% /sys/fs/cgroup
 
  tmpfs          436M    0  436M  0% /sys/fs/cgroup
 
  tmpfs          436M  4.0K  436M  1% /tmp
 
  tmpfs          436M  4.0K  436M  1% /tmp
  /dev/mmcblk0p4  58M  7.7M   46M  15% /boot
+
  /dev/mmcblk0p4  58M  8.2M   46M  16% /boot
  tmpfs          436M  160K 436M  1% /var/volatile
+
/dev/mmcblk0p7  6.4G  68M  6.1G  2% /usr/local
/dev/mmcblk0p7  15G  14G    0 100% /usr/local
+
  tmpfs          436M  128K 436M  1% /var/volatile
  /dev/mmcblk0p5  15M  8.7M 4.7M 65% /vendor
+
  /dev/mmcblk0p5  15M  8.2M 5.3M 61% /vendor
 
  tmpfs            88M    0  88M  0% /run/user/0
 
  tmpfs            88M    0  88M  0% /run/user/0
   
Line 250: Line 287:
 
<br>
 
<br>
 
Note: the user file system (userfs) and the boot file system (bootfs) are accessible respectively through the ''/usr/local'' mounting point, and the ''/boot'' mounting point (see [[STM32MP15 Flash mapping#Flash partitions|Flash partitions]] for a description of the file systems).
 
Note: the user file system (userfs) and the boot file system (bootfs) are accessible respectively through the ''/usr/local'' mounting point, and the ''/boot'' mounting point (see [[STM32MP15 Flash mapping#Flash partitions|Flash partitions]] for a description of the file systems).
  +
  +
<noinclude>
  +
{{NoIndex}}
  +
[[Category:Sub-articles]]
  +
</noinclude>