The cause of a 2^32 file can be that gcc has been upgraded and is generating new section names that are not covered in our ldscripts. I fixed this problem recently in another context. The new sections will get linked at address 0.
I think your accidental 0 idea is correct. Can you do a readelf on the various coreboot files and look for a section name that is not in the ldscripts? ron -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
