Phytec L-1017e.A3 i.MX 8M Plus User manual

A Product of PHYTEC Technology Holding Company
L-1017e.A3 i.MX 8M Plus BSP Manual










L-1017e.A3 i.MX 8M Plus BSP Manual
L-1017e.A3 i.MX 8M Plus BSP Manual
Document Title L-1017e.A3 i.MX 8M Plus BSP Manual
Document Type BSP Manual
Article Number L-1017e.A3
Yocto Manual L-813e.A12 Yocto Reference Manual (hardknott)
Release Date 09.12.2022
Is Branch of L-1017e.Ax i.MX 8M Plus BSP Manual Head
This BSP manual guides you through the installation and creation steps for the Board Support Package (BSP) and
describes how to handle the interfaces for thephyCORE-i.MX8M Plus Kit. Furthermore, this document describes
how to create BSP images from the source code. This is useful for those who need to change the default image and
need a way to implement these changes in a simple and reproducible way.
The table below shows the Compatible BSPs for this manual:
Compatible BSP'S BSP Release Type BSP Release Date BSP Status
BSP-Yocto-NXP-i.MX8MP-
PD22.1.0
Major 09.12.2022 Released
Note
This document contains code examples that describe the communication with the board over the serial
shell.The code examples lines begin with "host$", "target$" or "u-boot=>". This describes where the
commands are to be executed. Only after these keywords must the actual command be copied.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
•
•
•
PHYTEC Documentation
PHYTEC provides a variety of hardware and software documentation for all of our products. This includes any or all
of the following:
QS Guide: A short guide on how to set up and boot a phyCORE board along with brief information on
building a BSP, the device tree, and accessing peripherals.
Hardware Manual: A detailed description of the System on Module and accompanying carrier board.
Yocto Guide: A comprehensive guide for the Yocto version the phyCORE uses. This guide contains an
overview of Yocto; introducing, installing, and customizing the PHYTEC BSP; how to work with programs like
Poky and Bitbake; and much more.
BSP Manual: A manual specific to the BSP version of the phyCORE. Information such as how to build the
BSP, booting, updating software, device tree, and accessing peripherals can be found here.
Development Environment Guide: This guide shows how to work with the Virtual Machine (VM) Host
PHYTEC has developed and prepared to run various Development Environments. There are detailed step-by-
step instructions for Eclipse and Qt Creator, which are included in the VM. There are instructions for running
demo projects for these programs on a phyCORE product as well. Information on how to build a Linux host
PC yourself is also a part of this guide.
Pin Muxing Table: phyCORE SOMs have an accompanying pin table (in Excel format). This table will show
the complete default signal path, from processor to carrier board. The default device tree muxing option will
also be included. This gives a developer all the information needed in one location to make muxing changes
and design options when developing a specialized carrier board or adapting a PHYTEC phyCORE SOM to an
application.
On top of these standard manuals and guides, PHYTEC will also provide Product Change Notifications, Application
Notes, and Technical Notes. These will be done on a case-by-case basis. Most of the documentation can be found in
the download page of our product: https://www.phytec.de/produkte/system-on-modules/phycore-imx-8m-plus/
#downloads/

L-1017e.A3 i.MX 8M Plus BSP Manual
Supported Hardware
The phyBOARD-Pollux with 2GB RAM is supported.
On our web page, you can see all supported Machines with the available Article Numbers forthis release:BSP-
Yocto-NXP-i.MX8MP-PD22.1.0 download.
If you choose a specificMachine Namein the sectionSupported Machines, you can see whichArticle
Numbersare available under this machine and also a short description of the hardware information.In case you
only have theArticle Numberof your hardware, you can leave theMachine Namedrop-down menu empty and
only choose yourArticle Number. Now it should show you the necessaryMachine Namefor your specific
hardware.
phyBOARD-Pollux Components
1 phyBOARD-Pollux Components (top)
2 phyBOARD-Pollux Components (bottom)

L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
•
•
•
•
Getting Started
The phyBOARD-Pollux Kits are shipped with a pre-flashed SD-Card. It contains the phytec-qt5demo-image and can
be used directly as a boot source. The eMMC is programmed with only a U-boot as default. You can get all the
sources from our download server.This chapter explains how to flash a BSP image to SD Card and how to start the
board.
Get the Image
The *.sdcard image contains all BSP files in several, correctly pre-formatted partitions and can be copied to the SD
card easily using the single Linux command dd. It can be built byYyoctoor downloaded from our download server.
Get the*.sdcardfile from our download server:
host$ wget https://download.phytec.de/Software/Linux/BSP-Yocto-i.MX8MP/BSP-Yocto-NXP-
i.MX8MP-PD22.1.0/images/ampliphy-vendor-xwayland/phyboard-pollux-imx8mp-3/phytec-
qt5demo-image-phyboard-pollux-imx8mp-3.sdcard
Write the Image to the SD Card
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:
host$ umount /dev/<your_device><number>
After having unmounted all devices with an appended number (<your_device><number>), you can create
your bootable SD card:
Warning
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!


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
•
host$ sudo dd if=<IMAGENAME>-<MACHINE>.sdcard of=/dev/<your_device> bs=1M conv=fsync
status=progress
Using the device name (<your_device>) without appended number (e.g.sde) which stands for the whole device.The
parameterconv=fsyncforces a sync operation on the device beforeddreturns. 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.
<BUILD-TIME>has the format:YYYYMMDDHHMMSS
example:
Date = 14.01.2022
Time = 10:42:11
<BUILD-TIME> = 20220114104211
First Start-up
To boot from an SD card, the bootmode switch (S3) needs to be set to the following position:
3 SD Card Bootmode
Insert the SD card
Connect the target and the host with micro USB on X1 debug USB
Power up the board
Note
The created file phytec-qt5demo-image-phyboard-pollux-imx8mp-3.sdcard is only a link to a file like phytec-
qt5demo-image-phyboard-pollux-imx8mp-3-<BUILD-TIME>.rootfs.sdcard.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
Building the BSP
This section will guide you through the general build process of the i.MX 8M PlusBSP using Yocto and the phyLinux
script. For more information about our meta-layer or Yocto in general visit: L-813e.A12 Yocto Reference Manual
(hardknott).
Basic Set-Up
If you have never created a Phytec BSP with Yocto on your computer, you should take a closer look at the chapter
BSP Workspace Installation in the L-813e.A12 Yocto Reference Manual (hardknott).
Get the BSP
There are two ways to get the BSP sources. You can download the complete BSP sources from our download page:
BSP-Yocto-i.MX8MP; or you can build it yourself with Yocto. This is particularly useful if you want to make
customizations.
The phyLinux script is a basic management tool for PHYTEC Yocto BSP releases written in Python. It is mainly a
helper to get started with the BSP structure.
Create a fresh project folder, get phyLinux, and make the script executable:
host$ mkdir ~/yocto
host$ cd yocto/
host$ wget https://download.phytec.de/Software/Linux/Yocto/Tools/phyLinux
host$ chmod +x phyLinux
Run phyLinux
host$ ./phyLinux init
During the execution of theinitcommand, you need to choose your processor platform (SoC), PHYTEC's BSP
release number, and the hardware you are working on.
Warning
A clean folder is important because phyLinux will clean its working directory.Calling phyLinux from a
directory that isn't empty will result in awarning.

Note
On the first initialization, the phyLinux script will ask you to install theRepotool in your/usr/local/
bindirectory.

Note


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
•
•
It is also possible to pass this information directly using command line parameters:
host$ DISTRO=ampliphy-vendor-xwayland MACHINE=phyboard-pollux-imx8mp-3./phyLinux
init -p imx8mp -r PD-BSP-Yocto-NXP-i.MX8MP-PD22.1.0
After the execution of theinitcommand, phyLinux will print a few important notes as well as information for the
next steps in the build process.
Starting the Build Process
Set up the shell environment variables:
host$ source sources/poky/oe-init-build-env
The current working directory of the shell should change tobuild/.
Open the main configuration file and accept the GPU and VPU binary license agreements. You have to
uncomment the corresponding line.
host$ vim conf/local.conf
# Uncomment to accept NXP EULA
# EULA can be found under ../sources/meta-freescale/EULA
ACCEPT_FSL_EULA = "1"
Build your image:
host$ bitbake phytec-headless-image
BSP Images
All images generated byBitbakeare deployed to~/yocto_imx8mp/build/deploy/images/<machine>. The following
list shows for example all files generated for the i.MX 8M Plus phyboard-pollux-imx8mp-*machine:
If you cannot identify your board with the information given in the selector, have a look at the invoice for
the product. And have look at https://www.phytec.de/bsp-download/?bsp=BSP-Yocto-NXP-i.MX8MP-
PD22.1.0
Note
This needs to be done every time you open a new shell for starting builds.

Note
We suggest starting with our smaller non-graphical imagephytec-headless-imageto see if everything is
working correctly. The first compile process takes about 40 minutes on a modern Intel Core i7. All
subsequent builds will use the filled caches and should take about 3 minutes.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
•
•
•
•
•
•
•
•
•
u-boot.bin: Binary compiled U-boot bootloader (U-Boot). Not the final Bootloader image!
oftree: Default kernel device tree
u-boot-spl.bin: Secondary program loader (SPL)
imx-boot-tools/bl31-imx8mp.bin: ARM Trusted Firmware binary
lpddr4_pmu_train_2d_dmem_202006.bin, lpddr4_pmu_train_2d_imem_202006.bin:DDR PHY firmware
images
imx-boot: Bootloader build by imx-mkimage which includes SPL, U-Boot, ARM Trusted Firmware and DDR
firmware. This is the final bootloader image which is bootable.
Image: Linux kernel image
Image.config: Kernel configuration
imx8mp-phyboard-pollux-rdk*.dtb: Kernel device tree file
imx8mp-phy*.dtbo: Kernel device tree overlay files
phytec-qt5demo-image*.tar.gz: Root file system
phytec-qt5demo-image*.sdcard: SD card image

L-1017e.A3 i.MX 8M Plus BSP Manual
Installing the OS
Bootmode Switch (S3)
The phyBOARD‑Pollux features a boot switch with four individually switchable ports to select the phyCORE-i.MX 8M
Plus default bootsource.
1 Boot Configuration Options (S3)
eMMC Internal Fuses
SPI NOR USB Serial Download
Tip
Hardware revision baseboard: 1552.2


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
SD Card Test Mode
Flash eMMC
To boot from eMMC, make sure that the BSP image is flashed correctly to the eMMC and the bootmode switch (S3) is
set to Default SOM boot.
Flash eMMC from Network
i.MX 8M Plus 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 SD card image (<name>.sdcard) from theYocto build system directly to the eMMC. The SD card
image contains the bootloader, kernel, device tree, device tree overlays, and root file system.
Flash eMMC from Network in u-boot on Target
These steps will show how to update the eMMC via a network. However, they only work if the size of the image file is
less than 1GB. If the image file is larger, go to the section Format SD Card. Configure the bootmode switch (S3)to
boot from SD Card and put in an SD card. Power on the board and stop in U-Boot prompt.
Load your image via network to RAM:
u-boot=> tftp ${loadaddr} phytec-qt5demo-image-phyboard-pollux-imx8mp-3.sdcard
Using ethernet@30be0000 device
TFTP from server 192.168.3.10; our IP address is 192.168.3.11
Filename 'phytec-qt5demo-image-phyboard-pollux-imx8mp-3.sdcard'.
Load address: 0x40480000
Loading: #################################################################
#################################################################
#################################################################
...
...
...
#################################################################
#############
11.2 MiB/s
done
Bytes transferred = 911842304 (36599c00 hex)
Write the image to the eMMC:
u-boot=> mmc dev 2
Tip
A working network is necessary! Setup Network Host.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
switch to partitions #0, OK
mmc2(part 0) is current device
u-boot=> setexpr nblk ${filesize} / 0x200
u-boot=> mmc write ${loadaddr} 0x0 ${nblk}

MMC write: dev # 2, block # 0, count 1780942 ... 1780942 blocks written: OK
Flash eMMC via Network in Linux on Target
You can update the eMMC from your target.
Take a compressed or uncompressed image on the host and send it withsshthrough the network (then
uncompress it, if necessary) to the eMMC of the target with a one-line command:
target$ ssh <USER>@192.168.3.10 "dd if=<path_to_file>/phytec-qt5demo-image-phyboard-
pollux-imx8mp-3.sdcard" | dd of=/dev/mmcblk2
Flash eMMC via Network in Linux on Host
It is also possible to install the OS at eMMC from your Linux host. As before, you need a complete image on your
host.
Show your available image files on the host:
host$ ls
phytec-headless-image-phyboard-pollux-imx8mp-3.sdcard
Send the image with the command dd command combined with sshthrough the network to the eMMC of
your device:
host$ dd if=phytec-headless-image-phyboard-pollux-imx8mp-3.sdcard status=progress |
ssh root@192.168.3.11 "dd of=/dev/mmcblk2"
Tip
A working network is necessary! Setup Network Host.

Tip
A working network is necessary! Setup Network Host.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
Flash eMMC from USB
Flash eMMC from USB in u-boot on Target
These steps will show how to update the eMMC via a USB device.Configure the bootmode switch to boot from SD
Card and put in an SD card. Power on the board and stop inu-boot prompt. Insert a USB device with the copied
*.sdcard image to the USB slot.
Load your image from the USB device to RAM:
u-boot=> usb start
starting USB...
USB0: USB EHCI 1.00
scanning bus 0for devices... 2USB Device(s) found
scanning usb for storage devices... 1Storage Device(s) found
u-boot=> fatload usb 0:1${loadaddr} *.sdcard
497444864 bytes read in 31577 ms (15 MiB/s)
Write the image to the eMMC:
u-boot=> mmc dev 2
switch to partitions #0, OK
mmc2(part 0) is current device
u-boot=> setexpr nblk ${filesize} / 0x200
u-boot=> mmc write ${loadaddr} 0x0 ${nblk}

MMC write: dev # 2, block # 0, count 1024000 ... 1024000 blocks written: OK
u-boot=> boot
Flash eMMC from USB in Linux
These steps will show how to flash the eMMC on Linux with a USB stick. You only need a complete image saved on
the USB stick and a bootable sdcard. (e.g. phytec-qt5demo-image-phyboard-pollux-imx8mp-3.sdcard). Set
thebootmode switchto boot from SD Card.
Insert and mount the USB stick:
[ 60.458908] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[ 60.467286] scsi host0: usb-storage 1-1.1:1.0
[ 61.504607] scsi 0:0:0:0: Direct-Access 8.07 PQ: 0
ANSI: 2
[ 61.515283] sd 0:0:0:0: [sda] 3782656 512-byte logical blocks: (1.94 GB/1.80 GiB)
[ 61.523285] sd 0:0:0:0: [sda] Write Protect is off
Tip
This step only works if the site of the image file fits into the free RAM space of the Bootloader.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
•
•
[ 61.528509] sd 0:0:0:0: [sda] No Caching mode page found
[ 61.533889] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 61.665969] sda: sda1
[ 61.672284] sd 0:0:0:0: [sda] Attached SCSI removable disk
target$ mount /dev/sda1 /mnt
Now show your saved image files on the USB Stick:
target$ cd /mnt
target$ ls
phytec-qt5demo-image-phyboard-pollux-imx8mp-3.sdcard
Show list of available MMC devices:
target$ ls /dev | grep mmc
mmcblk1
mmcblk1p1
mmcblk1p2
mmcblk2
mmcblk2boot0
mmcblk2boot1
mmcblk2p1
mmcblk2p2
mmcblk2rpmb
The eMMC device can be recognized by the fact that it contains two boot partitions: (mmcblk2boot0;
mmcblk2boot1)
Write the image to the phyCORE-i.MX 8M Plus eMMC (MMC device 2 without partition):
target$ dd if=phytec-qt5demo-image-phyboard-pollux-imx8mp-3.sdcard of=/dev/mmcblk2
After a complete write, your board can boot from eMMC.
Flash 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 the 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 Resizing ext4 Root Filesystem.
Warning
Before this will work, you need to configure the multi-port switch toDefault SOM Boot toboot from
eMMC.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
•
•
•
•
•
•
Flash eMMC from SD card in u-boot on Target
Flash an SD card with a working image and create a third FAT partition. Copy the *.sdcard image (for
example phytec-qt5demo-image.sdcard) to this partition.
Configure the bootmode switch to boot from the SD Cardand insert the SD card.
Power on the board and stop inu-boot.
Flash your<YOUR_IMAGE>.sdcard image (for example phytec-qt5demo-image.sdcard) from the SD card to
eMMC. This will partition the card and copy imx-boot,Image,dtb, dtbo, and root file system to eMMC.
Load the image:
u-boot=> fatload mmc 1:3${loadaddr} phytec-qt5demo-image-phyboard-pollux-imx8mp-3.sd
card
reading
911842304 bytes read in 39253 ms (22.2 MiB/s)
Switch the mmc dev:
u-boot=> mmc list
FSL_SDHC: 1(SD)
FSL_SDHC: 2(eMMC)
u-boot=> mmc dev 2
switch to partitions #0, OK
mmc0(part 0) is current device
u-boot=> setexpr nblk ${filesize} / 0x200
u-boot=> mmc write ${loadaddr} 0x0 ${nblk}
MMC write: dev # 2, block # 0, count 1780942 ... 1780942 blocks written: OK
Power off the board and change the multi-port switch toDefault SOM Boot to boot from eMMC.
Flash eMMC from SD card in Linux on Target
You can also flash the eMMC on Linux. You only need a complete image saved on the SD card (e.g. phytec-qt5demo-
image-phyboard-pollux-imx8mp-3.sdcard).
Show your saved image files on the SD card:
target$ ls
phytec-qt5demo-image-phyboard-pollux-imx8mp-3.sdcard
Show list of available MMC devices:
Tip
This step only works if the size of the image file fits into the free RAM space of the Bootloader. If the image
file is too large use Updating eMMC from SD card in Linux on Target.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
•
target$ ls /dev | grep mmc
mmcblk1
mmcblk1p1
mmcblk1p2
mmcblk2
mmcblk2boot0
mmcblk2boot1
mmcblk2p1
mmcblk2p2
mmcblk2rpmb
The eMMC device can be recognized by the fact that it contains two boot partitions: (mmcblk2boot0;
mmcblk2boot1)
Write the image to the phyCORE-i.MX 8M Plus eMMC (MMC device 2 without partition):
target$ dd if=phytec-qt5demo-image-phyboard-pollux-imx8mp-3.sdcard of=/dev/mmcblk2
After a complete write, your board can boot from eMMC.
FlashSPI NOR Flash
The phyCORE-i.MX8MP modules are optionally equipped with SPI NOR Flash. To boot from SPI Flash, setbootmode
switch S3 to QSPI boot to boot from QSPI. The SPI Flash is usually quite small. The phyBOARD-Pollux-i.MX8MP kit
only has 32MB SPI NOR flash populated. Only the bootloader and the environment can be stored. The kernel, device
tree, and file system are taken from eMMC by default.
The SPI NOR flash partition table is defined in the U-Boot environment. It can be printed with:
u-boot=> printenv mtdparts
mtdparts=30bb0000.spi:3840k(u-boot),128k(env),128k(env:redund),-(none)
Flash SPI NOR Flash from Network
The SPI NOR can contain the bootloader and environment to boot from. The arm64 kernel can not decompress
itself, the image size extends the SPI NOR flash populated on the phyCORE-i.MX 8M Plus.
Warning
Before this will work, you need to configure the bootmode switch S3 to Default SOM Boot toboot from
eMMC.

Tip
A working network is necessary! Setup Network Host.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
•
Flash SPI NOR from Network in u-boot on Target
Similar to updating the eMMC 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. Before reading and
writing is possible, the SPI-NOR flash needs to be probed:
u-boot=> sf probe
SF: Detected mt25qu512a with page size 256 Bytes, erase size 64 KiB, total 64 MiB
A specially formatted u-boot image for the SPI NOR flash is used. Ensure you use the correct image file. Load
the image over tftp, erase and write the bootloader to the flash:
u-boot=> tftp ${loadaddr} imx-boot-phyboard-pollux-imx8mp-3-fspi.bin-
flash_evk_flexspi
u-boot=> sf erase 00x400000
SF: 4194304 bytes @ 0x0 Erased: OK u-boot=> sf write ${loadaddr} 00x400000
u-boot=> sf write ${loadaddr} 0x400000
SF: 4194304 bytes @ 0x0 Written: OK
Erase the environment partition as well. This way, the environment can be written after booting from SPI
NOR flash:
u-boot=> sf erase 0x400000 0x100000
Flash SPI NOR from Network in kernel on Target
Copy the image from host to target:
host$ scp imx-boot-phyboard-pollux-imx8mp-3-fspi.bin-flash_evk_flexspi root@192.168.3
.11:/root
Find the number of erase blocks of the U-boot partition:
target$ mtdinfo /dev/mtd0
mtd0
Name: u-boot
Type: nor
Eraseblock size: 65536 bytes, 64.0 KiB
Amount of eraseblocks: 60 (3932160 bytes, 3.7 MiB)
Warning
Erasing the complete SPI NOR flash when it is fully written will take quite some time. This can trigger the
watchdog to reset. Due to this, erase the full flash in Linux.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
•
•
Minimum input/output unit size: 1byte
Sub-page size: 1byte
Character device major/minor: 90:0
Bad blocks are allowed: false
Device is writable: true
Erase the u-boot partition and flash it:
target$ flash_erase /dev/mtd0 0x0 60
target$ flashcp imx-boot-phyboard-pollux-imx8mp-3-fspi.bin-flash_evk_flexspi /dev/
mtd0
Flash SPI NOR Flash from SD Card
The bootloader on SPI NOR flash can be also flashed with SD Card.
Flash SPI NOR from SD Card in u-boot on Target
Copy the SPI NOR flash U-boot image imx-boot-phyboard-pollux-imx8mp-3-fspi.bin-flash_evk_flexspi to the
FAT partition on the SD Card. Before reading and writing are possible, the SPI-NOR flash needs to be probed:
u-boot=> sf probe
SF: Detected n25q256ax1 with page size 256 Bytes, erase size 64 KiB, total 32 MiB
A specially formatted U-boot image for the SPI NOR flash is used. Ensure you use the correct image file. Load
the image from the SD Card, erase and write the bootloader to the flash:
u-boot=> mmc dev 1
u-boot=> fatload mmc 1:1${loadaddr} imx-boot-phyboard-pollux-imx8mp-3-fspi.bin-
flash_evk_flexspi
u-boot=> sf erase 00x400000
u-boot=> sf write ${loadaddr} 00x400000
Erase the environment partition as well. This way, the environment can be written after booting from SPI
NOR flash:
u-boot=> sf erase 0x400000 0x100000
Warning
Erasing the complete SPI NOR flash when it is fully written will take quite some time. This can trigger the
watchdog to reset. Due to this, erase the full flash in Linux.


L-1017e.A3 i.MX 8M Plus BSP Manual
•
•
Flash SPI NOR from SD Card in kernel on Target
Mount the SD Card:
host$ mount /dev/mmcblkp1 /mnt
Find the number of erase blocks of the u-boot partition:
target$ mtdinfo /dev/mtd0
mtd0
Name: u-boot
Type: nor
Eraseblock size: 65536 bytes, 64.0 KiB
Amount of eraseblocks: 64 (4194304 bytes, 4.0 MiB)
Minimum input/output unit size: 1byte
Sub-page size: 1byte
Character device major/minor: 90:0
Bad blocks are allowed: false
Device is writable: true
Erase the u-boot partition and flash it:
target$ flash_erase /dev/mtd0 0x0 64
target$ flashcp /mnt/imx-boot-phyboard-pollux-imx8mp-3-fspi.bin-flash_evk_flexspi /
dev/mtd0
RAUC
The RAUC (Robust Auto-Update Controller) mechanism support has been added to meta-ampliphy. It controls the
procedure of updating a device with new firmware. This includes updating the Linux kernel, Device Tree, and root
filesystem. PHYTEC has written an online manual on how we have intergraded RAUC into our BSPs: L-1006e.A3
RAUC Update & Device Management Manual.

L-1017e.A3 i.MX 8M Plus BSP Manual
•
1.
2.
•
•
•
•
Development
Booting the Kernel from a Network
Booting from a network means loading the kernel over TFTP and the root file system over NFS. The bootloader itself
must already be loaded from another boot device that is available.
Host Preparation
On the development host, a TFTP server must be installed and configured. The following tools will be needed to
boot the Kernel from Ethernet:
A TFTP server
For Ubuntu, install:
host$ sudo apt-get install tftpd-hpa xinetd
After the installation, there are two ways to configure the TFTP server.
TFTP Server Setup
As a stand-alone daemon
Controlled and handled by xinetd
First, create a directory to store the TFTP files:
host$ sudo mkdir /tftpboot
host$ sudo chmod -R 777 /tftpboot
host$ sudo chown -R nobody /tftpboot
Then copy your BSP image files to this directory.You also need to configure a static IP address for the
appropriate interface. The default IP address of the PHYTEC evaluation boards is 192.168.3.11. Setting a host
address 192.168.3.10 with netmask 255.255.255.0 is a good choice.
host$ ifconfig eth1
You will receive:
eth1 Link encap:Ethernet HWadr 00:11:6b:98:e3:47
inet addr:192.168.3.10 Bcast:192.168.3.255 Mask:255.255.255.0 
TFTP as a Stand-alone Daemon
Create or edit /etc/default/tftpd-hpa: