On 24.08.2021 11:45, Naresh G. Solanki wrote:
I remember working on an issue related to "FSP asserts on IOM ready check" I guess on ICL RVP It got fixed for me after making sure proper IOM binary was added using the fit tool.
I'm sure your setup is able to boot with vendor provided bios. Then other option is that you can extract iom.bin from a working bios & pack it into your generated coreboot fw. Then give it a try.
I couldn't get the IOM working despite preserving the ME region during flash updates. So literalyl I have been using the same IOM binary as shipped. Using the same IOM binary doesn't guarantee the correct operation of the TCSS and ends up in assert. Why? Because for some reason an engineering sample PCH have been forcing the ME into disabled state. No command could get ME out of this state which is probably the reason why IOM was not working correctly as well (ME didn't load the firmware?) or the FSP was not compatible with pre-production silicon.
Regards, Naresh Solanki
On Tue, Aug 24, 2021 at 2:39 PM Samek, Jan <email@example.com mailto:firstname.lastname@example.org> wrote:
Hello again Michal, I'd like to additionally ask you about a small detail regarding to the issue: What was the stepping that started to work? I'm currently encountering this behavior on B-0. I really did have some really bad memory init errors on A-0 which was considered an engineering sample and swapping for B-0 solved it. Nevertheless, this MCE issue still persists on B-0 in my case. Thanks for info. Regards, Jan Samek Siemens, s.r.o. ADV D EU CZ AE AC 7 email@example.com <mailto:firstname.lastname@example.org> _______________________________________________ coreboot mailing list -- email@example.com <mailto:firstname.lastname@example.org> To unsubscribe send an email to email@example.com <mailto:firstname.lastname@example.org>
-- Best regards, Naresh G. Solanki
coreboot mailing list -- email@example.com To unsubscribe send an email to firstname.lastname@example.org