1 .. SPDX-License-Identifier: GPL-2.0+ OR BSD-3-Clause
2 .. sectionauthor:: Patrick Delaunay <patrick.delaunay@st.com>
7 This is a quick instruction for setup STM32MP15x boards.
12 U-Boot supports STMP32MP15x SoCs:
18 The STM32MP15x is a Cortex-A MPU aimed at various applications.
22 - Dual core Cortex-A7 application core (Single on STM32MP151)
23 - 2D/3D image composition with GPU (only on STM32MP157)
24 - Standard memories interface support
25 - Standard connectivity, widely inherited from the STM32 MCU family
26 - Comprehensive security support
28 Everything is supported in Linux but U-Boot is limited to:
31 2. SD card/MMC controller (SDMMC)
32 3. NAND controller (FMC)
33 4. NOR controller (QSPI)
34 5. USB controller (OTG DWC2)
35 6. Ethernet controller
37 And the necessary drivers
40 2. STPMIC1 (PMIC and regulator)
41 3. Clock, Reset, Sysreset
44 Currently the following boards are supported:
46 + stm32mp157a-avenger96.dts
55 3 boot configurations are supported with:
57 +----------+------------------------+-------------------------+--------------+
58 | **ROM** | **FSBL** | **SSBL** | **OS** |
59 + **code** +------------------------+-------------------------+--------------+
60 | | First Stage Bootloader | Second Stage Bootloader | Linux Kernel |
61 + +------------------------+-------------------------+--------------+
62 | | embedded RAM | DDR |
63 +----------+------------------------+-------------------------+--------------+
65 The **Trusted** boot chain
66 ``````````````````````````
68 defconfig_file : stm32mp15_trusted_defconfig
70 +-------------+-------------------------+------------+-------+
71 | ROM code | FSBL | SSBL | OS |
72 + +-------------------------+------------+-------+
73 | |Trusted Firmware-A (TF-A)| U-Boot | Linux |
74 +-------------+-------------------------+------------+-------+
75 | TrustZone |TF-A secure monitor |
76 +-------------+-------------------------+------------+-------+
78 TF-A performs a full initialization of Secure peripherals and installs a
79 secure monitor (BL32=SPMin).
81 U-Boot is running in normal world and uses TF-A monitor to access
84 The **Trusted** boot chain with **OP-TEE**
85 ``````````````````````````````````````````
87 defconfig_file : stm32mp15_optee_defconfig
89 +-------------+-------------------------+------------+-------+
90 | ROM code | FSBL | SSBL | OS |
91 + +-------------------------+------------+-------+
92 | |Trusted Firmware-A (TF-A)| U-Boot | Linux |
93 +-------------+-------------------------+------------+-------+
95 +-------------+-------------------------+------------+-------+
97 TF-A performs a full initialization of Secure peripherals and installs OP-TEE
98 from specific partitions (teeh, teed, teex).
100 U-Boot is running in normal world and uses OP-TEE monitor to access
103 The **Basic** boot chain
104 ````````````````````````
106 defconfig_file : stm32mp15_basic_defconfig
108 +-------------+------------+------------+-------+
109 | ROM code | FSBL | SSBL | OS |
110 + +------------+------------+-------+
111 | |U-Boot SPL | U-Boot | Linux |
112 +-------------+------------+------------+-------+
113 | TrustZone | | PSCI from U-Boot |
114 +-------------+------------+------------+-------+
116 SPL has limited security initialization
118 U-Boot is running in secure mode and provide a secure monitor to the kernel
119 with only PSCI support (Power State Coordination Interface defined by ARM).
121 All the STM32MP15x boards supported by U-Boot use the same generic board
122 stm32mp1 which support all the bootable devices.
124 Each board is configured only with the associated device tree.
126 Device Tree Selection
127 ---------------------
129 You need to select the appropriate device tree for your board,
130 the supported device trees for STM32MP15x are:
132 + ev1: eval board with pmic stpmic1 (ev1 = mother board + daughter ed1)
136 + ed1: daughter board with pmic stpmic1
140 + dk1: Discovery board
144 + dk2: Discovery board = dk1 with a BT/WiFI combo and a DSI panel
148 + avenger96: Avenger96 board from Arrow Electronics
150 + stm32mp157a-avenger96
155 1. Install the required tools for U-Boot
157 * install package needed in U-Boot makefile
158 (libssl-dev, swig, libpython-dev...)
160 * install ARMv7 toolchain for 32bit Cortex-A (from Linaro,
161 from SDK for STM32MP15x, or any crosstoolchains from your distribution)
162 (you can use any gcc cross compiler compatible with U-Boot)
164 2. Set the cross compiler::
166 # export CROSS_COMPILE=/path/to/toolchain/arm-linux-gnueabi-
168 3. Select the output directory (optional)::
170 # export KBUILD_OUTPUT=/path/to/output
172 for example: use one output directory for each configuration::
174 # export KBUILD_OUTPUT=stm32mp15_trusted
175 # export KBUILD_OUTPUT=stm32mp15_optee
176 # export KBUILD_OUTPUT=stm32mp15_basic
178 you can build outside of code directory::
180 # export KBUILD_OUTPUT=../build/stm32mp15_trusted
182 4. Configure U-Boot::
184 # make <defconfig_file>
186 with <defconfig_file>:
188 - For **trusted** boot mode : **stm32mp15_trusted_defconfig**
189 - For **trusted** with OP-TEE boot mode : **stm32mp15_optee_defconfig**
190 - For basic boot mode: stm32mp15_basic_defconfig
192 5. Configure the device-tree and build the U-Boot image::
194 # make DEVICE_TREE=<name> all
198 a) trusted boot on ev1::
200 # export KBUILD_OUTPUT=stm32mp15_trusted
201 # make stm32mp15_trusted_defconfig
202 # make DEVICE_TREE=stm32mp157c-ev1 all
204 b) trusted with OP-TEE boot on dk2::
206 # export KBUILD_OUTPUT=stm32mp15_optee
207 # make stm32mp15_optee_defconfig
208 # make DEVICE_TREE=stm32mp157c-dk2 all
210 c) basic boot on ev1::
212 # export KBUILD_OUTPUT=stm32mp15_basic
213 # make stm32mp15_basic_defconfig
214 # make DEVICE_TREE=stm32mp157c-ev1 all
216 d) basic boot on ed1::
218 # export KBUILD_OUTPUT=stm32mp15_basic
219 # make stm32mp15_basic_defconfig
220 # make DEVICE_TREE=stm32mp157c-ed1 all
222 e) basic boot on dk1::
224 # export KBUILD_OUTPUT=stm32mp15_basic
225 # make stm32mp15_basic_defconfig
226 # make DEVICE_TREE=stm32mp157a-dk1 all
228 f) basic boot on avenger96::
230 # export KBUILD_OUTPUT=stm32mp15_basic
231 # make stm32mp15_basic_defconfig
232 # make DEVICE_TREE=stm32mp157a-avenger96 all
236 BootRom and TF-A expect binaries with STM32 image header
237 SPL expects file with U-Boot uImage header
239 So in the output directory (selected by KBUILD_OUTPUT),
240 you can found the needed files:
242 - For **Trusted** boot (with or without OP-TEE)
244 - FSBL = **tf-a.stm32** (provided by TF-A compilation)
245 - SSBL = **u-boot.stm32**
249 - FSBL = spl/u-boot-spl.stm32
252 Switch Setting for Boot Mode
253 ----------------------------
255 You can select the boot mode, on the board with one switch, to select
256 the boot pin values = BOOT0, BOOT1, BOOT2
258 +-------------+---------+---------+---------+
259 |*Boot Mode* | *BOOT2* | *BOOT1* | *BOOT0* |
260 +=============+=========+=========+=========+
261 | Recovery | 0 | 0 | 0 |
262 +-------------+---------+---------+---------+
264 +-------------+---------+---------+---------+
266 +-------------+---------+---------+---------+
268 +-------------+---------+---------+---------+
269 | Reserved | 1 | 0 | 0 |
270 +-------------+---------+---------+---------+
271 | SD-Card | 1 | 0 | 1 |
272 +-------------+---------+---------+---------+
273 | Recovery | 1 | 1 | 0 |
274 +-------------+---------+---------+---------+
275 | SPI-NAND | 1 | 1 | 1 |
276 +-------------+---------+---------+---------+
278 - on the **daugther board ed1 = MB1263** with the switch SW1
279 - on **Avenger96** with switch S3 (NOR and SPI-NAND are not applicable)
280 - on board **DK1/DK2** with the switch SW1 = BOOT0, BOOT2
281 with only 2 pins available (BOOT1 is forced to 0 and NOR not supported),
282 the possible value becomes:
284 +-------------+---------+---------+
285 |*Boot Mode* | *BOOT2* | *BOOT0* |
286 +=============+=========+=========+
288 +-------------+---------+---------+
290 +-------------+---------+---------+
292 +-------------+---------+---------+
294 +-------------+---------+---------+
296 Recovery is a boot from serial link (UART/USB) and it is used with
297 STM32CubeProgrammer tool to load executable in RAM and to update the flash
298 devices available on the board (NOR/NAND/eMMC/SD card).
300 The communication between HOST and board is based on
302 - for UARTs : the uart protocol used with all MCU STM32
303 - for USB : based on USB DFU 1.1 (without the ST extensions used on MCU STM32)
308 The minimal requirements for STMP32MP15x boot up to U-Boot are:
310 - GPT partitioning (with gdisk or with sgdisk)
311 - 2 fsbl partitions, named fsbl1 and fsbl2, size at least 256KiB
312 - one ssbl partition for U-Boot
314 Then the minimal GPT partition is:
316 +-------+--------+---------+-------------+
317 | *Num* | *Name* | *Size* | *Content* |
318 +=======+========+=========+=============+
319 | 1 | fsbl1 | 256 KiB | TF-A or SPL |
320 +-------+--------+---------+-------------+
321 | 2 | fsbl2 | 256 KiB | TF-A or SPL |
322 +-------+--------+---------+-------------+
323 | 3 | ssbl | enought | U-Boot |
324 +-------+--------+---------+-------------+
325 | 4 | <any> | <any> | Rootfs |
326 +-------+--------+---------+-------------+
328 Add a 4th partition (Rootfs) marked bootable with a file extlinux.conf
329 following the Generic Distribution feature (doc/README.distro for use).
331 According the used card reader select the correct block device
332 (for example /dev/sdx or /dev/mmcblk0).
334 In the next example, it is /dev/mmcblk0
336 For example: with gpt table with 128 entries
338 a) remove previous formatting::
340 # sgdisk -o /dev/<SD card dev>
342 b) create minimal image::
344 # sgdisk --resize-table=128 -a 1 \
345 -n 1:34:545 -c 1:fsbl1 \
346 -n 2:546:1057 -c 2:fsbl2 \
347 -n 3:1058:5153 -c 3:ssbl \
348 -n 4:5154: -c 4:rootfs \
349 -p /dev/<SD card dev>
351 With other partition for kernel one partition rootfs for kernel.
353 c) copy the FSBL (2 times) and SSBL file on the correct partition.
354 in this example in partition 1 to 3
356 for basic boot mode : <SD card dev> = /dev/mmcblk0::
358 # dd if=u-boot-spl.stm32 of=/dev/mmcblk0p1
359 # dd if=u-boot-spl.stm32 of=/dev/mmcblk0p2
360 # dd if=u-boot.img of=/dev/mmcblk0p3
362 for trusted boot mode: ::
364 # dd if=tf-a.stm32 of=/dev/mmcblk0p1
365 # dd if=tf-a.stm32 of=/dev/mmcblk0p2
366 # dd if=u-boot.stm32 of=/dev/mmcblk0p3
368 To boot from SD card, select BootPinMode = 1 0 1 and reset.
373 You can use U-Boot to copy binary in eMMC.
375 In the next example, you need to boot from SD card and the images
376 (u-boot-spl.stm32, u-boot.img) are presents on SD card (mmc 0)
377 in ext4 partition 4 (bootfs).
379 To boot from SD card, select BootPinMode = 1 0 1 and reset.
381 Then you update the eMMC with the next U-Boot command :
383 a) prepare GPT on eMMC,
384 example with 2 partitions, bootfs and roots::
386 # setenv emmc_part "name=ssbl,size=2MiB;name=bootfs,type=linux,bootable,size=64MiB;name=rootfs,type=linux,size=512"
387 # gpt write mmc 1 ${emmc_part}
389 b) copy SPL on eMMC on firts boot partition
390 (SPL max size is 256kB, with LBA 512, 0x200)::
392 # ext4load mmc 0:4 0xC0000000 u-boot-spl.stm32
394 # mmc partconf 1 1 1 1
395 # mmc write ${fileaddr} 0 200
396 # mmc partconf 1 1 1 0
398 c) copy U-Boot in first GPT partition of eMMC::
400 # ext4load mmc 0:4 0xC0000000 u-boo t.img
402 # part start mmc 1 1 partstart
403 # mmc write ${fileaddr} ${partstart} ${filesize}
405 To boot from eMMC, select BootPinMode = 0 1 0 and reset.
410 Please read doc/README.enetaddr for the implementation guidelines for mac id
411 usage. Basically, environment has precedence over board specific storage.
413 For STMicroelectonics board, it is retrieved in STM32MP15x OTP :
415 - OTP_57[31:0] = MAC_ADDR[31:0]
416 - OTP_58[15:0] = MAC_ADDR[47:32]
418 To program a MAC address on virgin OTP words above, you can use the fuse command
419 on bank 0 to access to internal OTP:
421 Prerequisite: check if a MAC address isn't yet programmed in OTP
423 1) check OTP: their value must be equal to 0
425 STM32MP> fuse sense 0 57 2
427 Word 0x00000039: 00000000 00000000
429 2) check environment variable
431 STM32MP> env print ethaddr
432 ## Error: "ethaddr" not defined
434 Example to set mac address "12:34:56:78:9a:bc"
438 STM32MP> fuse prog -y 0 57 0x78563412 0x0000bc9a
442 STM32MP> fuse sense 0 57 2
444 Word 0x00000039: 78563412 0000bc9a
446 3) next REBOOT, in the trace::
448 ### Setting environment from OTP MAC address = "12:34:56:78:9a:bc"
450 4) check env update::
452 STM32MP> env print ethaddr
453 ethaddr=12:34:56:78:9a:bc
455 .. warning:: This command can't be executed twice on the same board as
456 OTP are protected. It is already done for the board
457 provided by STMicroelectronics.
462 U-Boot can boot the coprocessor before the kernel (coprocessor early boot).
464 a) Manuallly by using rproc commands (update the bootcmd)
468 # env set name_copro "rproc-m4-fw.elf"
469 # env set dev_copro 0
470 # env set loadaddr_copro 0xC1000000
472 Load binary from bootfs partition (number 4) on SD card (mmc 0)::
474 # ext4load mmc 0:4 ${loadaddr_copro} ${name_copro}
476 => ${filesize} variable is updated with the size of the loaded file.
478 Start M4 firmware with remote proc command::
481 # rproc load ${dev_copro} ${loadaddr_copro} ${filesize}
482 # rproc start ${dev_copro}"00270033
484 b) Automatically by using FIT feature and generic DISTRO bootcmd
486 see examples in the board stm32mp1 directory: fit_copro_kernel_dtb.its
488 Generate FIT including kernel + device tree + M4 firmware with cfg with M4 boot::
490 $> mkimage -f fit_copro_kernel_dtb.its fit_copro_kernel_dtb.itb
492 Then using DISTRO configuration file: see extlinux.conf to select the correct
501 The DFU is supported on ST board.
503 The env variable dfu_alt_info is automatically build, and all
504 the memory present on the ST boards are exported.
506 The dfu mode is started by the command::
510 On EV1 board, booting from SD card, without OP-TEE::
513 DFU alt settings list:
514 dev: RAM alt: 0 name: uImage layout: RAM_ADDR
515 dev: RAM alt: 1 name: devicetree.dtb layout: RAM_ADDR
516 dev: RAM alt: 2 name: uramdisk.image.gz layout: RAM_ADDR
517 dev: eMMC alt: 3 name: sdcard_fsbl1 layout: RAW_ADDR
518 dev: eMMC alt: 4 name: sdcard_fsbl2 layout: RAW_ADDR
519 dev: eMMC alt: 5 name: sdcard_ssbl layout: RAW_ADDR
520 dev: eMMC alt: 6 name: sdcard_bootfs layout: RAW_ADDR
521 dev: eMMC alt: 7 name: sdcard_vendorfs layout: RAW_ADDR
522 dev: eMMC alt: 8 name: sdcard_rootfs layout: RAW_ADDR
523 dev: eMMC alt: 9 name: sdcard_userfs layout: RAW_ADDR
524 dev: eMMC alt: 10 name: emmc_fsbl1 layout: RAW_ADDR
525 dev: eMMC alt: 11 name: emmc_fsbl2 layout: RAW_ADDR
526 dev: eMMC alt: 12 name: emmc_ssbl layout: RAW_ADDR
527 dev: eMMC alt: 13 name: emmc_bootfs layout: RAW_ADDR
528 dev: eMMC alt: 14 name: emmc_vendorfs layout: RAW_ADDR
529 dev: eMMC alt: 15 name: emmc_rootfs layout: RAW_ADDR
530 dev: eMMC alt: 16 name: emmc_userfs layout: RAW_ADDR
531 dev: MTD alt: 17 name: nor_fsbl1 layout: RAW_ADDR
532 dev: MTD alt: 18 name: nor_fsbl2 layout: RAW_ADDR
533 dev: MTD alt: 19 name: nor_ssbl layout: RAW_ADDR
534 dev: MTD alt: 20 name: nor_env layout: RAW_ADDR
535 dev: MTD alt: 21 name: nand_fsbl layout: RAW_ADDR
536 dev: MTD alt: 22 name: nand_ssbl1 layout: RAW_ADDR
537 dev: MTD alt: 23 name: nand_ssbl2 layout: RAW_ADDR
538 dev: MTD alt: 24 name: nand_UBI layout: RAW_ADDR
539 dev: VIRT alt: 25 name: OTP layout: RAW_ADDR
540 dev: VIRT alt: 26 name: PMIC layout: RAW_ADDR
542 All the supported device are exported for dfu-util tool::
545 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=26, name="PMIC", serial="002700333338511934383330"
546 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=25, name="OTP", serial="002700333338511934383330"
547 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=24, name="nand_UBI", serial="002700333338511934383330"
548 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=23, name="nand_ssbl2", serial="002700333338511934383330"
549 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=22, name="nand_ssbl1", serial="002700333338511934383330"
550 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=21, name="nand_fsbl", serial="002700333338511934383330"
551 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=20, name="nor_env", serial="002700333338511934383330"
552 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=19, name="nor_ssbl", serial="002700333338511934383330"
553 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=18, name="nor_fsbl2", serial="002700333338511934383330"
554 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=17, name="nor_fsbl1", serial="002700333338511934383330"
555 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=16, name="emmc_userfs", serial="002700333338511934383330"
556 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=15, name="emmc_rootfs", serial="002700333338511934383330"
557 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=14, name="emmc_vendorfs", serial="002700333338511934383330"
558 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=13, name="emmc_bootfs", serial="002700333338511934383330"
559 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=12, name="emmc_ssbl", serial="002700333338511934383330"
560 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=11, name="emmc_fsbl2", serial="002700333338511934383330"
561 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=10, name="emmc_fsbl1", serial="002700333338511934383330"
562 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=9, name="sdcard_userfs", serial="002700333338511934383330"
563 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=8, name="sdcard_rootfs", serial="002700333338511934383330"
564 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=7, name="sdcard_vendorfs", serial="002700333338511934383330"
565 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=6, name="sdcard_bootfs", serial="002700333338511934383330"
566 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=5, name="sdcard_ssbl", serial="002700333338511934383330"
567 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=4, name="sdcard_fsbl2", serial="002700333338511934383330"
568 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=3, name="sdcard_fsbl1", serial="002700333338511934383330"
569 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=2, name="uramdisk.image.gz", serial="002700333338511934383330"
570 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=1, name="devicetree.dtb", serial="002700333338511934383330"
571 Found DFU: [0483:5720] ver=9999, devnum=99, cfg=1, intf=0, alt=0, name="uImage", serial="002700333338511934383330"
573 You can update the boot device:
577 $> dfu-util -d 0483:5720 -a 3 -D tf-a-stm32mp157c-ev1-trusted.stm32
578 $> dfu-util -d 0483:5720 -a 4 -D tf-a-stm32mp157c-ev1-trusted.stm32
579 $> dfu-util -d 0483:5720 -a 5 -D u-boot-stm32mp157c-ev1-trusted.img
580 $> dfu-util -d 0483:5720 -a 6 -D st-image-bootfs-openstlinux-weston-stm32mp1.ext4
581 $> dfu-util -d 0483:5720 -a 7 -D st-image-vendorfs-openstlinux-weston-stm32mp1.ext4
582 $> dfu-util -d 0483:5720 -a 8 -D st-image-weston-openstlinux-weston-stm32mp1.ext4
583 $> dfu-util -d 0483:5720 -a 9 -D st-image-userfs-openstlinux-weston-stm32mp1.ext4
587 $> dfu-util -d 0483:5720 -a 10 -D tf-a-stm32mp157c-ev1-trusted.stm32
588 $> dfu-util -d 0483:5720 -a 11 -D tf-a-stm32mp157c-ev1-trusted.stm32
589 $> dfu-util -d 0483:5720 -a 12 -D u-boot-stm32mp157c-ev1-trusted.img
590 $> dfu-util -d 0483:5720 -a 13 -D st-image-bootfs-openstlinux-weston-stm32mp1.ext4
591 $> dfu-util -d 0483:5720 -a 14 -D st-image-vendorfs-openstlinux-weston-stm32mp1.ext4
592 $> dfu-util -d 0483:5720 -a 15 -D st-image-weston-openstlinux-weston-stm32mp1.ext4
593 $> dfu-util -d 0483:5720 -a 16 -D st-image-userfs-openstlinux-weston-stm32mp1.ext4
597 $> dfu-util -d 0483:5720 -a 17 -D tf-a-stm32mp157c-ev1-trusted.stm32
598 $> dfu-util -d 0483:5720 -a 18 -D tf-a-stm32mp157c-ev1-trusted.stm32
599 $> dfu-util -d 0483:5720 -a 19 -D u-boot-stm32mp157c-ev1-trusted.img
601 - NAND (UBI partition used for NAND only boot or NOR + NAND boot)::
603 $> dfu-util -d 0483:5720 -a 21 -D tf-a-stm32mp157c-ev1-trusted.stm32
604 $> dfu-util -d 0483:5720 -a 22 -D u-boot-stm32mp157c-ev1-trusted.img
605 $> dfu-util -d 0483:5720 -a 23 -D u-boot-stm32mp157c-ev1-trusted.img
606 $> dfu-util -d 0483:5720 -a 24 -D st-image-weston-openstlinux-weston-stm32mp1_nand_4_256_multivolume.ubi
608 - you can also dump the OTP and the PMIC NVM with::
610 $> dfu-util -d 0483:5720 -a 25 -U otp.bin
611 $> dfu-util -d 0483:5720 -a 26 -U pmic.bin