> -----邮件原件----- > 发件人: Tim Harvey <[email protected]> > 发送时间: 2025年1月1日 4:32 > 收件人: Alice Guo (OSS) <[email protected]>; Simon Glass > <[email protected]> > 抄送: Tom Rini <[email protected]>; Stefano Babic <[email protected]>; Fabio > Estevam <[email protected]>; dl-uboot-imx <[email protected]>; Lukasz > Majewski <[email protected]>; Sean Anderson <[email protected]>; Alper > Nebi Yasak <[email protected]>; [email protected]; > [email protected]; Alice Guo <[email protected]>; Ye Li <[email protected]>; > Peng Fan <[email protected]> > 主题: Re: [EXT] Re: [PATCH v2 16/17] imx95_evk: add i.MX95 19x19 EVK board > basic support > > Caution: This is an external email. Please take care when clicking links or > opening attachments. When in doubt, report the message using the 'Report this > email' button > > > On Mon, Dec 30, 2024 at 6:34 PM Alice Guo (OSS) <[email protected]> > wrote: > > > > > 主题: [EXT] Re: [PATCH v2 16/17] imx95_evk: add i.MX95 19x19 EVK board > > > basic support > > > > > > > I gave this series a go on top of 5cfbf8c364 origin/next on an EVK I > > > have here and I saw no u-boot proper output after the ATF. > > > > > > Here is what I saw on UART2: > > > U-Boot SPL 2025.01-rc5-00393-g9b292f7d347f (Dec 27 2024 - 16:12:20 > > > -0800) DDRMIX is powered UP Normal Boot Trying to boot from MMC2 > > > Primary set selected Load image from MMC/SD 0xdec00 > > > NOTICE: BL31: v2.10.0 (release):lf-6.6.52-2.2.0 > > > NOTICE: BL31: Built : 16:06:15, Dec 27 2024 > > > > > > U-Boot SPL 2025.01-rc5-00393-g9b292f7d347f (Dec 27 2024 - 16:12:20 > > > -0800) DDRMIX is powered UP Normal Boot Trying to boot from MMC2 > > > Primary set selected Load image from MMC/SD 0xdec00 > > > NOTICE: BL31: v2.10.0 (release):lf-6.6.52-2.2.0 > > > NOTICE: BL31: Built : 16:06:15, Dec 27 2024 ^^^ nothing after this > > > > > > Any thoughts on what is wrong here? > > > > > > Best Regards, > > > > > > Tim > > > > Hi Tim, > > > > I tried it on my MX95 and it works well, so I not sure what causes this > > issue on > your EVK. > > > > Hi Alice, > > I discovered what happened. The first make for uboot resulted in a binman > warning (which should be a failure but is not for some reason) and results in > an > image that doesn't contain uboot proper: > WARNING './u-boot.bin' not found, resulting binary may be not-functional > > Simon, do you know why this warning doesn't result in a make failure? > > Doing a second make works, so I think there is likely a binman dependency > issue > going on here. You can re-create the issue with a distclean as shown here: >
I reproduced this issue with make distclean, but not every time. I need time to check it. Best Regards, Alice Guo
