From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-19.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2C355C07E96 for ; Thu, 8 Jul 2021 09:18:54 +0000 (UTC) Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 76D5B6146E for ; Thu, 8 Jul 2021 09:18:53 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 76D5B6146E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=foss.st.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 9DA7983177; Thu, 8 Jul 2021 11:18:20 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=foss.st.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=foss.st.com header.i=@foss.st.com header.b="xcMwmEDG"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id B07C583146; Thu, 8 Jul 2021 11:18:03 +0200 (CEST) Received: from mx07-00178001.pphosted.com (mx07-00178001.pphosted.com [185.132.182.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 9809F8314A for ; Thu, 8 Jul 2021 11:17:53 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=foss.st.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=prvs=182386853b=patrick.delaunay@foss.st.com Received: from pps.filterd (m0241204.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 1689B1uj021900; Thu, 8 Jul 2021 11:17:53 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foss.st.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type; s=selector1; bh=QJTWOuqEmoL9DEF3p13kxrkwTDp9n1HuwYho/NL5uKo=; b=xcMwmEDGm2GsPrONBbENfiCw18BvHUIWGX1BZqDqNhe8XUpzK4RGAPDTLOV9jo7951hJ HG+gZamXRGsFFEKIeZppotg4m+xtJA5O6K70sOlvwBA7JaWxsPlveFOOPDi1+B+hqhaN KUXzaCXEvESoXE5nxeoX4Ob/66sWJVnLc2x2eA5Gc3KDufpOj2V0Vkt1Z5/ZDCj1fIXG fcUczM70WIp4bNDj6e97/zPYqGIT1NjHsvDVcPVrLCbGFsp8KoWloS3zsP0fNrnUR0fm gZxVzpfb146BZGbJiP4tFHYT883j6Mvy4TWTpzEMaOU2SP+pUsMqsPRln3nv9kzeUgFj 6w== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com with ESMTP id 39n8evy33s-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 08 Jul 2021 11:17:53 +0200 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id B619410002A; Thu, 8 Jul 2021 11:17:52 +0200 (CEST) Received: from Webmail-eu.st.com (sfhdag2node3.st.com [10.75.127.6]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id ABAD221812E; Thu, 8 Jul 2021 11:17:52 +0200 (CEST) Received: from localhost (10.75.127.48) by SFHDAG2NODE3.st.com (10.75.127.6) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 8 Jul 2021 11:17:52 +0200 From: Patrick Delaunay To: CC: Yann GAUTIER , Patrick Delaunay , Patrice Chotard , U-Boot STM32 Subject: [PATCH 4/5] doc: st: stm32mp1: Add FIP support for trusted boot Date: Thu, 8 Jul 2021 11:17:46 +0200 Message-ID: <20210708111743.4.I5b4dcc998de66f175510fed96f6930c7208b492c@changeid> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20210708091747.317500-1-patrick.delaunay@foss.st.com> References: <20210708091747.317500-1-patrick.delaunay@foss.st.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.75.127.48] X-ClientProxiedBy: SFHDAG1NODE2.st.com (10.75.127.2) To SFHDAG2NODE3.st.com (10.75.127.6) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-07-08_04:2021-07-06, 2021-07-08 signatures=0 X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.34 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean TF-A for STM32MP15 now supports the FIP: it is a packaging format which includes the secure monitor, u-boot-nodtb.bin and u-boot.dtb This FIP file is loaded by FSBL = TF-A BL2. This patch updates the board documentation to use this FIP file and no more u-boot.stm32 (with STM32 image header) which is no more generated. Signed-off-by: Patrick Delaunay --- doc/board/st/stm32mp1.rst | 166 ++++++++++++++++++++++---------------- 1 file changed, 97 insertions(+), 69 deletions(-) diff --git a/doc/board/st/stm32mp1.rst b/doc/board/st/stm32mp1.rst index f0c2b09b98..6048fa36a7 100644 --- a/doc/board/st/stm32mp1.rst +++ b/doc/board/st/stm32mp1.rst @@ -60,7 +60,7 @@ Currently the following boards are supported: Boot Sequences -------------- -3 boot configurations are supported with: +2 boot configurations are supported with: +----------+------------------------+-------------------------+--------------+ | **ROM** | **FSBL** | **SSBL** | **OS** | @@ -70,10 +70,12 @@ Boot Sequences | | embedded RAM | DDR | +----------+------------------------+-------------------------+--------------+ -The **Trusted** boot chain -`````````````````````````` +The **Trusted** boot chain with TF-A +````````````````````````````````````` -defconfig_file : stm32mp15_trusted_defconfig +defconfig_file : + + **stm32mp15_defconfig** (for TF-A with FIP support) + + **stm32mp15_trusted_defconfig** (for TF-A without FIP support) +-------------+-------------------------+------------+-------+ | ROM code | FSBL | SSBL | OS | @@ -83,19 +85,16 @@ defconfig_file : stm32mp15_trusted_defconfig | TrustZone |secure monitor | +-------------+-------------------------+------------+-------+ -TF-A performs a full initialization of Secure peripherals and installs a -secure monitor, BL32: +TF-A (BL2) initialize the DDR and loads the next stage binaries from a FIP file: + + BL32: a secure monitor BL32 = SPMin provided by TF-A or OP-TEE : performs a full initialization of Secure peripherals and provides service to normal world + + BL33: a non-trusted firmware = U-Boot, running in normal world and uses the secure monitor to access to secure resources. + + HW_CONFIG: The hardware configuration file = the U-Boot device tree - * SPMin provided by TF-A or - * OP-TEE from specific partitions (teeh, teed, teex). +The **Basic** boot chain with SPL +````````````````````````````````` -U-Boot is running in normal world and uses the secure monitor to access -to secure resources. - -The **Basic** boot chain -```````````````````````` - -defconfig_file : stm32mp15_basic_defconfig +defconfig_file : + + **stm32mp15_basic_defconfig** +-------------+------------+------------+-------+ | ROM code | FSBL | SSBL | OS | @@ -163,12 +162,13 @@ Build Procedure for example: use one output directory for each configuration:: + # export KBUILD_OUTPUT=stm32mp15 # export KBUILD_OUTPUT=stm32mp15_trusted # export KBUILD_OUTPUT=stm32mp15_basic you can build outside of code directory:: - # export KBUILD_OUTPUT=../build/stm32mp15_trusted + # export KBUILD_OUTPUT=../build/stm32mp15 4. Configure U-Boot:: @@ -176,7 +176,7 @@ Build Procedure with : - - For **trusted** boot mode : **stm32mp15_trusted_defconfig** + - For **trusted** boot mode : **stm32mp15_defconfig** or stm32mp15_trusted_defconfig - For basic boot mode: stm32mp15_basic_defconfig 5. Configure the device-tree and build the U-Boot image:: @@ -185,13 +185,13 @@ Build Procedure Examples: - a) trusted boot on ev1:: + a) trusted boot with FIP on ev1:: - # export KBUILD_OUTPUT=stm32mp15_trusted - # make stm32mp15_trusted_defconfig + # export KBUILD_OUTPUT=stm32mp15 + # make stm32mp15_defconfig # make DEVICE_TREE=stm32mp157c-ev1 all - b) trusted with OP-TEE boot on dk2:: + b) trusted boot without FIP on dk2:: # export KBUILD_OUTPUT=stm32mp15_trusted # make stm32mp15_trusted_defconfig @@ -223,16 +223,32 @@ Build Procedure 6. Output files - BootRom and TF-A expect binaries with STM32 image header - SPL expects file with U-Boot uImage header + The ROM code expects FSBL binaries with STM32 image header. + TF-A expects: + - a FIP binary, including the OS monitor (SPmin or OP-TEE) and the U-Boot + binary + device tree + - binaries with STM32 image header: U-Boot and OP-TEE + SPL expects file with U-Boot uImage header. So in the output directory (selected by KBUILD_OUTPUT), you can found the needed files: - For **Trusted** boot (with or without OP-TEE) - - FSBL = **tf-a.stm32** (provided by TF-A compilation) - - SSBL = **u-boot.stm32** + - with FIP: + - FSBL = **tf-a.stm32** and **fip.bin** (provided by TF-A compilation) + - SSBL = **u-boot-nodtb.bin** and **u-boot.dtb** + + The file fip.bin includes the 2 U-Boot files, u-boot-nodtb.bin and u-boot.dtb; + they are needed during the TF-A compilation(BL33=u-boot-nodtb.bin BL33_CFG=u-boot.dtb). + + You can also update a existing it with the tools provided by TF-A: + + # fiptool update --nt-fw u-boot-nodtb.bin --hw-config u-boot.dtb fip-stm32mp157c-ev1.bin + + - without FIP support: + - FSBL = **tf-a.stm32** (provided by TF-A compilation) + - SSBL = **u-boot.stm32** - For Basic boot @@ -299,22 +315,27 @@ Prepare an SD card The minimal requirements for STMP32MP15x boot up to U-Boot are: - GPT partitioning (with gdisk or with sgdisk) -- 2 fsbl partitions, named fsbl1 and fsbl2, size at least 256KiB -- one ssbl partition for U-Boot +- 2 fsbl partitions, named "fsbl1" and "fsbl2", size at least 256KiB +- one partition named "fip" for FIP or U-Boot (TF-A search the "fip" + partition and SPL search the 3th partition, because + CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION=3) + +Without FIP support in TF-A, the 3rd partition "fip" for u-boot.stm32 must +be named "ssbl". Then the minimal GPT partition is: - +-------+--------+---------+-------------+ - | *Num* | *Name* | *Size* | *Content* | - +=======+========+=========+=============+ - | 1 | fsbl1 | 256 KiB | TF-A or SPL | - +-------+--------+---------+-------------+ - | 2 | fsbl2 | 256 KiB | TF-A or SPL | - +-------+--------+---------+-------------+ - | 3 | ssbl | enought | U-Boot | - +-------+--------+---------+-------------+ - | 4 | | | Rootfs | - +-------+--------+---------+-------------+ + +-------+--------+---------+------------------------------+ + | *Num* | *Name* | *Size* | *Content* | + +=======+========+=========+==============================+ + | 1 | fsbl1 | 256 KiB | TF-A BL2 (tf-a.stm32) or SPL | + +-------+--------+---------+------------------------------+ + | 2 | fsbl2 | 256 KiB | TF-A BL2 (tf-a.stm32) or SPL | + +-------+--------+---------+------------------------------+ + | 3 | fip | enought | fip.bin or u-boot.img | + +-------+--------+---------+------------------------------+ + | 4 | | | Rootfs | + +-------+--------+---------+------------------------------+ Add a 4th partition (Rootfs) marked bootable with a file extlinux.conf following the Generic Distribution feature (doc/README.distro for use). @@ -324,22 +345,22 @@ According the used card reader select the correct block device In the next example, it is /dev/mmcblk0 -For example: with gpt table with 128 entries +For example: with gpt table with 128 entries and 4MB fip partition a) remove previous formatting:: # sgdisk -o /dev/ -b) create minimal image:: +b) create minimal image for FIP:: # sgdisk --resize-table=128 -a 1 \ -n 1:34:545 -c 1:fsbl1 \ -n 2:546:1057 -c 2:fsbl2 \ - -n 3:1058:5153 -c 3:ssbl \ - -n 4:5154: -c 4:rootfs \ + -n 3:1058:9249 -c 3:fip \ + -n 4:9250: -c 4:rootfs -A 4:set:2 \ -p /dev/ - With other partition for kernel one partition rootfs for kernel. + With partition 4 marked bootable (bit 2). c) copy the FSBL (2 times) and SSBL file on the correct partition. in this example in partition 1 to 3 @@ -356,7 +377,7 @@ c) copy the FSBL (2 times) and SSBL file on the correct partition. # dd if=tf-a.stm32 of=/dev/mmcblk0p1 # dd if=tf-a.stm32 of=/dev/mmcblk0p2 - # dd if=u-boot.stm32 of=/dev/mmcblk0p3 + # dd if=fip.bin of=/dev/mmcblk0p3 To boot from SD card, select BootPinMode = 1 0 1 and reset. @@ -366,34 +387,41 @@ Prepare eMMC You can use U-Boot to copy binary in eMMC. In the next example, you need to boot from SD card and the images -(u-boot-spl.stm32, u-boot.img for systems without CONFIG_SPL_LOAD_FIT -or u-boot.itb for systems with CONFIG_SPL_LOAD_FIT=y) are presents on -SD card (mmc 0) in ext4 partition 4 (bootfs). +(tf-a.stm32, fip.bin / u-boot-spl.stm32, u-boot.img for systems without CONFIG_SPL_LOAD_FIT +or u-boot.itb for systems with CONFIG_SPL_LOAD_FIT=y) are presents +on SD card (mmc 0) in ext4 partition 4 (bootfs) To boot from SD card, select BootPinMode = 1 0 1 and reset. Then you update the eMMC with the next U-Boot command : a) prepare GPT on eMMC, - example with 2 partitions, bootfs and roots:: + example with 3 partitions, fip, bootfs and roots:: - # setenv emmc_part "name=ssbl,size=2MiB;name=bootfs,type=linux,bootable,size=64MiB;name=rootfs,type=linux,size=512" + # setenv emmc_part "name=fip,size=4MiB;name=bootfs,type=linux,bootable,size=64MiB;name=rootfs,type=linux,size=512" # gpt write mmc 1 ${emmc_part} -b) copy SPL on eMMC on firts boot partition +b) copy FSBL, TF-A or SPL, on first eMMC boot partition (SPL max size is 256kB, with LBA 512, 0x200):: + # ext4load mmc 0:4 0xC0000000 tf-a.stm32 + or # ext4load mmc 0:4 0xC0000000 u-boot-spl.stm32 + # mmc dev 1 # mmc partconf 1 1 1 1 # mmc write ${fileaddr} 0 200 # mmc partconf 1 1 1 0 -c) copy U-Boot in first GPT partition of eMMC:: +c) copy SSBL, FIP or U-Boot binary, in first GPT partition of eMMC:: + # ext4load mmc 0:4 0xC0000000 fip.bin + or # ext4load mmc 0:4 0xC0000000 u-boot.img # Without CONFIG_SPL_LOAD_FIT - OR - ext4load mmc 0:4 0xC0000000 u-boot.itb # With CONFIG_SPL_LOAD_FIT=y + or + # ext4load mmc 0:4 0xC0000000 u-boot.itb # With CONFIG_SPL_LOAD_FIT=y + + # mmc dev 1 # part start mmc 1 1 partstart # mmc write ${fileaddr} ${partstart} ${filesize} @@ -526,14 +554,14 @@ On EV1 board, booting from SD card, without OP-TEE:: dev: RAM alt: 2 name: uramdisk.image.gz layout: RAM_ADDR dev: eMMC alt: 3 name: mmc0_fsbl1 layout: RAW_ADDR dev: eMMC alt: 4 name: mmc0_fsbl2 layout: RAW_ADDR - dev: eMMC alt: 5 name: mmc0_ssbl layout: RAW_ADDR + dev: eMMC alt: 5 name: mmc0_fip layout: RAW_ADDR dev: eMMC alt: 6 name: mmc0_bootfs layout: RAW_ADDR dev: eMMC alt: 7 name: mmc0_vendorfs layout: RAW_ADDR dev: eMMC alt: 8 name: mmc0_rootfs layout: RAW_ADDR dev: eMMC alt: 9 name: mmc0_userfs layout: RAW_ADDR dev: eMMC alt: 10 name: mmc1_boot1 layout: RAW_ADDR dev: eMMC alt: 11 name: mmc1_boot2 layout: RAW_ADDR - dev: eMMC alt: 12 name: mmc1_ssbl layout: RAW_ADDR + dev: eMMC alt: 12 name: mmc1_fip layout: RAW_ADDR dev: eMMC alt: 13 name: mmc1_bootfs layout: RAW_ADDR dev: eMMC alt: 14 name: mmc1_vendorfs layout: RAW_ADDR dev: eMMC alt: 15 name: mmc1_rootfs layout: RAW_ADDR @@ -554,14 +582,14 @@ All the supported device are exported for dfu-util tool:: Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=15, name="mmc1_rootfs", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=14, name="mmc1_vendorfs", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=13, name="mmc1_bootfs", serial="002700333338511934383330" - Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=12, name="mmc1_ssbl", serial="002700333338511934383330" + Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=12, name="mmc1_fip", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=11, name="mmc1_boot2", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=10, name="mmc1_boot1", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=9, name="mmc0_userfs", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=8, name="mmc0_rootfs", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=7, name="mmc0_vendorfs", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=6, name="mmc0_bootfs", serial="002700333338511934383330" - Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=5, name="mmc0_ssbl", serial="002700333338511934383330" + Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=5, name="mmc0_fip", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=4, name="mmc0_fsbl2", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=3, name="mmc0_fsbl1", serial="002700333338511934383330" Found DFU: [0483:df11] ver=9999, devnum=99, cfg=1, intf=0, alt=2, name="uramdisk.image.gz", serial="002700333338511934383330" @@ -572,9 +600,9 @@ You can update the boot device: - SD card (mmc0) :: - $> dfu-util -d 0483:5720 -a 3 -D tf-a-stm32mp157c-ev1-trusted.stm32 - $> dfu-util -d 0483:5720 -a 4 -D tf-a-stm32mp157c-ev1-trusted.stm32 - $> dfu-util -d 0483:5720 -a 5 -D u-boot-stm32mp157c-ev1-trusted.img + $> dfu-util -d 0483:5720 -a 3 -D tf-a-stm32mp157c-ev1.stm32 + $> dfu-util -d 0483:5720 -a 4 -D tf-a-stm32mp157c-ev1.stm32 + $> dfu-util -d 0483:5720 -a 5 -D fip-stm32mp157c-ev1.bin $> dfu-util -d 0483:5720 -a 6 -D st-image-bootfs-openstlinux-weston-stm32mp1.ext4 $> dfu-util -d 0483:5720 -a 7 -D st-image-vendorfs-openstlinux-weston-stm32mp1.ext4 $> dfu-util -d 0483:5720 -a 8 -D st-image-weston-openstlinux-weston-stm32mp1.ext4 @@ -582,9 +610,9 @@ You can update the boot device: - EMMC (mmc1):: - $> dfu-util -d 0483:5720 -a 10 -D tf-a-stm32mp157c-ev1-trusted.stm32 - $> dfu-util -d 0483:5720 -a 11 -D tf-a-stm32mp157c-ev1-trusted.stm32 - $> dfu-util -d 0483:5720 -a 12 -D u-boot-stm32mp157c-ev1-trusted.img + $> dfu-util -d 0483:5720 -a 10 -D tf-a-stm32mp157c-ev1.stm32 + $> dfu-util -d 0483:5720 -a 11 -D tf-a-stm32mp157c-ev1.stm32 + $> dfu-util -d 0483:5720 -a 12 -D fip-stm32mp157c-ev1.bin $> dfu-util -d 0483:5720 -a 13 -D st-image-bootfs-openstlinux-weston-stm32mp1.ext4 $> dfu-util -d 0483:5720 -a 14 -D st-image-vendorfs-openstlinux-weston-stm32mp1.ext4 $> dfu-util -d 0483:5720 -a 15 -D st-image-weston-openstlinux-weston-stm32mp1.ext4 @@ -601,14 +629,14 @@ only the MTD partition on the boot devices are available, for example: - NOR (nor0 = alt 20) & NAND (nand0 = alt 26) :: - $> dfu-util -d 0483:5720 -a 21 -D tf-a-stm32mp157c-ev1-trusted.stm32 - $> dfu-util -d 0483:5720 -a 22 -D tf-a-stm32mp157c-ev1-trusted.stm32 - $> dfu-util -d 0483:5720 -a 23 -D u-boot-stm32mp157c-ev1-trusted.img + $> dfu-util -d 0483:5720 -a 21 -D tf-a-stm32mp157c-ev1.stm32 + $> dfu-util -d 0483:5720 -a 22 -D tf-a-stm32mp157c-ev1.stm32 + $> dfu-util -d 0483:5720 -a 23 -D fip-stm32mp157c-ev1.bin $> dfu-util -d 0483:5720 -a 27 -D st-image-weston-openstlinux-weston-stm32mp1_nand_4_256_multivolume.ubi - NAND (nand0 = alt 21):: - $> dfu-util -d 0483:5720 -a 22 -D tf-a-stm32mp157c-ev1-trusted.stm32 - $> dfu-util -d 0483:5720 -a 23 -D u-boot-stm32mp157c-ev1-trusted.img - $> dfu-util -d 0483:5720 -a 24 -D u-boot-stm32mp157c-ev1-trusted.img + $> dfu-util -d 0483:5720 -a 22 -D tf-a-stm32mp157c-ev1.stm32 + $> dfu-util -d 0483:5720 -a 23 -D fip-stm32mp157c-ev1.bin + $> dfu-util -d 0483:5720 -a 24 -D fip-stm32mp157c-ev1.bin $> dfu-util -d 0483:5720 -a 25 -D st-image-weston-openstlinux-weston-stm32mp1_nand_4_256_multivolume.ubi -- 2.25.1