U-Boot recovery for STM32MP1 DHSOM via DFU - Revision history

Jneuhauser: /* U-Boot booting via DFU */ Add kernel log check also for USB download gadget

2022-09-09T07:42:36Z

U-Boot booting via DFU: Add kernel log check also for USB download gadget

← Older revision		Revision as of 09:42, 9 September 2022
Line 124:		Line 124:
	Then load U-Boot in the DRAM of your STM32MP1 and continue the boot process using the shown key combination.		Then load U-Boot in the DRAM of your STM32MP1 and continue the boot process using the shown key combination.

	=== ~~Check for available DFU device~~ ===		=== Download of U-Boot SPL with <code>dfu-util</code> ===

	(Re-)Connect the USB cable with your host computer and the OTG port of your baseboard and check the kernel log for a available DFU device:		(Re-)Connect the USB cable with your host computer and the OTG port of your baseboard and check the kernel log for a available '''DFU''' device:
	<syntaxhighlight lang="shell">		<syntaxhighlight lang="shell">
	sudo dmesg		sudo dmesg
Line 138:		Line 138:
	usb 2-2: SerialNumber: 0040001D3130510439373430		usb 2-2: SerialNumber: 0040001D3130510439373430
	</syntaxhighlight>		</syntaxhighlight>

	~~=== Download of U-Boot SPL with <code>dfu-util</code> ===~~

	Download of U-Boot SPL with dfu-util to connected device:		Download of U-Boot SPL with dfu-util to connected device:
Line 181:		Line 179:
	</syntaxhighlight>		</syntaxhighlight>

	=== Download of U-Boot with <code>dfu-util</code> ===		=== Download of U-Boot with <code>dfu-util</code> ===

			(Re-)Connect the USB cable with your host computer and the OTG port of your baseboard and check the kernel log for a available '''USB download gadget''' device:
			<syntaxhighlight lang="shell">
			sudo dmesg
			</syntaxhighlight>
			<syntaxhighlight lang="console" highlight="5">
			...
			usb 3-2: new high-speed USB device number 8 using xhci_hcd
			usb 3-2: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.27
			usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
			usb 3-2: Product: USB download gadget
			usb 3-2: Manufacturer: dh
			</syntaxhighlight>

	Download of U-Boot with dfu-util to connected device:		Download of U-Boot with dfu-util to connected device:

Jneuhauser: Fix translation

2022-09-09T06:16:30Z

Fix translation

← Older revision		Revision as of 08:16, 9 September 2022
Line 33:		Line 33:
	=== Download/Build U-Boot SPL and U-Boot binaries ===		=== Download/Build U-Boot SPL and U-Boot binaries ===

	There are two ways to get the required ~~submarine~~ binaries.		There are two ways to get the required U-Boot binaries.
	These can either be downloaded or built from the sources by yourself.		These can either be downloaded or built from the sources by yourself.
	Follow one of the two steps below.		Follow one of the two steps below.

Jneuhauser: Add text to section

2022-09-09T06:15:52Z

Add text to section

← Older revision		Revision as of 08:15, 9 September 2022
Line 32:		Line 32:

	=== Download/Build U-Boot SPL and U-Boot binaries ===		=== Download/Build U-Boot SPL and U-Boot binaries ===

			There are two ways to get the required submarine binaries.
			These can either be downloaded or built from the sources by yourself.
			Follow one of the two steps below.

	==== Download prebuilt binaries ====		==== Download prebuilt binaries ====

Ageisreiter: /* Boot from SD card */

2022-04-25T05:14:15Z

Boot from SD card

← Older revision		Revision as of 07:14, 25 April 2022
Line 332:		Line 332:

	# Hold the button for SD card boot mode on the SODIMM-200 module (DHCOM) below the eMMC chip.		# Hold the button for SD card boot mode on the SODIMM-200 module (DHCOM) below the eMMC chip.
	#:[[File:~~DHCOR_i.MX6ULL_SDP~~-~~Boot~~.jpg\|400px]]		#:[[File:STM32MP1-Button.jpg\|400px]]
	# Reset the device. To reset the device, press the reset button on the baseboard or unplug and plug in the power plug.		# Reset the device. To reset the device, press the reset button on the baseboard or unplug and plug in the power plug.
	# Release the button for SD card boot mode		# Release the button for SD card boot mode

Jneuhauser: /* Write U-Boot SPL and U-Boot to the SD card */

2022-04-14T09:50:37Z

Write U-Boot SPL and U-Boot to the SD card

← Older revision		Revision as of 11:50, 14 April 2022
Line 340:		Line 340:
	=== Write U-Boot SPL and U-Boot to the SD card ===		=== Write U-Boot SPL and U-Boot to the SD card ===

	Follow the ~~instruction~~ in [[#U-Boot booting via SD card\|U-Boot booting via SD card]] to prepare a SD card with a file system on partition 4~~, which~~ contains the required ~~binaries~~ <code>u-boot-spl.stm32</code> and <code>u-boot.itb</code>.		Follow the instructions in [[#U-Boot booting via SD card\|U-Boot booting via SD card]] to prepare an SD card with a file system on partition 4 that contains the required <code>u-boot-spl.stm32</code> and <code>u-boot.itb</code> binaries.

	=== Write U-Boot SPL and U-Boot to SPI-NOR-Flash ===		=== Write U-Boot SPL and U-Boot to SPI-NOR-Flash ===

Jneuhauser at 09:49, 14 April 2022

2022-04-14T09:49:17Z

Show changes

Jneuhauser: /* Check for available DFU device */

2022-04-14T09:12:32Z

Check for available DFU device

← Older revision		Revision as of 11:12, 14 April 2022
Line 121:		Line 121:
	=== Check for available DFU device ===		=== Check for available DFU device ===

	(Re-)Connect the USB cable with your host computer and the OTG port of your baseboard.		(Re-)Connect the USB cable with your host computer and the OTG port of your baseboard and check the kernel log for a available DFU device:
	In the kernel log ~~you should see something like~~:
	<syntaxhighlight lang="shell">		<syntaxhighlight lang="shell">
	sudo dmesg		sudo dmesg

Jneuhauser: Created page with " To recover a corrupted U-Boot on a STM32MP1-based DHCOM, we can use the de..."

2022-04-14T08:50:06Z

Created page with " To recover a corrupted U-Boot on a STM32MP1-based DHCOM, we can use the de..."

New page

To recover a corrupted U-Boot on a STM32MP1-based DHCOM, we can use the default fallback boot source DFU via serial link or USB to temporarily boot U-Boot SPL and U-Boot.
From this U-Boot shell we can write both bootloader images from the SD card to the boot flash.

<div class="toclimit-3">__TOC__</div>

== Requirements ==
=== Software ===
* Linux host computer ([[Virtual Machine for Application Development]] is used in this guide)
* [https://packages.debian.org/stable/dfu-util dfu-util]
* [https://source.denx.de/u-boot/u-boot/-/tree/v2022.04 U-Boot 2022.04] for your board (download and build instructions below)

=== Hardware ===
* STM32MP1 based DHCOM
* DHCOM Premium Developer Kit Baseboard (or Baseboards with OTG ports)
* USB cable for OTG port (Mini USB for PDK2, USB-C for PDK3)

== Preparation ==
This installation was made on the [[Virtual Machine for Application Development]].
All console expressions refer to this Debian system, but any other debian based system should also work.

=== Install dfu-util (debian) ===
<syntaxhighlight lang="shell">
apt-get install dfu-util
</syntaxhighlight>
<syntaxhighlight lang="console">
</syntaxhighlight>

=== Download/Build U-Boot SPL and U-Boot binaries ===

==== Download prebuilt binaries ====

[[media:AACQ30W-7l-Zi_Zutu0Zv-Zua|Dropbox: U-Boot_recovery_for_STM32MP1_DHSOM_via_DFU]] ([https://source.denx.de/u-boot/u-boot/-/tree/v2022.04 source])

<syntaxhighlight lang="shell">
curl -LsS https://www.dropbox.com/sh/os9so01tivajkxs/AACQ30W-7l-Zi_Zutu0Zv-Zua > recovery_binaryies.zip
unzip recovery_binaryies.zip
</syntaxhighlight>
<syntaxhighlight lang="console">
Archive: recovery_binaryies.zip
warning: stripped absolute path spec from /
mapname: conversion of failed
creating: U-Boot_v2022.04_mainline/
creating: U-Boot_v2022.04_mainline/av96/
creating: U-Boot_v2022.04_mainline/pdk2/
creating: U-Boot_v2022.04_mainline/drc02/
creating: U-Boot_v2022.04_mainline/picoitx/
extracting: U-Boot_v2022.04_mainline/av96/u-boot.itb
extracting: U-Boot_v2022.04_mainline/pdk2/u-boot.itb
extracting: U-Boot_v2022.04_mainline/drc02/u-boot.itb
extracting: U-Boot_v2022.04_mainline/picoitx/u-boot.itb
extracting: U-Boot_v2022.04_mainline/av96/u-boot-spl.stm32
extracting: U-Boot_v2022.04_mainline/pdk2/u-boot-spl.stm32
extracting: U-Boot_v2022.04_mainline/drc02/u-boot-spl.stm32
extracting: U-Boot_v2022.04_mainline/picoitx/u-boot-spl.stm32
</syntaxhighlight>

==== Build binaries from source ====

Clone U-Boot mainline source code for release v2022.04:
<syntaxhighlight lang="shell">
UBOOT_SRC=/work/dev/u-boot_v2022.04
mkdir -p $UBOOT_SRC
git clone --branch v2022.04 --depth 1 https://source.denx.de/u-boot/u-boot.git $UBOOT_SRC
cd $UBOOT_SRC
</syntaxhighlight>

Available U-Boot defconfigs for STM32MP1 based DHSOM devices with default device tree in bold:
* '''stm32mp15_dhcom_basic_defconfig''' ('''pdk2''', picoitx, drc02)
* '''stm32mp15_dhcor_basic_defconfig''' ('''avenger96''')
<syntaxhighlight lang="shell">
mkdir -p /work/dev/u-boot
git clone https://source.denx.de/u-boot/u-boot.git -b v2022.04 /work/dev/u-boot
cd /work/dev/u-boot
ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make stm32mp15_dhcom_basic_defconfig
</syntaxhighlight>

Change default device tree (Example for: stm32mp15xx-dhcom-picoitx):
<syntaxhighlight lang="shell">
sed -iE 's/(stm32mp15xx-dhcom-pdk2|stm32mp157a-dhcor-avenger96)/stm32mp15xx-dhcom-picoitx/' .config
</syntaxhighlight>

Build linux binaries with all available cores:
<syntaxhighlight lang="shell">
ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make -j$(nproc)
</syntaxhighlight>
<syntaxhighlight lang="console">
...
SHIPPED dts/dt.dtb
CAT u-boot-dtb.bin
MKIMAGE u-boot.img
COPY u-boot.dtb
MKIMAGE u-boot-dtb.img
MKIMAGE u-boot.itb
...
LD spl/u-boot-spl
OBJCOPY spl/u-boot-spl-nodtb.bin
SYM spl/u-boot-spl.sym
CAT spl/u-boot-spl-dtb.bin
COPY spl/u-boot-spl.bin
BINMAN all
</syntaxhighlight>

Check that the required binaries have been created and are of the appropriate size:
<syntaxhighlight lang="shell">
ls -l u-boot.itb u-boot-spl.stm32
</syntaxhighlight>
<syntaxhighlight lang="console">
-rw-r--r-- 1 devel devel 819720 Apr 11 17:03 u-boot.itb
-rw-r--r-- 1 devel devel 124288 Apr 11 17:03 u-boot-spl.stm32
</syntaxhighlight>

== U-Boot booting via DFU ==

To boot U-Boot SPL and U-Boot via DFU boot mode, you must first check if you have a DFU device connected, then load U-Boot SPL into the SRAM of your STM32MP1 and wait until the DRAM is initialized.
Then load U-Boot in the DRAM of your STM32MP1 and continue the boot process using the shown key combination.

=== Check for available DFU device ===

(Re-)Connect the USB cable with your host computer and the OTG port of your baseboard.
In the kernel log you should see something like:
<syntaxhighlight lang="shell">
sudo dmesg
</syntaxhighlight>
<syntaxhighlight lang="console" highlight="4">
...
usb 2-2: New USB device found, idVendor=0483, idProduct=df11, bcdDevice= 2.00
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-2: Product: DFU in HS Mode @Device ID /0x500, @Revision ID /0x0000
usb 2-2: Manufacturer: STMicroelectronics
usb 2-2: SerialNumber: 0040001D3130510439373430
</syntaxhighlight>

=== Download of U-Boot SPL with <code>dfu-util</code> ===

Download of U-Boot SPL with dfu-util to connected device:
<syntaxhighlight lang="shell">
dfu-util -a 1 -D u-boot-spl.stm32
</syntaxhighlight>
<syntaxhighlight lang="console">
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #1 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 1024
Copying data from PC to DFU device
Download [=========================] 100% 160911 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
</syntaxhighlight>

Output of the serial console:
<syntaxhighlight lang="console">
U-Boot SPL 2022.04 (Apr 05 2022 - 08:27:30 +0200)
Model: STMicroelectronics STM32MP15xx DHCOM Premium Developer Kit (2)
Code: SoM:rev=1,ddr3=3 Board:rev=0
RAM: DDR3L 32bits 2x4Gb 533MHz
Trying to boot from DFU
</syntaxhighlight>

=== Download of U-Boot with <code>dfu-util</code> ===

Download of U-Boot with dfu-util to connected device:
<syntaxhighlight lang="shell">
dfu-util -a 0 -D u-boot.itb
</syntaxhighlight>
<syntaxhighlight lang="console">
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download [=========================] 100% 819232 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
</syntaxhighlight>

Output of the serial console:
<syntaxhighlight lang="console">
#DOWNLOAD ... OK
Ctrl+C to exit ...
</syntaxhighlight>

Output of the serial console after pressing '''Ctrl+C''':
<syntaxhighlight lang="console">
U-Boot 2022.04 (Apr 05 2022 - 08:27:30 +0200)

CPU: STM32MP157CAA Rev.Z
Model: STMicroelectronics STM32MP15xx DHCOM Premium Developer Kit (2)
Board: stm32mp1 in basic mode (dh,stm32mp15xx-dhcom-pdk2)
DRAM: 1 GiB
Clocks:
- MPU : 650 MHz
- MCU : 208.878 MHz
- AXI : 266.500 MHz
- PER : 24 MHz
- DDR : 533 MHz
Core: 255 devices, 31 uclasses, devicetree: separate
MMC: STM32 SD/MMC: 2, STM32 SD/MMC: 0, STM32 SD/MMC: 1
Loading Environment from SPIFlash... SF: Detected w25q16cl with page size 256 Bytes, erase size 4 KiB, total 2 MiB
OK
In: serial
Out: serial
Err: serial
Net: eth0: ethernet@5800a000, eth1: ks8851mll@64000000
Hit any key to stop autoboot: 0
</syntaxhighlight>

== Troubleshooting ==
If there is a U-Boot starting, the DFU procedure may not work properly.
There are two solutions to prevent the start of U-Boot from the SPI-NOR-Flash.

=== SD card boot mode (only HS00014) ===
# Boot in SD card boot mode to prevent booting the broken U-Boot from SPI-NOR-Flash
## Hold the button for SD card boot mode on the SODIMM-200 module (DHCOM) below the eMMC chip.
##:[[File:DHCOR_i.MX6ULL_SDP-Boot.jpg|400px]]
## Reset the device. To reset the device, press the reset button on the baseboard or unplug and plug in the power plug.
## Release the button for SD card boot mode
# If no new output is printed on the serial console (serial port), continue with the DFU booting procedure

=== Delete U-Boot ===
# <code>sf probe</code>
# <code>sf erase 0x0 0xf0000</code>
# Restart the board
# If no new output is printed on the serial console (serial port), continue with the DFU booting procedure