[coreboot] Kabylake unable to boot with post code 0x71

[Jose Trujillo]

Thank you Naresh,

I added the missing PCH device id following your advise, also enabled DEBUG_BOOT_STATE but I am still not able to get more information via serial debug about the exact location of the problem (but now I am certain is in the coreboot code not in FSP).

I suspect the code involved aound this issue is hardwaremain.c and device.c....

Only the first "boot" just after flash I notice that the ethernet and SATA LEDs blink for a fraction of a second then reboots.
After that, the following attempts to boot I don't see LED activity neither reboots, just halted in some kind of loop.

According to the serial dump the las printed text is "0x71" but my question is if the serial port gets broken still during "BS_DEV_INIT_CHIPS" or is already  doing "BS_DEV_ENUMERATE".

As Naresh pointed my PCH H chipset "Kabylake-H HM175" was not added to the list; I added it but may be is needed to do something else to make it work.
Or istill is misconfigured (attached my .config file for your review)... I someone has a similar system working and want to share its configuration files to compare them myself I will be grateful.

Jose Trujillo.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, 12 September 2018 19:33, Naresh G. Solanki <naresh.solanki.2011 at gmail.com> wrote:

> Hi
>
>>PCH: device id a152 (rev 31) is Unknown
>
> This indicates that LPCID 0xa152 is not added.
>
> The #define should be added in source path:
> https://review.coreboot.org/cgit/coreboot.git/tree/src/include/device/pci_ids.h#n2721
>
> https://review.coreboot.org/cgit/coreboot.git/tree/src/soc/intel/common/block/lpc/lpc.c#n131
>
> &
>
> https://review.coreboot.org/cgit/coreboot.git/tree/src/soc/intel/skylake/bootblock/report_platform.c#n73
>
> as well.
>
> Additionally you can enable config DEBUG_BOOT_STATE to understand where exactly its stuck.
>
> Regards,
>
> Naresh G. Solanki
>
> On Wed, Sep 12, 2018 at 9:24 PM Jose Trujillo via coreboot <coreboot at coreboot.org> wrote:
>
>> 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
>>
>> --
>> coreboot mailing list: coreboot at coreboot.org
>> https://mail.coreboot.org/mailman/listinfo/coreboot
>
> --
> Best regards,
> Naresh G. Solanki
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20180914/de9b3a58/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/octet-stream
Size: 28508 bytes
Desc: not available
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20180914/de9b3a58/attachment.obj>