Intermittent failure on APL platform with message "HeciInitialize HECIMBAR 0XD3708000"
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
调研方向
从报告的启动日志消息和 Apollo Lake FSP Release Note 开始，尤其关注关于硬件和软件兼容性的第 8.0 章。将文档中记录的 Coreboot 支持情况与报告的 Slim Bootloader 构建进行比较，并调查受影响硬件上的复位行为。完成的标准是得出可复现的解释或确认存在受支持的配置。
由索引模型根据 Issue 内容生成。
描述
Hello,
We are experiencing significant manufacturing fallout (poor yield) on our custom design which is based on Apollo Lake (E3930). Some of the units boot-up quickly and reliably. Other units boot correctly immediately after power-up, but fail to boot on subsequent hardware or software resets.
We have adapted the Slim Bootloader BIOS to our product and built it with the Debug version of the FSP library MR6 ( i received this debug library from Intel rep).
When a unit fails to boot, it seems to pause at the following message in the boot log:
HeciInitialize HECIMBAR 0XD3708000
Occasionally, after the unit pauses at this message, it automatically reboots, proceeds past this message on its second attempt, and successfully loads the operating system. In other situations, the self-reboot does not succeed and the unit remains stuck, displaying the second copy of the message indefinitely.
I had the following questions to Intel rep:
- What is the FSP library trying to accomplish when it displays this message "HeciInitialize HECIMBAR 0XD3708000"?
- What hardware or software failures would prevent this boot step from succeeding?
- Why does the Apollo Lake processor (or FSP library) reboot itself when this step fails the first time?
- After a self-reboot, why would a second attempt at executing the same code succeed?
- Why would the FSP library stop self-reboot attempts? Does it count these attempts?
But Intel rep has come back to us saying that:
"According to Apollo Lake FSP Release Note, in chapter 8.0 "Hardware and Software Compatibility" stated that Coreboot is the supported bootloader. Besides that, based on IOTG Platform Boot Solution roadmap, Intel FSP with Slim Bootloader is not supporting Apollo Lake while Intel FSP with coreboot is supporting in Apollo Lake and you may refer to IOTG NDA 5Q Platform Roadmap for more details."
So, could someone please provide any leads on this issue?
Regards,
Mahesh.
- 主要语言
- C
- 星标
- 366
- 派生
- 143
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
intel/FSP 的其他 Issue
-
ArrowLakeS FSP: TmeEnable = 1 leaves TME inactive on Core Ultra 9 285K (single-key TME, no TME-MK)未关闭
难度 5/5 一周以上 新手友好度 24/100
-
难度 4/5 3-5 天 新手友好度 42/100
-
难度 4/5 3-5 天 新手友好度 42/100
-
难度 3/5 1-2 天 新手友好度 68/100
-
难度 5/5 一周以上 新手友好度 35/100
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
SPIDevice selects an active-high device as soon as it is created可能已有人在做 @mikeysklar 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 73/100
adafruit/circuitpython#11869 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
gnif/LookingGlass#1352 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
kovidgoyal/kitty#10862 ·
维护者通常 1 天内回复