Hi,
the following mainboard Config.lb have not been refactored yet because they have not that much in common with other boards: asus/m2v-mx_se/Config.lb (512 kB XIP, different size calculation) technologic/ts5300/Config.lb (32 kB XIP) digitallogic/msm586seg/Config.lb (32 kB XIP) emulation/qemu-x86/Config.lb (32 kB XIP, no fallback) iei/juki-511p/Config.lb (64 kB XIP, no fallback)
To be honest, XIP size calculation seems pretty arbitrary to me. Some boards use 32 kB, some 64 kB, the majority uses 128 kB and one single board uses 512 kB.
AFAICS for ROMCC boards, making XIP larger than cache will result in cache misses, but won't corrupt anything. For CAR boards, having CAR+XIP exceed cache size will result in corruption. That means startup code should automatically calculate maximum XIP size. As a side benefit, calculating XIP stuff can be eliminated from these boards.
Can someone explain why the qemu-x86 and the IEI juki-511p targets do not have fallback options?
Regards, Carl-Daniel