> -----邮件原件----- > 发件人: Tim Harvey <thar...@gateworks.com> > 发送时间: 2025年8月21日 8:52 > 收件人: Alice Guo (OSS) <alice....@oss.nxp.com> > 抄送: Tom Rini <tr...@konsulko.com>; Simon Glass <s...@chromium.org>; Alper > Nebi Yasak <alpernebiya...@gmail.com>; Stefano Babic > <sba...@nabladev.com>; Fabio Estevam <feste...@gmail.com>; dl-uboot-imx > <uboot-...@nxp.com>; Alice Guo <alice....@nxp.com>; Marek Vasut > <marek.va...@mailbox.org>; u-boot@lists.denx.de; Ye Li <ye...@nxp.com> > 主题: Re: [PATCH v3 0/2] Restore support for i.MX95 A0 silicon > > On Wed, Aug 20, 2025 at 4:05 AM Alice Guo (OSS) <alice....@oss.nxp.com> > wrote: > > > > Changes for v3: > > - update the binman etype to generate a configuration file and a .bin > > file > > - update Get ahab-container.img in imx95_evk.rst > > - rename configs/imx95.config to configs/imx95_evk.config > > > > Signed-off-by: Alice Guo <alice....@nxp.com> > > --- > > Alice Guo (2): > > binman: add a new entry type to support .bin file generation for the > i.MX95 platform > > imx95_evk: Restore support for i.MX95 A0 silicon > > > > Makefile | 3 +- > > arch/arm/dts/imx95-u-boot.dtsi | 44 +++++++-- > > arch/arm/mach-imx/Makefile | 5 + > > arch/arm/mach-imx/imx9/Kconfig | 5 +- > > arch/arm/mach-imx/imx9/scmi/container.cfg | 11 --- > > arch/arm/mach-imx/imx9/scmi/imximage.cfg | 16 ---- > > board/freescale/imx95_evk/MAINTAINERS | 1 + > > configs/imx95_19x19_evk_defconfig | 153 > > +----------------------------- > > configs/imx95_a0_19x19_evk_defconfig | 2 + > > configs/imx95_evk.config | 150 > +++++++++++++++++++++++++++++ > > doc/board/nxp/imx95_evk.rst | 42 +++++++- > > tools/binman/entries.rst | 12 +++ > > tools/binman/etype/nxp_imx9image.py | 85 +++++++++++++++++ > > 13 files changed, 338 insertions(+), 191 deletions(-) > > --- > > base-commit: 0c558bbad9e7581808b358091d1fd979f860e8ac > > change-id: 20250809-imx95-10b5b18e0ad7 > > > > Best regards, > > -- > > Alice Guo <alice....@oss.nxp.com> > > > > Hi Alice, > > I have a board with IMX95 A1 silicon - with respect to this documentation > should > that be considered A0 vs B0? Are there any issues with A1 that would make the > oei/sm/atf/uboot not compatible here? > > As far as I can tell the only part of boot firmware that needs compile-time > configuration based on silicon revision is the imx-oei and I only see special > handling for r=A0. If I build with anything other than r=A0 the OEI does not > run > for me whereas building with r=A0 the OEI's appear to run fine yet I don't > seem > to make it to U-Boot SPL. >
flash.bin for i.MX95 A1 can be generated in the same way as i.MX95 A0. Can sm run work well? oei-m33-tcm.bin is required for A1. Best Regards, Alice Guo