cancel
Showing results for 
Search instead for 
Did you mean: 

Problems encountered when burning emmc using STM32CubeProgrammer

Ivy7
Associate II

Hello STMicroelectronics Community:

 I read this wiki:https://wiki.st.com/stm32mpu/wiki/STM32CubeProgrammer_flashlayout. So I have some questions:

1.Why are the offset addresses of fsbl1 and fsbl2 boot1 and boot2 in the following example? I noticed that except for emmc, this two values of other burning methods are a specific address.

Ivy7_0-1749524595554.png

2.What is the meaning of metadatabin?

 

Thanks,

Ivy7

 

1 ACCEPTED SOLUTION

Accepted Solutions
PatrickF
ST Employee

Hi @Ivy7 

Title of the post is referring to problems encountered, but information seems missing (board, messages, version, etc...).

 

Regarding you questions:

1) Unlike other Flash, eMMC provide specific boot partitions not part of eMMC data partition, this explain why there is no offset for those. More explanation could be found in JEDEC JESD84-B51.

2) I think metadata.bin convey some TF-A parameters like the DDR settings

 

Regards.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

View solution in original post

1 REPLY 1
PatrickF
ST Employee

Hi @Ivy7 

Title of the post is referring to problems encountered, but information seems missing (board, messages, version, etc...).

 

Regarding you questions:

1) Unlike other Flash, eMMC provide specific boot partitions not part of eMMC data partition, this explain why there is no offset for those. More explanation could be found in JEDEC JESD84-B51.

2) I think metadata.bin convey some TF-A parameters like the DDR settings

 

Regards.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.