09:45 <javierm> NishanthMenon: hi, how can I build the u-boot images for am62xx? https://paste.centos.org/view/raw/3319ea6d

09:45 <javierm> NishanthMenon: I read https://www.mail-archive.com/u-boot@lists.denx.de/msg484448.html thread but still isn't clear to me

09:46 <javierm> tried cloning the ti-linux-firmware repo and export DM=$MY_PATH/ti-linux-firmware/ti-dm/am62xx/ipc_echo_testb_mcu1_0_release_strip.xer5f but that didn't help

09:53 <NishanthMenon> @javierm: https://github.com/nmenon/k3-upstream-boot-build

09:53 <NishanthMenon> It might be simpler to read the .config and make file?

09:55 <NishanthMenon> $(Q)$(MAKE) -C $(UBOOT_DIR) CROSS_COMPILE=$(CROSS_COMPILE_32) O=$(O)/u-boot/r5 BINMAN_INDIRS=$(FW_DIR)

09:55 <NishanthMenon> With binman, that is

09:56 <NishanthMenon> So if UBoot is tip of upstream master or TI uboot..

09:57 <NishanthMenon> https://u-boot.readthedocs.io/en/latest/board/ti/am62x_sk.html?highlight=Am62#build-procedure

10:08 <javierm> NishanthMenon: thanks for the pointers

10:08 <NishanthMenon> javierm: I hope it helps..

10:09 <javierm> NishanthMenon: yes, it will but I also want to package the needed bits in Fedora and that will be more tricky...

10:09 <NishanthMenon> javierm: gotcha. We had moved to binman to hopefully make things easier for standard distros

10:10 <javierm> NishanthMenon: I was talking more about the firmware that is in ti-linux-firmware but not yet in linux-firmware

10:10 <javierm> because shipping that I believe would be against the Fedora packaging guidelines, I'll need to check

10:11 <NishanthMenon> Aah. It was in the path of being upstreamed, but not sure why it stalled.

10:11 <NishanthMenon> Let me check

10:18 <javierm> NishanthMenon: btw, I tried to follow the doc in ./doc/board/ti/am62x_beagleplay.rst but that's not complete, so maybe should also mention that one need to set BL31 and TEE en vars ?

10:19 <NishanthMenon> Rst does includes. It is meant to make the rendered doc complete.

10:19 <javierm> and build the bl31.bin and tee-pager_v2.bin before, because that wasn't evident to me

10:20 <NishanthMenon> Tom wanted documentation generated that was accurate without duplication in rst.

10:21 <NishanthMenon> I thought we killed all references to tee-pager-v2

10:22 <NishanthMenon> javierm: I am confused a bit.

10:22 <NishanthMenon> I thought it did describe the build deps. Maybe I am missing something? We need to fix it..

10:24 <javierm> NishanthMenon: probably my bad because I opened that file using vim? What's a rst viewer I can use that would follow the included rst ?

10:27 <javierm> NishanthMenon: nvm, I just went to the gitlab repo for it to be rendered https://source.denx.de/u-boot/u-boot/-/blob/next/doc/board/ti/am62x_beagleplay.rst?ref_type=heads

10:27 <javierm> I just miss the simpler times when I could open a text file and see the commands to build the SPL and u-boot images (and didn't need ATF, OP-TEE, firmware, etc to build) :)

10:27 <NishanthMenon> Yeah, I know.

10:28 <NishanthMenon> Rst render in gitlab/hub still doesn't understand include semantics. It is sphinx render

10:29 <javierm> sigh, so even looking at the gitlab repo is not useful then

10:29 <vigneshr> Yeah, I ve been using published doc: https://u-boot.readthedocs.io/en/latest/board/ti/am62x_sk.html

10:30 <javierm> vigneshr: thanks, I was just going through each include manually (e.g: https://source.denx.de/u-boot/u-boot/-/blob/next/doc/board/ti/k3.rst?ref_type=heads)

10:40 <javierm> vigneshr, NishanthMenon: with the properly rendered rst that you shared I was able to build all the binaries, thanks!

10:41 <NishanthMenon> We need to see what we can do to improve

10:42 <NishanthMenon> javierm: glad you got past this. But I am wondering what we could probably do to help make it easier.

10:46 <javierm> NishanthMenon: I haven't contributed to u-boot in a decade, maybe folks nowadays know that need to generate docs with `make htmldocs` so it won't be an issue for them?

10:46 <javierm> I wrongly assumed that the ./doc/board/ti/am62x_beagleplay.rst would be self contained

10:47 <NishanthMenon> True

10:47 <javierm> sorry for my silly questions then and thanks again for the assistance :)

11:07 <NishanthMenon> javierm: thank you for highlighting. Need to think a bit more for a soln.