Skip to contentSkip to conversation

DTB_RESELECT/MULTI DTB with SPL flow

DISCUSSION Michal Simek 2 participants 3 messages Jun 11, 2021 – Jun 28, 2021

lore
Share & tools
lore
#0 lore raw

Hi,

I am just trying to wrap my head around DTB_RESELECT feature. ZynqMP is using u-boot.itb which is u-boot/atf + a lot of DT files. As of now SPL should pick the right one load it predefined location which U-Boot proper pickup.
Others DTBs are not loaded at all.
This is working fine and I expect it should work like this even with DTB_RESELECT enabled because you need to have base DTB for being able to do platform detection.
I have hookup platform detection in embedded_dtb_select and I know which board revision I am running at and struggling how to tell u-boot what to do.

What should be the right flow for changing DTB at run time? Where they should be stored? I would expect that I need to have FIT image in memory for all board revisions and u-boot should be calling board_fit_config_name_match() which will decide which DT is correct based on board detection done in embedded_dtb_select().

Thanks,
Michal

#1 lore raw

Hi Michal,

Quoted 4 lines · Michal Simek

Hi,

I am just trying to wrap my head around DTB_RESELECT feature.

Did you intend to cc the author of that?

Does doc/README.multi-dtb-fit help?

Quoted 10 lines

ZynqMP is using u-boot.itb which is u-boot/atf + a lot of DT files. As of now SPL should pick the right one load it predefined location which U-Boot proper pickup.
Others DTBs are not loaded at all.
This is working fine and I expect it should work like this even with DTB_RESELECT enabled because you need to have base DTB for being able to do platform detection.
I have hookup platform detection in embedded_dtb_select and I know which board revision I am running at and struggling how to tell u-boot what to do.

Quoted 5 lines

What should be the right flow for changing DTB at run time? Where they should be stored? I would expect that I need to have FIT image in memory for all board revisions and u-boot should be calling board_fit_config_name_match() which will decide which DT is correct based on board detection done in embedded_dtb_select().

Yes you can use a FIT to hold the DTs. You can also use binman I suppose (the 'files' entry type perhaps).

Regards,
Simon

#2 lore raw

Hi Simon,

Quoted 22 lines · Simon Glass

Hi Michal,

Quoted 4 lines · Michal Simek

Hi,

I am just trying to wrap my head around DTB_RESELECT feature.

Did you intend to cc the author of that?

Does doc/README.multi-dtb-fit help?

Quoted 10 lines

ZynqMP is using u-boot.itb which is u-boot/atf + a lot of DT files. As of now SPL should pick the right one load it predefined location which U-Boot proper pickup.
Others DTBs are not loaded at all.
This is working fine and I expect it should work like this even with DTB_RESELECT enabled because you need to have base DTB for being able to do platform detection.
I have hookup platform detection in embedded_dtb_select and I know which board revision I am running at and struggling how to tell u-boot what to do.

Quoted 8 lines
Quoted 5 lines

What should be the right flow for changing DTB at run time? Where they should be stored? I would expect that I need to have FIT image in memory for all board revisions and u-boot should be calling board_fit_config_name_match() which will decide which DT is correct based on board detection done in embedded_dtb_select().

Yes you can use a FIT to hold the DTs. You can also use binman I suppose (the 'files' entry type perhaps).

I got it working. Also found one alignment issue which needs to be fixed. And also DT overlays are not supported now.

Thanks,
Michal