cancel
Showing results for 
Search instead for 
Did you mean: 

Error: fsbl1 (0x4): invalid address 0x4400 (min=0x80000) during loading flash_layout image to custom STM32MP1 board

ASkri.1
Senior

Hi!

During loading flash_layout image to custom STM32MP1 I've got following error after staring u-boot and truing to load information to partition 0x04 fsbl1:

U-Boot 2020.01-stm32mp-r1 (Jan 06 2020 - 20:56:31 +0000)

CPU: STM32MP157DAB Rev.Z

Model: STMicroelectronics STM32MP157A-DK1 STM32CubeMX board

Board: stm32mp1 in trusted mode (st,stm32mp157a-stm32mp151-dk1-mx)

DRAM: 512 MiB

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...

WDT:  Started with servicing (32s timeout)

NAND: 0 MiB

MMC:  STM32 SD/MMC: 0

In:  serial

Out:  serial

Err:  serial

invalid MAC address in OTP 00:00:00:00:00:00

stm32 vrefbuf timed out: -110

adc@0: can't enable vdd-supply!board_check_usb_power: single shot failed for adc@0[18]!

Net:  No ethernet found.

Hit any key to stop autoboot: 0

Boot over usb0!

Error: fsbl1 (0x4): invalid address 0x4400 (min=0x80000)

DFU alt info setting: done

crq->brequest:0x0

Reset requested

#

UPLOAD ... done

flash-layout .tsv file:

#Opt Id Name Type IP Offset Binary

- 0x01 fsbl1-boot Binary none 0x0 ../../arm-trusted-firmware/tf-a-stm32mp157a-stm32mp151-dk1-mx-serialboot.stm32

- 0x03 ssbl-boot Binary none 0x0 ../../bootloader/u-boot-stm32mp157a-stm32mp151-dk1-mx-trusted.stm32

P 0x04 fsbl1 Binary mmc0 0x00004400 ../../arm-trusted-firmware/tf-a-stm32mp157a-stm32mp151-dk1-mx-trusted.stm32

P 0x05 fsbl2 Binary mmc0 0x00044400 ../../arm-trusted-firmware/tf-a-stm32mp157a-stm32mp151-dk1-mx-trusted.stm32

PD 0x06 ssbl Binary mmc0 0x00084400 ../../bootloader/u-boot-stm32mp157a-stm32mp151-dk1-mx-trusted.stm32

P 0x21 boot System mmc0 0x00284400 ../../st-image-bootfs-openstlinux-weston-stm32mp1-disco-mx.ext4

P 0x22 vendorfs FileSystem mmc0 0x04284400 ../../st-image-vendorfs-openstlinux-weston-stm32mp1-disco-mx.ext4

P 0x23 rootfs FileSystem mmc0 0x05284400 ../../st-image-weston-openstlinux-weston-stm32mp1-disco-mx.ext4

P 0x24 userfs FileSystem mmc0 0x33C84400 ../../st-image-userfs-openstlinux-weston-stm32mp1-disco-mx.ext4

Custom board have mmc connected to SDMMC0 interface and pmic connected to i2c2 instead of i2c4. And nothing more.

I've no ideas which way to go...

Could you please suggest me a ways to debug such situation.

Thank you in advance

Looking forward for your reply

1 ACCEPTED SOLUTION

Accepted Solutions
ASkri.1
Senior

Answering myself... SD and MMC requires different flash-layouts.

View solution in original post

2 REPLIES 2
ASkri.1
Senior

Answering myself... SD and MMC requires different flash-layouts.