Andrew –

Thanks!

At this point, I’m not sure of anything…  not the least of which is the 
DebugLib.
Continuing to experiment, I did find that if I compile the PEI driver for IA32 
(as opposed to X64), then at least it doesn’t brick the BIOS. Doesn’t mean that 
my code is running since I’m not getting any output but small steps work as 
well. [Very thankful this is still a socketed BIOS chip and not surface mounted 
yet…]

I have some folks helping to get some answers about a number of different 
questions from the BIOS development team so maybe I’ll get hooked up with the 
correct person.
I posted because it just seems like there’s a void when it comes to finding 
information on PEI drivers in general (as opposed to DXE drivers for example).

-Joe Thomas

// Joseph Thomas
// Principal Software Engineer
// Dot Hill Systems
// 2905 NorthWest Blvd., Suite 20
// Plymouth, MN 55441
// 763.226.2640

From: Andrew Fish [mailto:af...@apple.com]
Sent: Monday, December 01, 2014 1:50 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] PEI driver help


On Dec 1, 2014, at 8:48 AM, Joe Thomas 
<joe.tho...@dothill.com<mailto:joe.tho...@dothill.com>> wrote:

Folks,

I’m trying to convert/port one of our DXE drivers to PEI (for Recovery support) 
but I’m having trouble finding useful information on generating a PEIM module 
that can be integrated into a BIOS.

Does anyone have any good pointers/info that might help point the way? Thanks.


Background:
-          DXE module being built under Edk_1.xx
-          Final output is .DXE or .DXE.ORG<http://dxe.org/> file (as well as 
the .efi)

-          BIOS is MMTOOL compatible

-          Building PEI module w/Edk2
-          Output from ‘build’ process is <name>.debug, <name>.dll or 
<name>.efi; none are in proper format for use by MMTOOL

Current (test) PEI module is a simple DEBUG() statement and return 
EFI_UNSUPPORTED for PeimEntry(). [Using MdeModulePkg/Bus/Pci/IdeBusPei/* as 
template files.] MMTOOL seems to like output by GenFfs… GenFfs want’s something 
with a PE or TE section such as GenSec outputs. Putting the resulting output 
into the BIOS bricks the system… Don’t have a debugger that will tell me what’s 
happening (hence trying to start with something that will output a debug 
message and exit…)


You can try running VolInfo on the FV that contains your PEIM to see how it got 
packaged up.

The DebugLib can have different underlying implementations. Are you sure you 
are using a DebugLib instance that is compatible with the platform?

Thanks,

Andrew Fish


Thanks again…

// Joseph Thomas
// Principal Software Engineer
// Dot Hill Systems
// 2905 NorthWest Blvd., Suite 20
// Plymouth, MN 55441
// 763.226.2640

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Reply via email to