On September 14, 2025 thus sayeth Aristo Chen: > Fix memory overlaps in FIT image configurations for TI AM62x and AM64x > PHYCore and SK boards. > > The overlaps occurred in two categories: > > 1. TI firmware stub images (tifsstub-hs, tifsstub-fs, tifsstub-gp): > These mutually exclusive firmware variants were incorrectly assigned > the same load address within FIT configurations, causing overlap > detection to fail. Adjust addresses with 64KB spacing: > - tifsstub-hs: Keep original address > - tifsstub-fs: Move to +64KB offset > - tifsstub-gp: Move to +128KB offset >
Yeah I can see how this looks like an oversight and I like the idea of checking for binaries that collide with each other however we're using the board_fit_image_post_process() function to load only one of these 'tifsstub' binaries which matches the security variant of the SoC at runtime[0]. Because we only load one of these they don't actually overlap. TBH I don't actually understand what is in these binaries which makes them so specific to each security variant or if we must load them to this specific address thanks to some IPC stuff between our vendor firmware. I'll ask around. But I don't think we can move these 'tifsstub' binaries this easily. ~Bryan [0] https://elixir.bootlin.com/u-boot/v2025.07/source/arch/arm/mach-k3/r5/common.c#L326
