Phytec LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit User manual

A Product of PHYTEC Technology Holding Company
LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart
Guide










LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
Document Title LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
Document Type Quickstart Guide
Yocto Page L-813e_7 Yocto Reference Manual
Article Number LAN-087e.A2
Release Date 13.02.2020
Is Branch of LAN-087e.Ax phyCORE-i.MX 8 Alpha Kit QS Guide Head

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
•
•
Introduction
This Quickstart guide describes the tools and provides the know-how to install and work with the Linux Board
Support Package (BSP) for the phyCORE-i.MX 8 AlphaKit. This guide shows you how to do everything including
installing the appropriate tools and sources, building custom kernels, and deploying the OS in order to operate the
software and hardware.
This kit is currently in Alpha Status. There are several topics to keep in mind while working with this kit and guide:
The phyCORE-i.MX 8 will go through several functional changes during the Alpha Stage of development. Due
to this, this Quickstart guide may change without any prior notice.
The phyCORE-i.MX 8 has some functionality that is not currently operational. Please be aware of this when
working with the Alpha Kit.
This Quickstart guide is only for booting and starting the basic functionality of the phyCORE-i.MX 8. This
guide does not qualify as a Hardware manual for the phyCORE-i.MX 8. The following manuals will be
available in future releases of the phyCORE-i.MX 8:
For more information or details regarding the phyCORE-i.MX 8, please contact the PHYTEC Sales
department.
  * Hardware Manual - provides a detailed description of all components and functions of the phyCORE-i.MX 8
and phyCORE-i.MX 8 Carrier Board
  * Yocto Reference Manual - provides information on Yocto, which is used with most PHYTEC products * Board
Support Package (BSP) Manual - provides detailed instructions on running the tools which are used to build
various software
  * Development Environment Guide - provides instructions to prepare and start the programs Eclipse and QT
Creator, as well as setting up a Linux host system

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
1.
2.
3.
4.
5.
Requirements
The following components and system requirements are necessary to successfully complete this Quickstart.
Deviations from these requirements are possible but may require workarounds.
Hardware
Included in Kit
phyCORE-i.MX 8 SOM with i.MX 8QuadMax processor (PCM-064)
phyCORE-i.MX 8 carrier board (PCM-943)
USB-A to Micro-USB Cable
Power adapter supplying 24 V DC/ 2.5 A
Ethernet Cable
phyCORE-i.MX 8 Alpha Kit Compete Assembly
phyCORE-i.MX 8 Alpha Kit

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
•
•
•
•
•
•
•
Additional Equipment
 
Additional Equipment (not included in Alpha Kit)
An SD card and SD card reader operational underLinux.
Additional Serial null modem cable (RS-232) (optional)
Additional Kits for the phyCORE-i.MX 8
LCD-018-070-KAP.A3 - 7" Display Kit
Software
A modernLinuxoperating host system either natively or via a virtual machine.
Ubuntu 16.04 LTS 64-bit recommended. Other distributions will likely work but note that some setup
information, as well as OS-specific commands and paths, may differ.
VMWare Workstation, VMWare Player, and VirtualBox are possible solutions if you want to use a virtual
machine.
Root access to yourLinuxhost PC. Some commands in this guide will not work if you do not have sudo
access (e.g. package installation, formatting an SD card).
At least 40 GB to 50 GB of free space on the build partition of the host PC.
An active internet connection.
phyCORE-i.MX 8 Carrier Board Components
The following pictures show the components of the phyCORE-i.MX 8 Carrier Board. The location of the components
on the board have been highlighted for easy reference.
If you do not have SD card access underLinuxon your host PC then formatting, copying the bootloader,
and mounting the root file system on an SD card will not be possible.


LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
phyCORE-i.MX 8 Components (Top)

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
phyCORE-i.MX 8 Components (Bottom)
As this is an Alpha Kit, there will be continuous revisions made to the phyCORE-i.MX 8 SOM and phyCORE-
i.MX 8 Carrier Board. Due to this, components and features may not be available. Contact PHYTEC if there
any questions regarding components and features for this Alpha Kit. To see which components are
currently functional, refer to the i.MX 8release notes.


LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
1.
2.
3.
4.
Connecting the phyCORE-i.MX 8 Carrier Board
There are 3 cables that need to be manually connected to the phyCORE-i.MX 8 in order for it to be operational
Connecting the USB Debug
If S1=ON, no boot is possible without connecting the Debug USB cable. Using the USB Micro head, connect the USB
cable to the Debug USB component (X10). The other head should be connected to the development host. After
switching On the power, 4 COM-Ports should show up.
-M41 UART (not supported yet)
-M40 UART (not supported yet)
-SCU-UART (only output of the SCU)
-Debug-UART (default console)
Connecting to the Ethernet
Connect one end of the Ethernet cable to the Ethernet ETH0 component (X8). Connect the other end to a suitable
Ethernet source, as the development host will need to be able to communicate with the phyCORE-i.MX8M carrier
board.
Powering the Board
Connect the power adapter to the Power-In component (X29 or X32). The Power Adapter included in this kit is a 2-
pole barrel connector used with X29.
Please note the polarity of the Power components X29 and X32. Ensure that your power adapter is
correctly set up to use the polarity as shown below.
phyCORE-i.MX8 Polarity

Be aware that as soon as the phyCORE-i.MX 8 Carrier Board is supplied with power, the default eMMC boot
sequence will begin. Ensure that all cables are connected and the desired boot mode is chosen before
powering on the board!


LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
Bootmode Switch
The i.MX 8QuadMax has 6 Boot-Pins. They are connected to Dip Switches on the carrier board. The following table
shows the Dip Switch configurations for the available Boot-Sources. ON = 0 and OFF = 1 when Nr.8 of the Dipswitch
is ON.
BOOT_MODE [0] is Dipswitch Nr.1, BOOT_MODE [1] is Dipswitch Nr. 2, etc.
Boot Mode Boot_Mode
[5]
Boot_Mode
[4]
Boot_Mode
[3]
Boot_Mode
[2]
Boot_Mode
[1]
Boot_Mode
[0]
USB Serial
Download
ON ON ON OFF ON ON
eMMC0 Boot ON ON OFF ON ON ON
USDHC2 SD Boot ON ON OFF OFF OFF ON
FlexSPI Boot ON OFF OFF OFF OFF ON
SATA Boot OFF ON ON ON OFF ON
By default the Boot-Source is EMMC(Switch the right Dip-Switch (Nr.8 = Enable Overwrite) of the
Bootswitches to "OFF" for default setting).

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
Building the BSP
This section will guide you through the general build process of the i.MX8 BSP using the phyLinux script.
If you want to use our software without phyLinux and the Repo tool managed environment instead, you can find all
Git repositories on:
Usedu-bootrepository:
Ouru-bootversion is based on theu-boot-imxand adds only a few patches which will be sent upstream in future.
Used Linux kernel repository:
Our i.MX8 kernel is based on the linux-imx kernel.
To find out which tag is used for a specific board, have a look at your checked out BSP source folder under:
Get the BSP
Create a fresh project directory:
Download and run the phyLinux script on the manifest file:
Basic Set-up
There are a few important steps which have to be done before the main build process.
git://git.phytec.de
git://git.phytec.de/u-boot-imx
git://git.phytec.de/linux-imx-dev
meta-phytec/dynamic-layers/fsl-bsp-release/recipes-bsp/u-boot/u-boot-
imx_*.bbappend
meta-phytec/recipes-kernel/linux/linux-imx_*.bb
host$ mkdir ~/yocto
host$ cd ~/yocto
host$ wget ftp://ftp.phytec.de/pub/Software/Linux/Yocto/Tools/phyLinux
host$ ./phyLinux init

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
•
•
•
•
•
•
•
•
•
To set up the host, seeYocto Reference Manual, "Setting up the Host"and NXP's documentationi.MX Yocto
Project User's Guide "Host Setup".
To set up theGitconfiguration, seeYocto Reference Manual "Git Configuration"
Finding the Right Software Platform
The i.MX 8 BSP is planned as a unified BSP, which means in the future it will support a set of different PHYTEC carrier
boards (CB) with different Systems on Module (SOMs). However, thisALPHA BSPsupports only one PHYTEC
machine:
Selecting the Software Platform
To set the correct SoC, BSP version and platform, call:
Starting the Build Process
Now you should be in a sub-folder namedbuildand you can start the first build process:
BSP Images
All images generated byBitbakeare deployed to~/yocto/build/tmp/deploy/images/<machine>.
The following list shows for example all files generated for the i.MX 8 phycore-imx8-1machine:
U-Boot:u-boot.bin
imx-boot:imx-boot-phycore-imx8-2-sd.bin
scfw:mx8qm-phycore-imx8-2-scfw-tcm.bin
Kernel:Image
Kernel device tree file:Image-phytec-imx8qm-phycore-rdk.dtb
Kernel configuration:Image.config
Root filesystem:fsl-image-qt5-validation-imx-phycore-imx8-2.tar.gz, fsl-image-qt5-validation-imx-phycore-
imx8-2.manifest
SD card image:fsl-image-qt5-validation-imx-phycore-imx8-2.sdcard
phycore-imx8-2
host$ ./phyLinux init
host$ bitbake fsl-image-qt5-validation-imx

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
•
•
•
Booting the System
The default boot source for the i.MX 8 module phycore-imx8 is the eMMC.
Booting the eMMC
To boot from eMMC, switch S8 has to be set to OFF (which is the default setup).
To update the eMMC software, see Updating the Software.
Booting the SD Card
Booting from an SD card is useful in several situations, e.g. if the board does not start anymore due to a damaged
bootloader. To boot from an SD card, switch S1, S5, S6 and S8 has to be set to ON.
There are two ways to create a bootable SD card. You can either use:
- a single prebuild SD card image, or
- the four individual images (imx-boot-, kernel- and device tree image, and root filesystem)
Using a Single, Prebuilt SD Card Image
The first possibility is to use the SD card image built byBitbake, a tool integrated inYocto. This image is zipped and
has the ending*.sdcard and can be found underbuild/tmp/deploy/images/phycore-imx8-2/fsl-image-qt5-validation-
imx-phycore-imx8-2.sdcard. It contains all BSP files in correctly preformatted partitions and can be copied to the SD
card easily using the singleLinuxcommanddd.
To create your bootable SD card, you must first find out the correct device name of your SD card and possible
partitions. Then unmount the partitions before you start copying the image to the SD card.
In order to get the correct device name, first remove your SD card and executels /dev.
Now insert your SD card and executels /devagain.
Compare the two outputs to find the new device name(s) listed in the second output. These are the device
names of the SD card (device and partitions if the SD card is formatted).
In order to verify the device names found, execute the commanddmesg. Within the last lines of its output,
you should also find the device names, for examplesde(depending on your system).
Now that you have the device name/dev/<your_device>(e.g./dev/sde), you can see the partitions which must be
unmounted if the SD card is formatted. In this case, you will also find/dev/<your_device>with an appended number
(e.g./dev/sde1) in the output. These represent the partition(s) that need to be unmounted.
Unmount all partitions with:
To create your bootable SD card with theddcommand, you must have root privileges. Because of this, you
must be very careful when selecting the destination device for theddcommand! All files on the selected
destination device will be erased immediately without any further query! Consequently, having selected
the wrong device can also erase your hard drive!

host$ umount /dev/<your_device><number>

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
•
•
•
•
After having unmounted all devices with an appended number (<your_device><number>), you can create
your bootable SD card with:
Using the device name (<your_device>) without appended number (e.g.sde) which stands for the whole device.The
parameterconv=fsyncforces a sync operation on the device beforeddreturns. This ensures that all blocks are
written to the SD card and are not still in memory.The parameterstatus=progresswill print out information on how
much data is and still has to be copied until it is finished.
Using four individual Images (imx-boot, kernel- and device tree image, and root
filesystem)
Option two uses imx-boot and a image (a kernel and device tree image together with the root filesystem) to create a
bootable SD card manually.
For this method, a new card must be set up with 2 partitions and 8 MB of free space at the beginning of the card. Use
the following procedure withfdiskunderLinux:
Create a new FAT partition with partition id C. When creating the new partition, you must leave 8 MB of free
space at the beginning of the card. When you go through the process of creating a new partition,fdisklets
you specify where the first sector starts. During this process,fdiskwill tell you where the first sector on the
disk begins. For example, if the first sector begins at 1000 and each sector is 512 bytes, then 8 MB / 512 bytes
= 16384 sectors. This means your first sector should begin at 17384 to leave 8 MB of free space. The size of
the FAT partition needs only be big enough to hold the Image, which is only a few megabytes. To be safe, we
recommend a size of 64 MB.
Create a newLinuxpartition with partition id 83. Make sure you start this partition after the last sector of
partition 1! By default,fdiskwill try to use the first partition available on the disk, which in this example is
1000. However, this is our reserved space! You must use the remaining portion of the card for this partition.
Write the new partition to the SD card and exitfdisk.
Example:
Type:
You will receive:
host$ sudo dd if=<IMAGENAME>-<MACHINE>.sdcard of=/dev/<your_device> bs=1MB
conv=fsync status=progress
host$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 4025 MB, 4025483264 bytes
4 heads, 32 sectors/track, 61424 cylinders, total 7862272 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x26edf128

Device Boot Start End Blocks Id System

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
•
•
•
•
•
Remove and reinsert the card. Otherwise,Linuxwill not recognize the new partitions created in the previous
step.
Create a file system on the partitions with (replacesdewith your device):
Now, the images need to be copied to the SD card.
Write the bootloader in front of the first partition (replacesdewith your device):
Mount the first partition (vfat) and copy thelinuximageandoftreefile to it:
In case you want to boot the wholeLinuxfrom the SD card, also mount theext4partition.
Then untar<IMAGENAME>-<MACHINE>.tar.gzrootfs image to it:
Do not forget to properly unmount the SD card with:
Booting the Kernel from Network
Booting from network means loading the kernel over TFTP and the root filesystem over NFS. The bootloader itself
must already be loaded from another boot device that is available.
/dev/sdc1 8192 24575 8192 c W95 FAT32 (LBA)
/dev/sdc2 24576 655359 315392 83 Linux
host$ sudo mkfs.vfat /dev/sde1
host$ sudo mkfs.ext4 -L "rootfs" /dev/sde2
host$ dd if=imx-boot-phycore-imx8-2-sd.bin of=/dev/sde bs=1k seek=32 conv=fs
ync
host$ sudo mount /dev/sd<X>1 /mnt
Make sure that the images are namedexactlyas previously mentioned as the bootloader expects them to
be named as such.

host$ sudo mount /dev/sd<X>2 /media
host$ sudo tar jxf <IMAGENAME>-<MACHINE>.tar.gz -C /media/
host$ sudo umount /media

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
1.
•
•
•
•
•
•
Development Host Preparations
On the development host, a TFTP server must be installed and configured. The following tool will be needed to boot
the Kernel from Ethernet:
a TFTP server
ForUbuntuinstall:
After the installation of the packages, you have to configure the TFTP server.
Setup for the TFTP Server
Edit/etc/default/tftpd-hpa.
Create a directory to store the TFTP files:
Configure a static IP address for the appropriate interface:
You will receive:
Restart the services to pick-up the configuration changes:
Now connect the ethernet port of the board to your host system, configure the board to network boot, and
start it.
host$ sudo apt-get install tftpd-hpa
TFTP_USERNAME="tftp"
TFTP_DIRECTORY="/tftpboot"
TFTP_ADDRESS=":69"
TFTP_OPTIONS="--secure"
host$ sudo mkdir /tftpboot
host$ sudo chmod -R 777 /tftpboot
host$ sudo chown -R nobody /tftpboot
host$ ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:11:6b:98:e3:47
inet addr:192.168.3.10 Bcast:192.168.3.255 Mask:255.255.255.0
host$ sudo service tftpd-hpa restart

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
•
•
Usually, TFTP servers are using the/tftpbootdirectory to fetch files from. If you built your own images, please copy
them from the BSP’s build directory to there.
We also need a network connection between the embedded board and the TFTP server. The server should be set to
IP 192.168.3.10 and netmask 255.255.255.0.
After the installation of the TFTP server, an NFS server needs to be installed. The NFS server is not restricted to a
certain file system location, so all we have to do on most distributions is to modify the file/etc/exportsand export
our root filesystem to the embedded network. In this example file, the whole work directory is exported and the
”lab network” address of the development host is 192.168.3.10. The IP addresses have to be adapted to the local
needs:
<user> must be replaced with your home directory name.
<rootfspath> can be set to a folder which contains arootfstar.gzimage extracted withsudo.
Preparations on the Enbedded Board
To find out the Ethernet settings in the bootloader of the target, type:
With your development host set to IP 192.168.3.10 and netmask 255.255.255.0, the target should return:
If you need to change something, type:
Ifethaddrorethprimeis not set, you should add it by typing something similar to:
<parameter> should be one ofipaddr,netmask,gatewayorserverip.
<value> will be the actual value of the chosen parameter.
/home/<user>/<rootfspath> 192.168.3.10/255.255.255.0(rw,no_root_squash,sync,
no_subtree_check)
u-boot=> printenv
ipaddr=192.168.3.11
netmask=255.255.255.0
gateway=192.168.3.10
serverip=192.168.3.10
ethaddr=68:05:ca:1b:b5:cc
ethprime=FEC
u-boot=> editenv <parameter>
edit: <value>
u-boot=> setenv <parameter> <value>

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
Make your changes and hit 'Enter'.
The changes you made are temporary for now, so to save these we have to save them by typing:
You can also change the IP address to DHCP instead of using a static one. Just configurenetargs:
Please note that these modifications will only affect the bootloader settings. For modifying the IP setting inLinux,
refer to SectionNetwork
Booting the Embedded Board
To boot from network, call:
u-boot=> saveenv
netargs=setenv bootargs console=${console} root=/dev/nfs ip=dhcp nfsroot=$
{serverip}:${nfsroot},v3,tcp
u-boot=> run netboot

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
Updating the Software
In this chapter, we explain how to use theu-bootbootloader on target orlinuxon target/host to update the images
in eMMC.
Updating eMMC via Network
i.MX 8 boards have an Ethernet connector and can be updated over a network. Be sure to set up the development
host correctly. The IP needs to be set to 192.168.3.10, the netmask to 255.255.255.0, and a TFTP server needs to be
available.
From a high-level point of view, an eMMC device is like an SD card. Therefore, it is possible to flash the
image<name>.sdcardfrom theYoctobuild system directly to the eMMC. The image contains the imx-boot, kernel,
device trees, and root filesystem.
Updating eMMC via network inu-booton target
This steps will show how to update the eMMC via a network, but they only work if the size of the image file is less
then 1GB. If the image file is larger, go to the chapterUpdating eMMC via network in Linux on target. Configure the
boot switch to boot from SD Card (Switch S1 is ON) and put in an SD card. Power on the board and stop inu-boot.
Load your image via network to RAM:
Write the image to the eMMC:
A working network is necessary!

u-boot=> tftp ${loadaddr} ${serverip}:small_test-image.sdcard
Using ethernet@30be0000 device
TFTP from server 192.168.3.1; our IP address is 192.168.3.3
Filename 'small_test-image.sdcard'.
Load address: 0x40480000
Loading: #################################################################
#################################################################
#################################################################
...
...
...
#################################################################
#################################################################
######################
20.3 MiB/s
done
Bytes transferred = 524288000 (1f400000 hex)
u-boot=> mmc dev 0
switch to partitions #0, OK
mmc0(part 0)is current device
u-boot=> mmc write ${loadaddr} 0x0 0xFA000

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
•
Updating eMMC via network in Linux on Target
You can update the eMMC from your target.
Take an uncompressed or compressed image on host and send it withsshthrough the network to the eMMC
of the target with an one-line command:
Updating eMMC via network in Linux on host
It is also possible to update the eMMC from your Linux host. As before, you need a complete image on your host.
Show your available image-files on host:
Uncompress and send image with dd command combined withsshthrough network to the eMMC of your
device:
Updating eMMC from SD card
Even if there is no network available, you can update the eMMC. For that, you only need a ready-to-use image file
(*.sdcard) located on SD card. Because the image file is quite large, you have to enlarge your SD card to use its full
space (if it was not enlarged before). To enlarge your SD card, see Resize the ext4 Filesystem.
number of blocks to write. In this case 524288000 bytes / 512 = 0xFA000

MMC write: dev # 0, block # 0, count 1024000 ... 1024000 blocks written: OK
A working network is necessary!

target$ ssh <USER>@192.168.3.1 "dd if=<path_to_file>/fsl-image-qt5-
validation-imx-phycore-imx8-2.sdcard" | dd of=/dev/mmcblk0 status=progress
A working network is necessary!

host$ ls
fsl-image-qt5-validation-imx-phycore-imx8-2.sdcard
host$ dd if=fsl-image-qt5-validation-imx-phycore-imx8-2.sdcard status=progres
s | ssh [email protected] "dd of=/dev/mmcblk0"

LAN-087e.A2 phyCORE-i.MX 8 Alpha Kit Quickstart Guide
•
•
Updating eMMC from SD card inu-booton target
Configure SD Card for Flashing
First, we create a new partition on the SD card to store the image in it.
On your host insert the SD card and see indmesg, which one it is:
Create a new partition withsudo fdisk /dev/sd<x>:
host$ dmesg | tail
...
[30436.175412]sd 4:0:0:0: [sdb]62453760 512-byte logical blocks: (32.0 GB/
29.8 GiB)
[30436.179846]sdb: sdb1 sdb2
...
host$ sudo fdisk /dev/sdb
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p
Disk /dev/sdb: 29,8 GiB, 31976325120 bytes, 62453760 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd28c31b9

Device Boot Start End Sectors Size Id Type
/dev/sdb1 16384 81919 65536 32M c W95 FAT32 (LBA)
/dev/sdb2 81920 3375103 3293184 1,6G 83 Linux

Command (m for help): n
Partition type
p primary (2 primary, 0 extended, 2 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (3,4, default 3): 3
First sector (2048-62453759, default 2048): 3440640
Last sector, +sectors or +size{K,M,G,T,P}(3440640-62453759, default 62453759):
Created a new partition 3 of type 'Linux' and of size 28,1 GiB.
Command (m for help): t
Partition number (1-3, default 3): 3