[Fw_Os_Forum] UEFI with the Minnow Board Max

[Richardson, Brian]

MinnowBoard Max issues can be reported here - https://bugzilla.yoctoproject.org/ 

The platform appears to be hanging due to the absence of the graphics controller, which is a reasonable thing to fail on since MinnowBoard Max/Turbot all have integrated graphics and expect they won't suddenly disappear. You can use the source code available at http://firmware.intel.com/projects to build a version of the firmware without any graphics init.

If you have further questions, please refer to one of the MinnowBoard community forums for help ... http://wiki.minnowboard.org/Get_Involved 

Thanks ... br
---
Brian Richardson -- brian.richardson at intel.com -- Twitter: intel_brian


-----Original Message-----
From: fw_os_forum-bounces at mailman.uefi.org [mailto:fw_os_forum-bounces at mailman.uefi.org] On Behalf Of Marcus Walters
Sent: Tuesday, March 01, 2016 7:59 AM
To: fw_os_forum at mailman.uefi.org
Subject: [Fw_Os_Forum] UEFI with the Minnow Board Max

I'm playing around with the UEFI/Minnow Board Max combination. The Minnow Board comes with the Atom E3825. This CPU has an integrated graphics processor in it. Intel also makes the E3805 which is the same processor but without the integrated graphics processor.

I removed the E3825 and placed the E3805 on the Minnow Board. The UEFI bios hangs trying to communicate with the integrated graphics processor that doesn't exist. Intel specifically states that their part of the UEFI bios (their blobs) support the entire family of Atom 38xx processors. I'm beginning to doubt they tested this, as their code should recognize what processor it detects.


The bug in question seems to be located in their Legacy initialization code, but I can't be sure until I can get a look into their code.

Here is the debug output of the last couple of lines the bios prints before it hangs trying to initialize the 3805 processor:

Initializing Legacy Region
InstallProtocolInterface: 0FC9013A-0568-4BA9-9B7E-C9C390A6609B 7846C250 Initializing GT PowerManagement and other GT POST related GraphicsDxeInit - 1 GraphicsDxeInit - 2 GraphicsDxeInit - 3 GraphicsDxeInit - 4 GraphicsDxeInit - 5 GraphicsDxeInit - 6 GraphicsDxeInit - 7 GraphicsDxeInit - 8 GraphicsDxeInit - 9 GraphicsDxeInit - a Initializing PAVP GraphicsDxeInit - b Initializing GT PowerManagement Polling allow-wake bit Polling Render Force Wake Acknowledge Bit



Here is the debug output of the same couple of lines the bios prints initializing the 3825 processor:

Initializing Legacy Region
InstallProtocolInterface: 0FC9013A-0568-4BA9-9B7E-C9C390A6609B 7846C250 Initializing GT PowerManagement and other GT POST related GraphicsDxeInit - 1 GraphicsDxeInit - 2 GraphicsDxeInit - 3 GraphicsDxeInit - 4 GraphicsDxeInit - 5 GraphicsDxeInit - 6 GraphicsDxeInit - 7 GraphicsDxeInit - 8 GraphicsDxeInit - 9 GraphicsDxeInit - a Initializing PAVP GraphicsDxeInit - b Initializing GT PowerManagement Polling allow-wake bit Polling Render Force Wake Acknowledge Bit Polling Media ForceWakeReq Acknowledge Bit PcBase = 0x7EEFA000 GraphicsDxeInit - c GraphicsDxeInit - d GraphicsDxeInit - f


Note: I attached the full UEFI debug output for both processors


I tried talking to the Intel rep about the BIOS issue and they say they don't support the UEFI bios and directed me to here. If you guys don't have any idea about this issue, would you know who I can get in contact with about Intel side of the pre-compiled UEFI binaries?


Thanks,
Marcus