On Thu, Oct 30, 2025 at 12:31:50AM +0000, Peng Fan wrote: > > Subject: Re: [PATCH v3 00/12] remoteproc: Add support for > > i.MX8M[M/N/P/Q] and i.MX93 > > > > Hi Fabio, > > > > On Sun, Oct 26, 2025 at 08:28:50AM -0300, Fabio Estevam wrote: > > >Hi Peng, > > > > > >On Tue, Oct 21, 2025 at 9:48 PM Peng Fan <[email protected]> > > wrote: > > >> > > >> CI: https://dev.azure.com/pengfan/uboot- > > ci/_build/results?buildId=21 > > >> > > >> This patch series introduces remoteproc support for NXP i.MX8M > > and > > >> i.MX93 platforms. Most of the i.MX-specific logic is ported from the > > >> Linux kernel to ensure compatibility and maintainability. > > > > > >I'm getting the following ut_dm_dm_test_remoteproc_elf error in > > Gitlab CI: > > > > > >https://source.denx.de/u-boot/custodians/u-boot-imx/- > > /jobs/1274168#L276 > > > > Not sure why it fails, my azure CI pass. > > I build this with sandbox64_defconfig using my local PC and run ./u- > > boot -d arch/sandbox/dts/sandbox64.dtb With command: ut dm > > dm_test_remoteproc_elf I not see failures. > > > > Let me rebase to latest master, push to CI and retest. > > Still no clue why sandbox amd64 pass, but sandbox arm64 clang fail. > > More and more I am thinking this might be compiler or else caused > the issue. > > I am not sure how to run the arm64 sandbox clang test at my local, > I built sandox64 with aarch64 gcc and ran it on i.MX8MP-EVK, no > issue.
How about with aarch64 clang on that device? I would hope you could grab the official aarch64 binaries, but as a worst case, building an image with OpenEmbedded that includes llvm, etc, should suffice. -- Tom
signature.asc
Description: PGP signature
