Skip to content

Conversation

@passgat
Copy link

@passgat passgat commented Jan 4, 2026

Comparing the SD card boot with the eMMC one, the DTS differs as follows:

  •   fwu-mdata-store = <0x00000085>;
    
  •   fwu-mdata-store = "/soc@0/bus@42080000/mmc@48230000";
    

In both cases, the U-Boot DTS loaded by tf-a-stm32mp at address 0x84400000 was obtained with the following commands:

STM32MP> fdt addr 0x84400000
Working FDT set to 84400000
STM32MP> fdt print

As shown in the diff, the working case (SD card) uses a numeric value, i.e. the phandle of the sdmmc1 node, while the eMMC case uses a path. This patch updates the fwu-mdata-store property to use the phandle instead of the path.

Please do not submit a Pull Request via github. Our project makes use of
mailing lists for patch submission and review. For more details please
see https://u-boot.readthedocs.io/en/latest/develop/sending_patches.html

The only exception to this is in order to trigger a CI loop on Azure prior
to posting of patches.

Comparing the SD card boot with the eMMC one, the DTS differs as follows:

-       fwu-mdata-store = <0x00000085>;
+       fwu-mdata-store = "/soc@0/bus@42080000/mmc@48230000";

In both cases, the U-Boot DTS loaded by tf-a-stm32mp at address 0x84400000
was obtained with the following commands:

STM32MP> fdt addr 0x84400000
Working FDT set to 84400000
STM32MP> fdt print

As shown in the diff, the working case (SD card) uses a numeric value,
i.e. the phandle of the sdmmc1 node, while the eMMC case uses a path.
This patch updates the fwu-mdata-store property to use the phandle
instead of the path.

Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant