[coreboot] Kabylake unable to boot with post code 0x71 "SGX: pre-conditions not met"

[Jose Trujillo]

Dear All,
About the memory I just changed the dimm to address A0 and now coreboot is reporting correctly 1 dimm detected.

But still no luck on the 0x71 post code loop (looks it is in some kind of loop because is still responsive to power and reset buttons).
I don't know where this loop could be located (coreboot or FSP).
The description on the post_codes.h file shows the following:
....
/**
* \brief Initializing Chips
*
* Boot State Machine: bs_dev_init_chips()
*/
#define POST_BS_DEV_INIT_CHIPS               0x71
....

Any advice on this issue?
Attached is the serial dump with extra information.

Thank you
Jose Trujillo

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, 12 September 2018 16:12, Jose Trujillo <ce.autom at protonmail.com> wrote:

> To begin with the system didn't find memory attached...
> but there is memory attached, SPD address mismatch?   I will check.
> ....
> .......Timeout while sending command 0x0d to EC!
> recv_ec_data: 0xff
> recv_ec_data: 0xff
> SPD index 7
> No memory dimm at address A0
> No memory dimm at address A2
> No memory dimm at address A6
> ....
> 0 DIMMs found
> ....
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Wednesday, 12 September 2018 13:29, Jose Trujillo via coreboot <coreboot at coreboot.org> wrote:
>
>> Dear coreboot engineers:
>>
>> Right now I am stuck with a Kabylake system with the following message:
>> ....
>> CPU #1 initialized
>> apic_id: 0x06 done.
>> microcode: updated to revision 0x8d date=2018-01-21
>> CPU #3 initialized
>> bsp_do_flight_plan done after 220 msecs.
>> CPU: frequency set to 3600 MHz
>> Enabling SMIs.
>> Locking SMM.
>> VMX : param.enable = 0
>> VMX: pre-conditions not met
>> SGX: pre-conditions not met
>> VMX: pre-conditions not met
>> VMX: pre-conditions not met
>> SGX: pre-conditions not met
>> SGX: pre-conditions not met
>> VMX: pre-conditions not met
>> SGX: pre-conditions not met
>> POST: 0x71
>> ....
>>
>> May be some configuration is missing and I am trying to find this out myself but if someone of you can give a hint on how to resolve it I will be grateful.
>>
>> Attached is the full serial dump.
>>
>> Thank you,
>> Jose Trujillo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20180912/0934ec85/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Serial_dump_extra.txt
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20180912/0934ec85/attachment-0001.txt>