Issue #511 has been updated by Elias Souza.
Matt DeVillier wrote in #note-3:
Elias Souza wrote in #note-2:
Matt DeVillier wrote in #note-1:
was this combination previously working with the 4.20 tag?
Sadly no, it's not working in the 4.20, the first try is from 8 months past and continues to can't boot, just work if SMMSTOREv2 driver is not enabled and just SMMSTOREv1 is used.
have you tried just disabling SMMSTORE on the edk2 side? You can do that by removing the param passed to edk2 via the extra build params Kconfig.
Sounds like this will need to be debugged on a board with serial output to see what's breaking in edk2
Oh thanks i will try to remove -DSMMSTORE from edk2 build and post the result here, the most problem are that i don't have a specific hardware debugger for UART debugging, In my country this is so hard to find
---------------------------------------- Bug #511: [STM/PE][BUG][SMMSTORE] Coreboot doesn't boot if SMMSTOREv2 driver Kconfig option is enabled https://ticket.coreboot.org/issues/511#change-1672
* Author: Elias Souza * Status: Needs Testing * Priority: High * Category: coreboot common code * Target version: 4.21 * Start date: 2023-10-09 * Affected hardware: is necessary testing in newest hardwares include Haswell and Kaby Lake, but idk if affect other platforms different than Sandybridge * Affected OS: All ---------------------------------------- For some reason the SMMSTOREv2 looks to break SMMSTORE support in STM/PE during boot.
Coreboot: 4.21 HARDWARE: Gigabyte H61M-DS2 with Ivybridge processor Payload: EDK2 SMMSTORE: SMMSTOREv2
A example with other guy using https://www.reddit.com/r/coreboot/comments/10rakni/comment/k444jz1/?context=...
* According with the reddit user crazyfox-ua " The same for me on T440p & X230t (both with edk2) - just blank screen. Disabled STM brings both laptops back to life. CB logs says nothing strange IMO (last record is "[DEBUG] Jumping to boot code at <hex here>".
Is necessary to test if others payloads is affected by this bug