-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apollo Lake MR9 FSP will set SMI Lock no matter what value I passed from bootloader #69
Comments
Hi @seattlezhu, Thank you for reporting this to us. Thank you. |
Hi @seattlezhu, Is there any update on the request above? It'll be great if you could clarify more so that we can proceed to debug this issue. Thank you. |
Hi @nuramir1 , Sorry for the late reply . Thank you. |
Hi @seattlezhu, Noted that this issue is being tracked and I will get back to you soon if there is any update on this issue. Thank you. |
Hi @seattlezhu , Can you share your debug log for the failing system? We would like to check on the SMI Lock debug print. Have you tried with previous MR6 FSP whether the issue is happening or not? Thank you, |
Hi @nuramir1 , I have tried with MR6 FSP and result to the same. The debug log is pretty easy just print the value of SMI Lock register at dirfferent InitPhase in Stage2 BoardInit function if you use Slimboot as the host bootloader. Thank you. |
Hi @seattlezhu, Sorry for the late reply as we're working on the latest FSP releases. Thank you, |
Hi,
I found no matter what value of LockDownGlobalSmi I passed form bootload, FSP would set SMI Lock after Notify EnumInitPhaseReadyToBoot. Is this a problem or out of some particular design? How would I supposed to clear SMI Lock?
Thanks!
The text was updated successfully, but these errors were encountered: