Skip to main content
Visitor II
December 2, 2019
Question

U-boot failed during SD access

  • December 2, 2019
  • 2 replies
  • 922 views

Hello Community

I'm trying to bring up a new architecture board based over STM32MP151aaa core.

From what I see from the serial the u-boot prompts leaving the following trace:

NOTICE: CPU: STM32MP151AAA Rev.B

NOTICE: Model: STMicroelectronics custom STM32CubeMX board

INFO:  Reset reason (0x15):

INFO:   Power-on Reset (rst_por)

INFO:  Using SDMMC

INFO:   Instance 1

INFO:  Boot used partition fsbl1

NOTICE: BL2: v2.0-r1.5(debug):

NOTICE: BL2: Built : 13:13:37, Oct 2 2018

INFO:  BL2: Doing platform setup

INFO:  RAM: DDR3-DDR3L 16bits 533000Khz

INFO:  Memory size = 0x20000000 (512 MB)

INFO:  BL2 runs SP_MIN setup

INFO:  BL2: Loading image id 4

INFO:  Loading image id=4 at address 0x2fff0000

INFO:  Image id=4 loaded: 0x2fff0000 - 0x30000000

INFO:  BL2: Loading image id 5

INFO:  Loading image id=5 at address 0xc0100000

INFO:  STM32 Image size : 800691

WARNING: Skip signature check (header option)

INFO:  Image id=5 loaded: 0xc0100000 - 0xc01c37b3

INFO:  read version 0 current version 0

NOTICE: BL2: Booting BL32

INFO:  Entry point address = 0x2fff0000

INFO:  SPSR = 0x1d3

NOTICE: SP_MIN: v2.0-r1.5(debug):

NOTICE: SP_MIN: Built : 13:13:37, Oct 2 2018

INFO:  ARM GICv2 driver initialized

INFO:  stm32mp RNG1 (12): Secure only

INFO:  stm32mp HSI (18): Secure only

INFO:  stm32mp HSE (20): Secure only

INFO:  stm32mp CSI (22): Secure only

INFO:  stm32mp PLL2 (27): Secure only

INFO:  stm32mp PLL2_R (30): Secure only

INFO:  SP_MIN: Initializing runtime services

INFO:  SP_MIN: Preparing exit to normal world

U-Boot 2018.11-stm32mp-r3 (Nov 14 2018 - 16:10:06 +0000)

CPU: STM32MP151AAA Rev.B

Model: STMicroelectronics custom STM32CubeMX board

Board: stm32mp1 in trusted mode (st,stm32mp151a-sw25v00-mx)

DRAM: 512 MiB

Clocks:

- MPU : 650 MHz

- MCU : 168 MHz

- AXI : 266.500 MHz

- PER : 0 MHz

- DDR : 533 MHz

NAND: 0 MiB

MMC:  STM32 SDMMC2: 0

Loading Environment from EXT4... In:  serial

Out:  serial

Err:  serial

invalid MAC address in OTP 00:00:00:00:00:00Net:  Invalid PHY interface

eqos_probe_resources() failed: -22eth-1: ethernet@5800a000

Hit any key to stop autoboot: 0

Boot over mmc0!

Saving Environment to EXT4... Failed (1)

Now for the moment I ignore the ETH error and I focused on error on EXT4.

I expect that boot it' s ready to load kernel from SD to ram and start with it.

What's going wrong?

Thank' you in advance.

    This topic has been closed for replies.

    2 replies

    Technical Moderator
    December 2, 2019

    I agree that ETH message has to be ignored.

    Please check the partition setup in CubeProgrammer .tsv file

    I recommend that you compare the Device Tree your defined with the one used on a working board (e.g. Discovery DK2)

    The following items in your log are suspects (but might be ok)

    - PER : 0 MHz (it is "24 MHz" on DK2 log)

    - MMC:  STM32 SDMMC2: 0 (it is "MMC:  STM32 SDMMC2: 0, STM32 SDMMC2: 1" on DK2 log)

    Visitor II
    December 2, 2019

    Thank you Patrick for your prompt response.

    In effect we have already done this kind of comparing with the 157A-EV1 that seems to be the closer architecture.

    Yes anyway I'll go to check the PER: clock that 's is suspect.

    What we have noticed that:

    "Loading Environment from EXT4 ..."

    Doesn't appears in a LOG captured from a DK2 demo board.

    What does it means?

    Because It seems that Loading succeed while saving not.

    Or Failed (1) is related to Boot over mmc0!.

    Bye