Hi Hilbert, For what it's worth, I was able to boot Linux as the payload without any obvious problems. It might be good to try other payloads, or see if you can enable serial console earlier in u-boot to find exactly where it reboots.
Here is my CPUID and microcode info printed by coreboot during ramstage: microcode: sig=0x50664 pf=0x10 revision=0xf00000c CPUID: 00050664 Cores: 32 Stepping: Y0 Revision ID: 05 So it appears I am using the production CPU and microcode that Zoran suggested. To obtain this, I downloaded SRV_P_203.exe from Intel's website and converted M1050664_0F00000C.TXT into a C-style header that can be included by coreboot's build system. On Thu, Jan 4, 2018 at 3:19 AM, Hilbert Tu(杜睿哲_Pegatron) < hilbert...@pegatroncorp.com> wrote: > Hi Zoran, > > About this issue, I decide to follow David's suggestion to comment out the > SMBus clock gating and then it can continue booting until load my U-Boot > payload. But then it enters infinite reboot as previous attached log > "smbus_init_fail_max_dump2.txt". I am not sure if is a side effect or > just a new issue. Do you have any recommendation about the reboot? By the > way, we have our own BDX-DE board, not Camelback CRB. But just use similar > configuration. Thanks. > > -Hilbert > This e-mail and its attachment may contain information that is > confidential or privileged, and are solely for the use of the individual to > whom this e-mail is addressed. If you are not the intended recipient or > have received it accidentally, please immediately notify the sender by > reply e-mail and destroy all copies of this email and its attachment. > Please be advised that any unauthorized use, disclosure, distribution or > copying of this email or its attachment is strictly prohibited. > 本電子郵件及其附件可能含有機密或依法受特殊管制之資訊,僅供本電子郵件之受文者使用。台端如非本電子郵件之受文者或誤收本電子郵件, > 請立即回覆郵件通知寄件人,並銷毀本電子郵件之所有複本及附件。任何未經授權而使用、揭露、散佈或複製本電子郵件或其附件之行為,皆嚴格禁止。 >
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot