My DEBUG print samples:
DEBUG ((EFI_D_INFO, "SUPPORTED!\n"));
or
if (EFI_ERROR (Status)) {
DEBUG((EFI_D_ERROR,"Install BLOCK_IO protocol error - %x\n",Status));
goto ON_ERROR;
}
Using Print() function in driver causes boot process freezing.
06.03.2014, 17:38, "Andrew Fish" <[email protected]>:
> On Mar 6, 2014, at 3:27 AM, Onipchuk Vladimir <[email protected]> wrote:
>> Neeraj,
>>
>> oh no, I mean checking on the non-problematic platform (DG41TX in my case).
>> On the problematic platform, I can't even print debug message at the start
>> of my code. So I think, my driver not executing at the platform
>> initialization stage.
> How are you routing your DEBUG prints, or are you using Print()?
>
> If you are using DEBUG() you need to look out for how you implement it.
>
> These require the console to be connected, which can happen after your
> driver is loaded, or maybe StdErr is not set.
>
> https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdePkg/Library/UefiDebugLibConOut/
>
> https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdePkg/Library/UefiDebugLibStdErr/
>
> This is not UEFI spec, or even PI spec it is the old Intel Framework, so it
> might not exist everywhere.
>
> https://svn.code.sf.net/p/edk2/code/trunk/edk2/IntelFrameworkModulePkg/Library/PeiDxeDebugLibReportStatusCode/
>
> Thanks,
>
> Andrew Fish
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
