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

[checked revision] [quality revision]
m


1 Article purpose[edit]

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

Warning.png 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.png 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 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).

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 ip addr command to query the network interface parameters:

Example of command (ip 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 Board $>, while any command executed on the host PC starts with PC $>.

5 Executing basic commands[edit]

Info.png 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.png Obviously, what you obtain might differ from what is displayed on the Output example column.
5.2.1 For ecosystem release v1.1.0 More info.png[edit]
Software How to get its version Output example
TF-A TF-A Version number

NOTICE: BL2: v2.0-r1.5(debug):v2.0-r1.5

U-Boot See the version displayed in the console

U-Boot 2018.11-stm32mp-r3 [...]

Linux kernel
Board $> cat /proc/version

Linux version 4.19.49 (xxxx@yyyy) (gcc version 8.2.0 (GCC)) [...]

GCC
Board $> cat /proc/version

Linux version 4.19.49 (xxxx@yyyy) (gcc version 8.2.0 (GCC)) [...]

Yocto Project
Board $> lsb_release -c

Codename: thud

Weston
Board $> weston --version

weston 5.0.0

GStreamer
Board $> gst-play-1.0 --version

GStreamer 1.14.4

GPU
Board $> cat /sys/kernel/debug/gc/version

6.2.4.p4.190076 built [...]

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

NOTICE: BL2: v2.0(debug):v2.0-dirty

U-Boot See the version displayed in the console

U-Boot 2018.11-stm32mp-r2 [...]

Linux kernel
Board $> cat /proc/version

Linux version 4.19.9 (xxxx@yyyy) (gcc version 8.2.0 (GCC)) [...]

GCC
Board $> cat /proc/version

Linux version 4.19.9 (xxxx@yyyy) (gcc version 8.2.0 (GCC)) [...]

Yocto Project
Board $> lsb_release -c

Codename: thud

Weston
Board $> weston --version

weston 5.0.0

GStreamer
Board $> gst-play-1.0 --version

GStreamer 1.14.2

GPU
Board $> cat /sys/kernel/debug/gc/version

6.2.4.p3.174315 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).

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 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):
Board $> 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.png The outputs of the commands executed below are examples; the outputs that you obtain might differ.

5.6.1 Printing distribution specific information[edit]

Board $> lsb_release -a
LSB Version:    core-5.0-noarch:core-5.0-arm
Distributor ID: openstlinux-weston
Description:    ST OpenSTLinux - Weston - (A Yocto Project Based Distro) 2.6-...
Release:        2.6...
Codename:       thud

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 release

5.6.2 Printing system information[edit]

Board $> uname -a
Linux stm32mp1 4.19.49 #1 SMP PREEMPT Sun Jun 9 07:17:25 UTC 2019 armv7l armv7l  armv7l GNU/Linux

Where:

Linux Kernel name
stm32mp1 Network node hostname
4.19.49 Kernel release
#1 SMP PREEMPT Sun Jun 9 07:17:25 UTC 2019 Kernel version
armv7l Machine hardware name
GNU/Linux Operating system

5.6.3 Printing Linux kernel and GCC versions[edit]

Board $> cat /proc/version
Linux version 4.19.49 (xxxx@yyyy) (gcc version 8.2.0 (GCC)) #1 SMP PREEMPT Sun Jun 9 07:17:25 UTC 2019

Where:

Linux Kernel name
version 4.19.49 Kernel release
(xxxx@yyyy) Person (xxxx) who compiled the kernel, and machine (yyyy) where it happened
(gcc version 8.2.0 (GCC) ) Version of the GCC compiler used to compile the kernel
#1 SMP PREEMPT Sun Jun 9 07:17:25 UTC 2019 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]

Board $> df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       719M  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  8.2M   46M  16% /boot
/dev/mmcblk0p7  6.4G   68M  6.1G   2% /usr/local
tmpfs           436M  128K  436M   1% /var/volatile
/dev/mmcblk0p5   15M  8.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


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>__NOINDEX__

==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 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_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==
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:
{{ReviewsComments| CPR IP address to change}}[[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 ''ip addr'' command to query the network interface parameters:

[[File: STM32MP15_example_command_local_terminal.png|thumb|upright=4|center|link=|Example of command (''ip 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}}

======For {{EcosystemRelease | revision=1.1.0 }}======
{| class="wikitable"
! Software !! How to get its version !! Output example
|-
| TF-A || [[TF-A - How to debug#TF-A Version number|TF-A Version number]] ||
NOTICE:  BL2: v2.0-r1.5(debug):{{Highlight|v2.0-r1.5}}
|-
| U-Boot || See the version displayed in the console ||
{{Highlight|U-Boot 2018.11-stm32mp-r3}} [...]
|-
| Linux kernel ||
 {{Board$}} cat /proc/version
||
{{Highlight|Linux version 4.19.49}} (xxxx@yyyy) (gcc version 8.2.0 (GCC)) [...]
|-
| GCC ||
 {{Board$}} cat /proc/version
||
Linux version 4.19.49 (xxxx@yyyy) ({{Highlight|gcc version 8.2.0 (GCC)}}) [...]
|-
| Yocto Project ||
 {{Board$}} lsb_release -c
||
Codename:       {{Highlight|thud}}
|-
| Weston ||
 {{Board$}} weston --version
||
{{Highlight|weston 5.0.0}}
|-
| GStreamer ||
 {{Board$}} gst-play-1.0 --version
||
{{Highlight|GStreamer 1.14.4}}
|-
| GPU ||
 {{Board$}} cat /sys/kernel/debug/gc/version
||
{{Highlight|6.2.4.p4.190076}} built [...]
|}<div class="mw-collapsible mw-collapsed">


======For {{EcosystemRelease | revision=1.0.0}}======<div class="mw-collapsible-content">


{| class="wikitable"
! Software !! How to get its version !! Output example
|-
| TF-A || [[TF-A - How to debug#TF-A Version number|TF-A Version number]] ||
NOTICE:  BL2: v2.0(debug):{{Highlight|v2.0-dirty}}
|-
| U-Boot || See the version displayed in the console ||
{{Highlight|U-Boot 2018.11-stm32mp-r2}} [...]
|-
| Linux kernel ||
 {{Board$}} cat /proc/version
||
{{Highlight|Linux version 4.19.9}} (xxxx@yyyy) (gcc version 8.2.0 (GCC)) [...]
|-
| GCC ||
 {{Board$}} cat /proc/version
||
Linux version 4.19.9 (xxxx@yyyy) ({{Highlight|gcc version 8.2.0 (GCC)}}) [...]
|-
| Yocto Project ||
 {{Board$}} lsb_release -c
||
Codename:       {{Highlight|thud}}
|-
| Weston ||
 {{Board$}} weston --version
||
{{Highlight|weston 5.0.0}}
|-
| GStreamer ||
 {{Board$}} gst-play-1.0 --version
||
{{Highlight|GStreamer 1.14.2}}
|-
| GPU ||
 {{Board$}} cat /sys/kernel/debug/gc/version
||
{{Highlight|6.2.4.p3.174315}} built [...]
|}
</div></div>


===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]]).
{{ReviewsComments|CPR: IP address to change}}* 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-5.0-noarch:core-5.0-arm
 Distributor ID: openstlinux-weston
 Description:    ST OpenSTLinux - Weston - (A Yocto Project Based Distro) 2.6-...
 Release:        2.6...
 Codename:       thud

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 release
|}

====Printing system information====
 {{Board$}} uname -a
 Linux stm32mp1 4.19.49 #1 SMP PREEMPT Sun Jun 9 07:17:25 UTC 2019 armv7l armv7l  armv7l GNU/Linux

Where:
{|
| Linux || Kernel name
|-
| stm32mp1 || Network node hostname
|-
| 4.19.49 || Kernel release
|-
| &#35;1 SMP PREEMPT Sun Jun 9 07:17:25 UTC 2019 || Kernel version
|-
| armv7l || Machine hardware name
|-
| GNU/Linux || Operating system 
|}

====Printing Linux kernel and GCC versions====
 {{Board$}} cat /proc/version
 Linux version 4.19.49 (xxxx@yyyy) (gcc version 8.2.0 (GCC)) #1 SMP PREEMPT Sun Jun 9 07:17:25 UTC 2019

Where:
{|
| Linux || Kernel name
|-
| version 4.19.49 ||Kernel release
|-
| (xxxx@yyyy) || Person (xxxx) who compiled the kernel, and machine (yyyy) where it happened
|-
| (gcc version 8.2.0 (GCC) ) || Version of the GCC compiler used to compile the kernel
|-
| &#35;1 SMP PREEMPT Sun Jun 9 07:17:25 UTC 2019 || 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  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  8.2M   46M  16% /boot
 /dev/mmcblk0p7  6.4G   68M  6.1G   2% /usr/local
 tmpfs           436M  128K  436M   1% /var/volatile
 /dev/mmcblk0p5   15M  8.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).

[[Category:Sub-articles]]
Line 54: Line 54:
 
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:
 
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:
   
{{ReviewsComments| CPR IP address to change}}
 
 
[[File: STM32MP15_example_command_remote_terminal.png|thumb|upright=4|center|link=|Example of command (''ifconfig'') executed on the remote Terminal program]]
 
[[File: STM32MP15_example_command_remote_terminal.png|thumb|upright=4|center|link=|Example of command (''ifconfig'') executed on the remote Terminal program]]
 
<br>
 
<br>
Line 176: Line 175:
 
Prerequisite: your board is connected to your local network through the Ethernet connector (see [[#step3|step 3]]).
 
Prerequisite: your board is connected to your local network through the Ethernet connector (see [[#step3|step 3]]).
   
{{ReviewsComments|CPR: IP address to change}}
 
 
* Get the IP address of your board with the [[IP Linux command line|''ip'' Linux command line]] ({{highlight|recommended method}}):
 
* 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                                                                           
 
  {{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

Attachments

Discussions