STM32MP157 uboot issue

[lijingyu]

When I download UBOOT using USB, the console appears the following log and repeats. Is this normal? I was wondering if when I modified uboot, it didn't fully fit my board?

NOTICE: CPU: STM32MP157AAA Rev.B
NOTICE: Model: STMicroelectronics STM32MP157A eval daughter on eval mother
INFO: Reset reason (0x54):
INFO: System reset generated by MPU (MPSYSRST)
INFO: PMIC version = 0x21
INFO: Using USB
INFO: Instance 2
INFO: Boot used partition fsbl1
NOTICE: BL2: v2.2-r1.0(debug):
NOTICE: BL2: Built : 09:27:07, May 14 2024
INFO: Using crypto library 'stm32_crypto_lib'
INFO: BL2: Doing platform setup
INFO: RAM: DDR3-DDR3L 32bits 533000Khz
INFO: Memory size = 0x40000000 (1024 MB)
INFO: BL2 runs SP_MIN setup
INFO: BL2: Loading image id 4
INFO: Loading image id=4 at address 0x2ffed000
INFO: Image id=4 loaded: 0x2ffed000 - 0x2ffff000
INFO: BL2: Loading image id 5
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 0
INFO: address 0x2ffe7988
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 0
INFO: address 0x2ffe7988
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: Start Download partition 0 to address 0xc0000000 length 0
INFO: USB : DFU : end of download partition : 0
INFO: Loading image id=5 at address 0xc0100000
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 3
INFO: address 0x2ffe7988
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 3
INFO: address 0x2ffe7988
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: usb_partition_size: partition size : 0xd62eb
INFO: Start Download partition 3 to address 0xc0100000 length 877291
INFO: USB : DFU : end of download partition : 3
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: UPLOAD :
INFO: Phase ID : 0
INFO: address 0xffffffff
INFO: Send detach request
INFO: GETSTATUS :
INFO: DFU_STATE_IDLE
INFO: Receive Detach
INFO: Image id=5 loaded: 0xc0100000 - 0xc01d62eb
WARNING: Skip signature check (header option)
NOTICE: ROTPK is not deployed on platform. Skipping ROTPK verification.
NOTICE: BL2: Booting BL32
INFO: Entry point address = 0x2ffed000
INFO: SPSR = 0x1d3
NOTICE: SP_MIN: v2.2-r1.0(debug):
NOTICE: SP_MIN: Built : 09:27:21, May 14 2024
INFO: ARM GICv2 driver initialized
INFO: stm32mp IWDG1 (12): Secure
INFO: ETZPC: CRYP1 (9) could be non secure
INFO: SP_MIN: Initializing runtime services
INFO: SP_MIN: Preparing exit to normal world

U-Boot 2020.01-stm32mp-r1 (May 14 2024 - 08:54:00 -0700)

CPU: STM32MP157AAA Rev.B
Model: STMicroelectronics STM32MP157C eval daughter on eval mother
Board: stm32mp1 in trusted mode (st,stm32mp157c-ev1)
DRAM: 1 GiB
Clocks:
- MPU : 650 MHz
- MCU : 208.878 MHz
- AXI : 266.500 MHz
- PER : 24 MHz
- DDR : 533 MHz
Fastboot key pressed, STM32Programmer key pressed, entering download mode...
error reading chip id: -110
WDT: Started with servicing (32s timeout)
NAND: 0 MiB
MMC: STM32 SD/MMC: 0, STM32 SD/MMC: 1
In: serial
Out: serial
Err: serial
invalid MAC address in OTP 00:00:00:00:00:00
Net:
Error: ethernet@5800a000 address not set.
No ethernet found.

Hit any key to stop autoboot: 0
Boot over usb0!
partitions : Writing GPT: success!
done
DFU alt info setting: done
No USB device found
usb_gadget_initialize failed
Download done
Reset...
resetting ...
INFO: PSCI Power Domain Map:
INFO: Domain Node : Level 1, parent_node -1, State ON (0x0)
INFO: Domain Node : Level 0, parent_node 0, State ON (0x0)
INFO: CPU Node : MPID 0x0, parent_node 0, State ON (0x0)
INFO: CPU Node : MPID 0xffffffff, parent_node 0, State OFF (0x2)

[PatrickF]

Hi @lijingyu ,

could you please clarify which board you are using ?

Log file seems to show that you are using an old STM32MP157A-EV1 board. Right ?
"STMicroelectronics STM32MP157A eval daughter on eval mother"
"STM32MP157AAA Rev.B"

Is it on a custom board with STM32MP15 got from an ST board ?

Furthermore, I see the following:
"Fastboot key pressed, STM32Programmer key pressed, entering download mode..."

This is probably because the two user buttons are seen as pressed. Might explain the reboot.
Could you check PA13 and PA14 connections ?

On a custom board, this should be adapted/removed in your device tree.

You ecosystem seems also quite old (ecosystem V2.x), please try using latest one (v5.0.2).

Regards.