Skip to contentSkip to conversation

Binman entry 'u-boot-any' not found in list

DISCUSSION Neha Malcom Francis 5 participants 7 messages Oct 28, 2022 – Oct 31, 2022

lore
Share & tools
lore
#0 lore raw

Hi!

U-Boot build for J721E with binman enabled on the latest tip of the master branch throws an error when I try to use u-boot-spl-nodtb entry in my dtsi.

What I'm trying to do is, to show I've made a small example (https://github.com/nehamalcom/u-boot/commit/f53dc83944f7774008afbb24fff42904862e9efe) that is:

&binman {
    	foo {
	    	filename = "foo.bin";
		u-boot-spl-nodtb {
		};
	};
};

which throws the error (https://gist.github.com/nehamalcom/4d855db7e4d5bd03aa29099b0e915e53):

binman: Section '/binman/foo': Symbol '_binman_u_boot_any_prop_image_pos'
in entry '/binman/foo/u-boot-spl-nodtb': Entry 'u-boot-any' not
found in list (u-boot-spl-nodtb,main-section)

This can be traced to the WriteSymbols() in etype/u_boot_spl_nodtb.py. On commenting out this function since it's not necessary in our use-case, the build was successful (https://github.com/nehamalcom/u-boot/commit/5666721860e1d2f759440a00c4aee8b6e89b54b3)

Why is binman not picking up on the "any" and choosing u-boot-spl-nodtb from the list?

Signature · 2 lines
Thanking You
Neha Malcom Francis
#1 lore raw

[Adding Alper - binmam maintainer and Oliver, who faced the same issue on imx8]

Quoted 38 lines · Neha Malcom Francis

Hi!

U-Boot build for J721E with binman enabled on the latest tip of the master branch throws an error when I try to use u-boot-spl-nodtb entry in my dtsi.

What I'm trying to do is, to show I've made a small example
(https://github.com/nehamalcom/u-boot/commit/f53dc83944f7774008afbb24fff42904862e9efe)
that is:

&binman {
        foo {
                filename = "foo.bin";
                u-boot-spl-nodtb {
                };
        };
};

which throws the error
(https://gist.github.com/nehamalcom/4d855db7e4d5bd03aa29099b0e915e53):

binman: Section '/binman/foo': Symbol '_binman_u_boot_any_prop_image_pos'
in entry '/binman/foo/u-boot-spl-nodtb': Entry 'u-boot-any' not
found in list (u-boot-spl-nodtb,main-section)

This can be traced to the WriteSymbols() in etype/u_boot_spl_nodtb.py. On commenting out this function since it's not necessary in our use-case, the build was successful
(https://github.com/nehamalcom/u-boot/commit/5666721860e1d2f759440a00c4aee8b6e89b54b3)

Why is binman not picking up on the "any" and choosing u-boot-spl-nodtb from the list?

--
Thanking You
Neha Malcom Francis

#2 lore raw

Hi Neha,

Quoted 38 lines · Fabio Estevam

[Adding Alper - binmam maintainer and Oliver, who faced the same issue on imx8]

Quoted 34 lines · Neha Malcom Francis

Hi!

U-Boot build for J721E with binman enabled on the latest tip of the master branch throws an error when I try to use u-boot-spl-nodtb entry in my dtsi.

What I'm trying to do is, to show I've made a small example
(https://github.com/nehamalcom/u-boot/commit/f53dc83944f7774008afbb24fff42904862e9efe)
that is:

&binman {
        foo {
                filename = "foo.bin";
                u-boot-spl-nodtb {
                };
        };
};

which throws the error
(https://gist.github.com/nehamalcom/4d855db7e4d5bd03aa29099b0e915e53):

binman: Section '/binman/foo': Symbol '_binman_u_boot_any_prop_image_pos'
in entry '/binman/foo/u-boot-spl-nodtb': Entry 'u-boot-any' not
found in list (u-boot-spl-nodtb,main-section)

This can be traced to the WriteSymbols() in etype/u_boot_spl_nodtb.py. On commenting out this function since it's not necessary in our use-case, the build was successful
(https://github.com/nehamalcom/u-boot/commit/5666721860e1d2f759440a00c4aee8b6e89b54b3)

Why is binman not picking up on the "any" and choosing u-boot-spl-nodtb from the list?

You might need this patch?

https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/

Regards,
Simon

#3 lore raw

Hi Simon,

Quoted 39 lines · Simon Glass

Hi Neha,

Quoted 36 lines · Fabio Estevam

[Adding Alper - binmam maintainer and Oliver, who faced the same issue on imx8]

Quoted 32 lines · Neha Malcom Francis

Hi!

U-Boot build for J721E with binman enabled on the latest tip of the master branch throws an error when I try to use u-boot-spl-nodtb entry in my dtsi.

What I'm trying to do is, to show I've made a small example
(https://github.com/nehamalcom/u-boot/commit/f53dc83944f7774008afbb24fff42904862e9efe)
that is:

&binman {
         foo {
                 filename = "foo.bin";
                 u-boot-spl-nodtb {
                 };
         };
};

which throws the error
(https://gist.github.com/nehamalcom/4d855db7e4d5bd03aa29099b0e915e53):

binman: Section '/binman/foo': Symbol '_binman_u_boot_any_prop_image_pos'
in entry '/binman/foo/u-boot-spl-nodtb': Entry 'u-boot-any' not
found in list (u-boot-spl-nodtb,main-section)

This can be traced to the WriteSymbols() in etype/u_boot_spl_nodtb.py. On commenting out this function since it's not necessary in our use-case, the build was successful
(https://github.com/nehamalcom/u-boot/commit/5666721860e1d2f759440a00c4aee8b6e89b54b3)

Quoted 6 lines
Quoted 2 lines
Quoted 2 lines

Why is binman not picking up on the "any" and choosing u-boot-spl-nodtb from the list?

You might need this patch?

https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/

Even after applying this patch, the entry is not working for me.

Quoted 3 lines

Regards,
Simon

Signature · 2 lines
Thanking You
Neha Malcom Francis
#4 lore raw

Hi Neha,

Quoted 42 lines · Neha Malcom Francis

Hi Simon,

Quoted 39 lines · Simon Glass

Hi Neha,

Quoted 36 lines · Fabio Estevam

[Adding Alper - binmam maintainer and Oliver, who faced the same issue on imx8]

Quoted 32 lines · Neha Malcom Francis

Hi!

U-Boot build for J721E with binman enabled on the latest tip of the master branch throws an error when I try to use u-boot-spl-nodtb entry in my dtsi.

What I'm trying to do is, to show I've made a small example
(https://github.com/nehamalcom/u-boot/commit/f53dc83944f7774008afbb24fff42904862e9efe)
that is:

&binman {
         foo {
                 filename = "foo.bin";
                 u-boot-spl-nodtb {
                 };
         };
};

which throws the error
(https://gist.github.com/nehamalcom/4d855db7e4d5bd03aa29099b0e915e53):

binman: Section '/binman/foo': Symbol '_binman_u_boot_any_prop_image_pos' in entry '/binman/foo/u-boot-spl-nodtb': Entry 'u-boot-any' not found in list (u-boot-spl-nodtb,main-section)

This can be traced to the WriteSymbols() in etype/u_boot_spl_nodtb.py. On commenting out this function since it's not necessary in our use-case, the build was successful
(https://github.com/nehamalcom/u-boot/commit/5666721860e1d2f759440a00c4aee8b6e89b54b3)

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Quoted 2 lines

Why is binman not picking up on the "any" and choosing u-boot-spl-nodtb from the list?

You might need this patch?

https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/

Even after applying this patch, the entry is not working for me.

Probably because that patch doesn't deal with CONFIG_SPL case, only CONFIG_TPL and CONFIG_VPL? Can you please try to do the same for CONFIG_SPL?

e.g.

#ifdef CONFIG_SPL
binman_sym_declare(ulong, u_boot_spl, image_pos);
binman_sym_declare(ulong, u_boot_spl, size);
#endif

cheers,
-roger

#5 lore raw
Quoted 3 lines · Neha Malcom Francis
Quoted 3 lines · Simon Glass
Quoted 2 lines · Fabio Estevam
Quoted 1 line

[Adding Alper - binmam maintainer and Oliver, who faced the same issue on imx8]

(Sorry I've been unavailable here for longer than I hoped for. Still trying to get some other work into Debian before their freeze.)

Quoted 28 lines
Quoted 28 lines
Quoted 28 lines
Quoted 28 lines · Neha Malcom Francis
Quoted 27 lines

Hi!

U-Boot build for J721E with binman enabled on the latest tip of the master branch throws an error when I try to use u-boot-spl-nodtb entry in my dtsi.

What I'm trying to do is, to show I've made a small example
(https://github.com/nehamalcom/u-boot/commit/f53dc83944f7774008afbb24fff42904862e9efe)
that is:

&binman {
         foo {
                 filename = "foo.bin";
                 u-boot-spl-nodtb {
                 };
         };
};

which throws the error
(https://gist.github.com/nehamalcom/4d855db7e4d5bd03aa29099b0e915e53):

binman: Section '/binman/foo': Symbol '_binman_u_boot_any_prop_image_pos' in entry '/binman/foo/u-boot-spl-nodtb': Entry 'u-boot-any' not found in list (u-boot-spl-nodtb,main-section)

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

This can be traced to the WriteSymbols() in etype/u_boot_spl_nodtb.py. On commenting out this function since it's not necessary in our use-case, the build was successful
(https://github.com/nehamalcom/u-boot/commit/5666721860e1d2f759440a00c4aee8b6e89b54b3)

Why is binman not picking up on the "any" and choosing u-boot-spl-nodtb from the list?

Binman is trying to embed into the SPL the position/size of U-Boot (its next phase), but there's no U-Boot proper entry in the same binman image, so it can't. Try disabling CONFIG_SPL_BINMAN_UBOOT_SYMBOLS to stop writing these symbols since you said you don't need them, see [1][2] merged since v2022.04 or so.

You can try putting everything into a monolithic binman image, but that proved difficult to do for i.MX8M, so I added that config and disabled it there. Maybe it should be disabled by default.

[1] spl: binman: Split binman symbols support from enabling binman
https://lore.kernel.org/u-boot/[email protected]/

[2] spl: binman: Disable u_boot_any symbols for i.MX8M boards
https://lore.kernel.org/u-boot/[email protected]/

Quoted 9 lines
Quoted 6 lines
Quoted 4 lines

You might need this patch?

https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/

Even after applying this patch, the entry is not working for me.

Probably because that patch doesn't deal with CONFIG_SPL case, only CONFIG_TPL and CONFIG_VPL? Can you please try to do the same for CONFIG_SPL?

The "u-boot-any" ones are for SPL, and implicitly #ifdef CONFIG_SPL. Those #ifdefs are a bit underspecified, but 'work' in the sense that for any phase its next phase is declared.

Quoted 9 lines

e.g.

#ifdef CONFIG_SPL
binman_sym_declare(ulong, u_boot_spl, image_pos);
binman_sym_declare(ulong, u_boot_spl, size);
#endif

cheers,
-roger

#6 lore raw

Hi Roger, Alper,

Thank you for the help!

Quoted 56 lines · Alper Nebi Yasak
Quoted 3 lines · Neha Malcom Francis
Quoted 3 lines · Simon Glass
Quoted 2 lines · Fabio Estevam
Quoted 1 line

[Adding Alper - binmam maintainer and Oliver, who faced the same issue on imx8]

(Sorry I've been unavailable here for longer than I hoped for. Still trying to get some other work into Debian before their freeze.)

Quoted 28 lines
Quoted 28 lines
Quoted 28 lines
Quoted 28 lines · Neha Malcom Francis
Quoted 27 lines

Hi!

U-Boot build for J721E with binman enabled on the latest tip of the master branch throws an error when I try to use u-boot-spl-nodtb entry in my dtsi.

What I'm trying to do is, to show I've made a small example
(https://github.com/nehamalcom/u-boot/commit/f53dc83944f7774008afbb24fff42904862e9efe)
that is:

&binman {
         foo {
                 filename = "foo.bin";
                 u-boot-spl-nodtb {
                 };
         };
};

which throws the error
(https://gist.github.com/nehamalcom/4d855db7e4d5bd03aa29099b0e915e53):

binman: Section '/binman/foo': Symbol '_binman_u_boot_any_prop_image_pos'
     in entry '/binman/foo/u-boot-spl-nodtb': Entry 'u-boot-any' not
found in list (u-boot-spl-nodtb,main-section)

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

This can be traced to the WriteSymbols() in etype/u_boot_spl_nodtb.py. On commenting out this function since it's not necessary in our use-case, the build was successful
(https://github.com/nehamalcom/u-boot/commit/5666721860e1d2f759440a00c4aee8b6e89b54b3)

Why is binman not picking up on the "any" and choosing u-boot-spl-nodtb from the list?

Binman is trying to embed into the SPL the position/size of U-Boot (its next phase), but there's no U-Boot proper entry in the same binman image, so it can't. Try disabling CONFIG_SPL_BINMAN_UBOOT_SYMBOLS to stop writing these symbols since you said you don't need them, see [1][2] merged since v2022.04 or so.

You can try putting everything into a monolithic binman image, but that proved difficult to do for i.MX8M, so I added that config and disabled it there. Maybe it should be disabled by default.

Quoted 6 lines

[1] spl: binman: Split binman symbols support from enabling binman
https://lore.kernel.org/u-boot/[email protected]/

[2] spl: binman: Disable u_boot_any symbols for i.MX8M boards
https://lore.kernel.org/u-boot/[email protected]/

Yes disabling the CONFIG_SPL_BINMAN_UBOOT_SYMBOLS worked, thank you for explaining what it was trying to do. Yes, if the use-case is lower, I think it can be 'n' by default.

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines

You might need this patch?

https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

Even after applying this patch, the entry is not working for me.

Probably because that patch doesn't deal with CONFIG_SPL case, only CONFIG_TPL and CONFIG_VPL? Can you please try to do the same for CONFIG_SPL?

The "u-boot-any" ones are for SPL, and implicitly #ifdef CONFIG_SPL. Those #ifdefs are a bit underspecified, but 'work' in the sense that for any phase its next phase is declared.

Okay, got it.

Quoted 10 lines
Quoted 10 lines

e.g.

#ifdef CONFIG_SPL
binman_sym_declare(ulong, u_boot_spl, image_pos);
binman_sym_declare(ulong, u_boot_spl, size);
#endif

cheers,
-roger

Signature · 2 lines
Thanking You
Neha Malcom Francis