Hi Neha, On 31/10/2022 05:40, Neha Malcom Francis wrote: > Hi Simon, > > On 30/10/22 07:13, Simon Glass wrote: >> Hi Neha, >> >> On Fri, 28 Oct 2022 at 04:58, Fabio Estevam <feste...@gmail.com> wrote: >>> >>> [Adding Alper - binmam maintainer and Oliver, who faced the same issue on >>> imx8] >>> >>> On Fri, Oct 28, 2022 at 7:56 AM Neha Malcom Francis <n-fran...@ti.com> >>> wrote: >>>> >>>> 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/20221021002320.1169603-5-...@chromium.org/ > > 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