EDK II

RD,

Is the USB port that the mouse is plugged into a UEFI 2.0 only root port?  Since the USB Mouse is likely USB 1.1, you may need to put a USB Hub between the root port and the USB mouse to get USB 1.1 devices to work correctly.

The only other thing to verify is if you have all the USB drivers installed.

Thanks,

Mike

-----Original Message-----
From: Ramya Desai [mailto:ramya.desai@...]
Sent: Thursday, May 27, 2010 4:49 AM
To: edk2-devel@...
Subject: [edk2] Mouse problem with USB2.0 port (EDK-II)

Dear Experts,

When I connected the USB mouse to USB2.0 Ehci port, it is not getting
enumerated. When I move the mouse, I didn't see any data transfers and
NAK transactions from mouse to PC. I opened edit application from
shell prompt.
I am using edk2-1.6.8 DUET over IA23 machine.
Here I am attaching the analyzer log file with this mail.

Please let me know, if I need to do any thing additional to make mouse work.

Regards,
RD

Thomas:
  EdkCompatibilityPkg\Foundation is for EDK style code, other EDKII packages such as MdePkg and MdeModulePkg are for EDKII style code. They can't be mixed used, because they are two different code base separately for UEFI2.0/Framework0.9 EDK code and UEFI2.3/PI1.2 EDKII code.

  Your mentioned PPI PEI_BASE_MEMORY_TEST_GUID is a implemented related PPI that is not defined in any UEFI/PI/Framework specification. It has been removed from EDKII Packages because no real case uses it.

Thanks
Liming
-----Original Message-----
From: Thomas Jourdan [mailto:tjourdan@...] 
Sent: Thursday, May 27, 2010 10:43 PM
To: edk2-devel@...
Subject: [edk2] How to use EdkCompatibilityPkg PPI in EDK2 ?

Hi

For my firmware I'm writing a PEIM module in EDK2 which implements and
installs PPIs defined in EdkCompatibilityPkg (for example
PEI_BASE_MEMORY_TEST_GUID in my case).

I don't understand how I can include the GUID and PPI definition (defined in
EdkCompatibilityPkg/Foundation/Ppi/BaseMemoryTest.h) in the inf file or the
source code of my module. I always end up with definition type conflicts, or
warnings (due to EFI_FORWARD_DECLARATION for example).

What is the correct method in EDK2 for using EdkCompatibilityPkg PPI /
GUIDs... ?

Regards,
Thomas


------------------------------------------------------------------------------

_______________________________________________
edk2-devel mailing list
edk2-devel@...
https://lists.sourceforge.net/lists/listinfo/edk2-devel

0x0000000D is a General Protection fault. This is usually caused by running non code or doing a read/write to an address range that does not exist.

The code was running at 0x3f0fa028. What address did your driver load at? You can subtract EIP from the load address of the driver to get the offset in the executable. You can add /FAcs to the compile line to generate .cod files that will contain mixed C/assembly with file offsets included.

Sent from my iPad

On May 26, 2010, at 7:44 AM, Ramya Desai <ramya.desai@...> wrote:

> Dear Experts,
> 
> When I port my USB Host driver code from EDK-II to EDK1.04, I am
> getting the system crash. The same code is working fine in EDK-II.
> I captured the crash log. Please find it bellow. Can any one help me
> how to analyze this log or what this log means.
> 
> Thanks in advance,
> RD
> 
> [22;11H[0m[37m[40m
> !!!! IA32 Exception Type - 0000000D !!!!
> EIP - 3F0FA028, CS - 00000010, EFLAGS - 00010286
> ExceptionData - 00000000
> EAX - FFFFFFA3, ECX - 5D8903B3, EDX - 80000000, EBX - 00000000
> ESP - 3F53BA70, EBP - 3F53BA8C, ESI - FFFFFFFF, EDI - FFFFFFA3
> DS - 00000008, ES - 00000008, FS - 00000008, GS - 00000008, SS - 00000008
> GDTR - 954C003F 3F533F16, IDTR - 959203C7 00003F16
> LDTR - 00000000, TR - 00000000
> CR0 - 00000013, CR2 - 00000000, CR3 - 00000000, CR4 - 00000208
> DR0 - 00000000, DR1 - 00000000, DR2 - 00000000, DR3 - 00000000
> DR6 - FFFF0FF0, DR7 - 00000400
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel

Actually, the driver is getting loaded properly and everything seems
to work fine. But, when a type a non shell command, at the command
prompt and press enter, then this exception is raised. Not quite sure,
how to proceed

On Wed, May 26, 2010 at 8:52 PM, Andrew Fish <afish@...> wrote:
> 0x0000000D is a General Protection fault. This is usually caused by running non code or doing a read/write to an address range that does not exist.
>
> The code was running at 0x3f0fa028. What address did your driver load at? You can subtract EIP from the load address of the driver to get the offset in the executable. You can add /FAcs to the compile line to generate .cod files that will contain mixed C/assembly with file offsets included.
>
> Sent from my iPad
>
> On May 26, 2010, at 7:44 AM, Ramya Desai <ramya.desai@...> wrote:
>
>> Dear Experts,
>>
>> When I port my USB Host driver code from EDK-II to EDK1.04, I am
>> getting the system crash. The same code is working fine in EDK-II.
>> I captured the crash log. Please find it bellow. Can any one help me
>> how to analyze this log or what this log means.
>>
>> Thanks in advance,
>> RD
>>
>> [22;11H[0m[37m[40m
>> !!!! IA32 Exception Type - 0000000D !!!!
>> EIP - 3F0FA028, CS - 00000010, EFLAGS - 00010286
>> ExceptionData - 00000000
>> EAX - FFFFFFA3, ECX - 5D8903B3, EDX - 80000000, EBX - 00000000
>> ESP - 3F53BA70, EBP - 3F53BA8C, ESI - FFFFFFFF, EDI - FFFFFFA3
>> DS - 00000008, ES - 00000008, FS - 00000008, GS - 00000008, SS - 00000008
>> GDTR - 954C003F 3F533F16, IDTR - 959203C7 00003F16
>> LDTR - 00000000, TR - 00000000
>> CR0 - 00000013, CR2 - 00000000, CR3 - 00000000, CR4 - 00000208
>> DR0 - 00000000, DR1 - 00000000, DR2 - 00000000, DR3 - 00000000
>> DR6 - FFFF0FF0, DR7 - 00000400
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@...
>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>

Hi,
  Do you load the non shell command from usb disk? Only the specific cmd has this issue or all applications in usb disk have?
  Another question to confirm is: are you successful to read/write a file from/into usb disk?
  
Thanks
Tian Feng
-----Original Message-----
From: aditya uttam [mailto:uttam.aditya@...] 
Sent: 2010年5月27日 2:24
To: edk2-devel@...
Subject: Re: [edk2] EDK crash

Actually, the driver is getting loaded properly and everything seems
to work fine. But, when a type a non shell command, at the command
prompt and press enter, then this exception is raised. Not quite sure,
how to proceed

On Wed, May 26, 2010 at 8:52 PM, Andrew Fish <afish@...> wrote:
> 0x0000000D is a General Protection fault. This is usually caused by running non code or doing a read/write to an address range that does not exist.
>
> The code was running at 0x3f0fa028. What address did your driver load at? You can subtract EIP from the load address of the driver to get the offset in the executable. You can add /FAcs to the compile line to generate .cod files that will contain mixed C/assembly with file offsets included.
>
> Sent from my iPad
>
> On May 26, 2010, at 7:44 AM, Ramya Desai <ramya.desai@...> wrote:
>
>> Dear Experts,
>>
>> When I port my USB Host driver code from EDK-II to EDK1.04, I am
>> getting the system crash. The same code is working fine in EDK-II.
>> I captured the crash log. Please find it bellow. Can any one help me
>> how to analyze this log or what this log means.
>>
>> Thanks in advance,
>> RD
>>
>> [22;11H[0m[37m[40m
>> !!!! IA32 Exception Type - 0000000D !!!!
>> EIP - 3F0FA028, CS - 00000010, EFLAGS - 00010286
>> ExceptionData - 00000000
>> EAX - FFFFFFA3, ECX - 5D8903B3, EDX - 80000000, EBX - 00000000
>> ESP - 3F53BA70, EBP - 3F53BA8C, ESI - FFFFFFFF, EDI - FFFFFFA3
>> DS - 00000008, ES - 00000008, FS - 00000008, GS - 00000008, SS - 00000008
>> GDTR - 954C003F 3F533F16, IDTR - 959203C7 00003F16
>> LDTR - 00000000, TR - 00000000
>> CR0 - 00000013, CR2 - 00000000, CR3 - 00000000, CR4 - 00000208
>> DR0 - 00000000, DR1 - 00000000, DR2 - 00000000, DR3 - 00000000
>> DR6 - FFFF0FF0, DR7 - 00000400
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@...
>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>

------------------------------------------------------------------------------

_______________________________________________
edk2-devel mailing list
edk2-devel@...
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Jason,

I would suspect the gEfiSmmAccess2ProtocolGuid, gEfiSmmControl2ProtocolGuid, and gEfiSmmConfigurationProtocolGuid  protocols you must of had to construct for the NT32 environment. There may be a few protocols I'm missing as there are a lot in the PI SMM area. 

You can Turn up the debug prints for the SmmCore by doing something like this in the Nt32Pkg/Nt32Pkg.dsc file

  MdeModulePkg/CorePiSmmCore.inf {
    <PcdsFixedAtBuild>
      gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel|0x800fffff
  }

Maybe some one, like Mike Kinney, could state if there is anything in the code that would make it impossible to port to NT32. But it seems like all CPU specifics of SMM should abstracted via the protocols and it would be possible to build a fake set for NT32? 

Andrew Fish

NCSU BSCE 87


On May 25, 2010, at 10:23 AM, Jason Gionta wrote:

> Hello,
> 
> Is it possible to integrate SMM_CORE and SMM IPL in the NT32 emulation ENV?
> 
> I seem to be getting memory reference issues when accessing the number of free pages in PiSmmCore/Page.c.  I just wanted to make sure is it even possible to emulate the SMM Core in the NT32 dev environment before running down the fox hole of trying to troubleshoot the issue.  I am using unmodified SMM code from the EDKII.
> 
> Thanks in advance,
> 
> -- 
> Jason Gionta
> Cyber Defense Lab
> North Carolina State University
> jjgionta@...
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel

Siva,

Yes.  DUET is supported in EDK II.

NT32 is for IA32 only.  It does not support X64 so you will not be able to test your X64 driver under NT32.

Best regards,

Mike


________________________________
From: Sivakumar Subramani [mailto:Sivakumar.Subramani@...]
Sent: Wednesday, May 19, 2010 2:57 AM
To: edk2-devel@...
Cc: Leonid Grossman
Subject: [edk2] DUET platfrom support

Hi,

I was using DUET platform support in EDK framework for build my driver. Now I am planning to migrate to EDK11. Is it supported in EDK 11 as well.

Will I be able to test X64 drivers under NT32 simulation environment? If so, Is there any document that explains me the steps to build a new driver for X64 to test it under NT32 simulation environment.

Thanks,
~Siva

Andrew,	

I suspect this should be related to the $(WORKSPACE)/Conf/.cache
Could you please remove that directory and try rebuilding NT32 platform?

Thanks & Best regards,
Huang, Qing 

-----Original Message-----
From: Andrew Fish [mailto:afish@...] 
Sent: Wednesday, May 19, 2010 3:29 AM
To: edk2-devel@...
Subject: [edk2] I've been seeing build crashes after the tools update last night?

Any one have an idea on whats going on? My Cygwin an OS X builds still work. Is it some issue with how the Python was frozen? 

C:\work\Edk2TOT>build -t VS2003
12:00:43, May.18 2010 [Windows-XP-5.1.2600]

WORKSPACE                = c:\work\edk2tot
ECP_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
EDK_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
EFI_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
EDK_TOOLS_PATH           = c:\work\edk2tot\basetools

TARGET_ARCH              = IA32
TARGET                   = DEBUG
TOOL_CHAIN_TAG           = VS2003

Active Platform          = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.dsc
Flash Image Definition   = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.fdf

Processing meta-data .


build...
 : error C0DE: Unknown fatal error when processing [c:\work\edk2tot\Nt32Pkg\Nt32
Pkg.dsc]

(Please send email to edk2-buildtools-devel@... for help, atta
ching following call stack trace!)

(Python 2.5.2 on win32) Traceback (most recent call last):
  File "build.py", line 1861, in Main
  File "build.py", line 1627, in Launch
  File "build.py", line 1462, in _MultiThreadBuildPlatform
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
ine 82, in __new__
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
ine 176, in _Init
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
abase.py", line 2083, in __getitem__
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
abase.py", line 2325, in __getitem__
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\MetaDataTabl
e.py", line 65, in Create
OperationalError: unable to open database file


- Failed -
12:00:45, May.18 2010 [00:02]
Andrew Fish






------------------------------------------------------------------------------

_______________________________________________
edk2-devel mailing list
edk2-devel@...
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Yes that was my first thought too, but it did not help?

Andrew Fish





On May 18, 2010, at 6:35 PM, Huang, Qing wrote:

> Andrew,	
> 
> I suspect this should be related to the $(WORKSPACE)/Conf/.cache
> Could you please remove that directory and try rebuilding NT32 platform?
> 
> Thanks & Best regards,
> Huang, Qing 
> 
> -----Original Message-----
> From: Andrew Fish [mailto:afish@...] 
> Sent: Wednesday, May 19, 2010 3:29 AM
> To: edk2-devel@...
> Subject: [edk2] I've been seeing build crashes after the tools update last night?
> 
> Any one have an idea on whats going on? My Cygwin an OS X builds still work. Is it some issue with how the Python was frozen? 
> 
> C:\work\Edk2TOT>build -t VS2003
> 12:00:43, May.18 2010 [Windows-XP-5.1.2600]
> 
> WORKSPACE                = c:\work\edk2tot
> ECP_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
> EDK_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
> EFI_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
> EDK_TOOLS_PATH           = c:\work\edk2tot\basetools
> 
> TARGET_ARCH              = IA32
> TARGET                   = DEBUG
> TOOL_CHAIN_TAG           = VS2003
> 
> Active Platform          = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.dsc
> Flash Image Definition   = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.fdf
> 
> Processing meta-data .
> 
> 
> build...
> : error C0DE: Unknown fatal error when processing [c:\work\edk2tot\Nt32Pkg\Nt32
> Pkg.dsc]
> 
> (Please send email to edk2-buildtools-devel@... for help, atta
> ching following call stack trace!)
> 
> (Python 2.5.2 on win32) Traceback (most recent call last):
>  File "build.py", line 1861, in Main
>  File "build.py", line 1627, in Launch
>  File "build.py", line 1462, in _MultiThreadBuildPlatform
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
> ine 82, in __new__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
> ine 176, in _Init
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
> abase.py", line 2083, in __getitem__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
> abase.py", line 2325, in __getitem__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\MetaDataTabl
> e.py", line 65, in Create
> OperationalError: unable to open database file
> 
> 
> - Failed -
> 12:00:45, May.18 2010 [00:02]
> Andrew Fish
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel

I pulled a clean tree and got the same error.

C:\work\edk2test>build -t VS2003
19:17:58, May.18 2010 [Windows-XP-5.1.2600]

WORKSPACE                = c:\work\edk2test
ECP_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
EDK_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
EFI_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
EDK_TOOLS_PATH           = c:\work\edk2test\basetools

TARGET_ARCH              = IA32
TARGET                   = DEBUG
TOOL_CHAIN_TAG           = VS2003

Active Platform          = c:\work\edk2test\Nt32Pkg\Nt32Pkg.dsc
Flash Image Definition   = c:\work\edk2test\Nt32Pkg\Nt32Pkg.fdf

Processing meta-data .


build...
 : error C0DE: Unknown fatal error when processing [c:\work\edk2test\Nt32Pkg\Nt3
2Pkg.dsc]

(Please send email to edk2-buildtools-devel@... for help, atta
ching following call stack trace!)

(Python 2.5.2 on win32) Traceback (most recent call last):
  File "build.py", line 1861, in Main
  File "build.py", line 1627, in Launch
  File "build.py", line 1462, in _MultiThreadBuildPlatform
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
ine 82, in __new__
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
ine 176, in _Init
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
abase.py", line 2083, in __getitem__
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
abase.py", line 2325, in __getitem__
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\MetaDataTabl
e.py", line 65, in Create
OperationalError: unable to open database file


- Failed -
19:17:59, May.18 2010 [00:02]


Andrew Fish





On May 18, 2010, at 6:35 PM, Huang, Qing wrote:

> Andrew,	
> 
> I suspect this should be related to the $(WORKSPACE)/Conf/.cache
> Could you please remove that directory and try rebuilding NT32 platform?
> 
> Thanks & Best regards,
> Huang, Qing 
> 
> -----Original Message-----
> From: Andrew Fish [mailto:afish@...] 
> Sent: Wednesday, May 19, 2010 3:29 AM
> To: edk2-devel@...
> Subject: [edk2] I've been seeing build crashes after the tools update last night?
> 
> Any one have an idea on whats going on? My Cygwin an OS X builds still work. Is it some issue with how the Python was frozen? 
> 
> C:\work\Edk2TOT>build -t VS2003
> 12:00:43, May.18 2010 [Windows-XP-5.1.2600]
> 
> WORKSPACE                = c:\work\edk2tot
> ECP_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
> EDK_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
> EFI_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
> EDK_TOOLS_PATH           = c:\work\edk2tot\basetools
> 
> TARGET_ARCH              = IA32
> TARGET                   = DEBUG
> TOOL_CHAIN_TAG           = VS2003
> 
> Active Platform          = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.dsc
> Flash Image Definition   = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.fdf
> 
> Processing meta-data .
> 
> 
> build...
> : error C0DE: Unknown fatal error when processing [c:\work\edk2tot\Nt32Pkg\Nt32
> Pkg.dsc]
> 
> (Please send email to edk2-buildtools-devel@... for help, atta
> ching following call stack trace!)
> 
> (Python 2.5.2 on win32) Traceback (most recent call last):
>  File "build.py", line 1861, in Main
>  File "build.py", line 1627, in Launch
>  File "build.py", line 1462, in _MultiThreadBuildPlatform
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
> ine 82, in __new__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
> ine 176, in _Init
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
> abase.py", line 2083, in __getitem__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
> abase.py", line 2325, in __getitem__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\MetaDataTabl
> e.py", line 65, in Create
> OperationalError: unable to open database file
> 
> 
> - Failed -
> 12:00:45, May.18 2010 [00:02]
> Andrew Fish
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel

Andrew,

We have tried to reproduce the issue on our development machine. Unfortunately, we still cannot reproduce the issue on a brand clean tree.
Looks like this is a regression issue on your machine. Could you please let us know the last working build.exe SVN revision that works fine on your machine? Maybe this will give us some clue for source code?

Thanks & Best regards,
Huang, Qing

-----Original Message-----
From: Andrew Fish [mailto:afish@...] 
Sent: Wednesday, May 19, 2010 10:20 AM
To: edk2-devel@...
Subject: Re: [edk2] I've been seeing build crashes after the tools update last night?

I pulled a clean tree and got the same error.

C:\work\edk2test>build -t VS2003
19:17:58, May.18 2010 [Windows-XP-5.1.2600]

WORKSPACE                = c:\work\edk2test
ECP_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
EDK_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
EFI_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
EDK_TOOLS_PATH           = c:\work\edk2test\basetools

TARGET_ARCH              = IA32
TARGET                   = DEBUG
TOOL_CHAIN_TAG           = VS2003

Active Platform          = c:\work\edk2test\Nt32Pkg\Nt32Pkg.dsc
Flash Image Definition   = c:\work\edk2test\Nt32Pkg\Nt32Pkg.fdf

Processing meta-data .


build...
 : error C0DE: Unknown fatal error when processing [c:\work\edk2test\Nt32Pkg\Nt3
2Pkg.dsc]

(Please send email to edk2-buildtools-devel@... for help, atta
ching following call stack trace!)

(Python 2.5.2 on win32) Traceback (most recent call last):
  File "build.py", line 1861, in Main
  File "build.py", line 1627, in Launch
  File "build.py", line 1462, in _MultiThreadBuildPlatform
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
ine 82, in __new__
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
ine 176, in _Init
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
abase.py", line 2083, in __getitem__
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
abase.py", line 2325, in __getitem__
  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\MetaDataTabl
e.py", line 65, in Create
OperationalError: unable to open database file


- Failed -
19:17:59, May.18 2010 [00:02]


Andrew Fish





On May 18, 2010, at 6:35 PM, Huang, Qing wrote:

> Andrew,	
> 
> I suspect this should be related to the $(WORKSPACE)/Conf/.cache
> Could you please remove that directory and try rebuilding NT32 platform?
> 
> Thanks & Best regards,
> Huang, Qing 
> 
> -----Original Message-----
> From: Andrew Fish [mailto:afish@...] 
> Sent: Wednesday, May 19, 2010 3:29 AM
> To: edk2-devel@...
> Subject: [edk2] I've been seeing build crashes after the tools update last night?
> 
> Any one have an idea on whats going on? My Cygwin an OS X builds still work. Is it some issue with how the Python was frozen? 
> 
> C:\work\Edk2TOT>build -t VS2003
> 12:00:43, May.18 2010 [Windows-XP-5.1.2600]
> 
> WORKSPACE                = c:\work\edk2tot
> ECP_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
> EDK_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
> EFI_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
> EDK_TOOLS_PATH           = c:\work\edk2tot\basetools
> 
> TARGET_ARCH              = IA32
> TARGET                   = DEBUG
> TOOL_CHAIN_TAG           = VS2003
> 
> Active Platform          = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.dsc
> Flash Image Definition   = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.fdf
> 
> Processing meta-data .
> 
> 
> build...
> : error C0DE: Unknown fatal error when processing [c:\work\edk2tot\Nt32Pkg\Nt32
> Pkg.dsc]
> 
> (Please send email to edk2-buildtools-devel@... for help, atta
> ching following call stack trace!)
> 
> (Python 2.5.2 on win32) Traceback (most recent call last):
>  File "build.py", line 1861, in Main
>  File "build.py", line 1627, in Launch
>  File "build.py", line 1462, in _MultiThreadBuildPlatform
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
> ine 82, in __new__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
> ine 176, in _Init
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
> abase.py", line 2083, in __getitem__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
> abase.py", line 2325, in __getitem__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\MetaDataTabl
> e.py", line 65, in Create
> OperationalError: unable to open database file
> 
> 
> - Failed -
> 12:00:45, May.18 2010 [00:02]
> Andrew Fish
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel


------------------------------------------------------------------------------

_______________________________________________
edk2-devel mailing list
edk2-devel@...
https://lists.sourceforge.net/lists/listinfo/edk2-devel

It looks like the last tools check-in caused the issue. I've been staying in sync in real time with the tree. I pulled a clean tree and it failed. I was in VMware, I'll try doing Bootcamp and make sure it fails. 

Andrew Fish





On May 18, 2010, at 8:22 PM, Huang, Qing wrote:

> Andrew,
> 
> We have tried to reproduce the issue on our development machine. Unfortunately, we still cannot reproduce the issue on a brand clean tree.
> Looks like this is a regression issue on your machine. Could you please let us know the last working build.exe SVN revision that works fine on your machine? Maybe this will give us some clue for source code?
> 
> Thanks & Best regards,
> Huang, Qing
> 
> -----Original Message-----
> From: Andrew Fish [mailto:afish@...] 
> Sent: Wednesday, May 19, 2010 10:20 AM
> To: edk2-devel@...
> Subject: Re: [edk2] I've been seeing build crashes after the tools update last night?
> 
> I pulled a clean tree and got the same error.
> 
> C:\work\edk2test>build -t VS2003
> 19:17:58, May.18 2010 [Windows-XP-5.1.2600]
> 
> WORKSPACE                = c:\work\edk2test
> ECP_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
> EDK_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
> EFI_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
> EDK_TOOLS_PATH           = c:\work\edk2test\basetools
> 
> TARGET_ARCH              = IA32
> TARGET                   = DEBUG
> TOOL_CHAIN_TAG           = VS2003
> 
> Active Platform          = c:\work\edk2test\Nt32Pkg\Nt32Pkg.dsc
> Flash Image Definition   = c:\work\edk2test\Nt32Pkg\Nt32Pkg.fdf
> 
> Processing meta-data .
> 
> 
> build...
> : error C0DE: Unknown fatal error when processing [c:\work\edk2test\Nt32Pkg\Nt3
> 2Pkg.dsc]
> 
> (Please send email to edk2-buildtools-devel@... for help, atta
> ching following call stack trace!)
> 
> (Python 2.5.2 on win32) Traceback (most recent call last):
>  File "build.py", line 1861, in Main
>  File "build.py", line 1627, in Launch
>  File "build.py", line 1462, in _MultiThreadBuildPlatform
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
> ine 82, in __new__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
> ine 176, in _Init
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
> abase.py", line 2083, in __getitem__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
> abase.py", line 2325, in __getitem__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\MetaDataTabl
> e.py", line 65, in Create
> OperationalError: unable to open database file
> 
> 
> - Failed -
> 19:17:59, May.18 2010 [00:02]
> 
> 
> Andrew Fish
> 
> 
> 
> 
> 
> On May 18, 2010, at 6:35 PM, Huang, Qing wrote:
> 
>> Andrew,	
>> 
>> I suspect this should be related to the $(WORKSPACE)/Conf/.cache
>> Could you please remove that directory and try rebuilding NT32 platform?
>> 
>> Thanks & Best regards,
>> Huang, Qing 
>> 
>> -----Original Message-----
>> From: Andrew Fish [mailto:afish@...] 
>> Sent: Wednesday, May 19, 2010 3:29 AM
>> To: edk2-devel@...
>> Subject: [edk2] I've been seeing build crashes after the tools update last night?
>> 
>> Any one have an idea on whats going on? My Cygwin an OS X builds still work. Is it some issue with how the Python was frozen? 
>> 
>> C:\work\Edk2TOT>build -t VS2003
>> 12:00:43, May.18 2010 [Windows-XP-5.1.2600]
>> 
>> WORKSPACE                = c:\work\edk2tot
>> ECP_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
>> EDK_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
>> EFI_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
>> EDK_TOOLS_PATH           = c:\work\edk2tot\basetools
>> 
>> TARGET_ARCH              = IA32
>> TARGET                   = DEBUG
>> TOOL_CHAIN_TAG           = VS2003
>> 
>> Active Platform          = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.dsc
>> Flash Image Definition   = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.fdf
>> 
>> Processing meta-data .
>> 
>> 
>> build...
>> : error C0DE: Unknown fatal error when processing [c:\work\edk2tot\Nt32Pkg\Nt32
>> Pkg.dsc]
>> 
>> (Please send email to edk2-buildtools-devel@... for help, atta
>> ching following call stack trace!)
>> 
>> (Python 2.5.2 on win32) Traceback (most recent call last):
>> File "build.py", line 1861, in Main
>> File "build.py", line 1627, in Launch
>> File "build.py", line 1462, in _MultiThreadBuildPlatform
>> File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
>> ine 82, in __new__
>> File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
>> ine 176, in _Init
>> File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
>> abase.py", line 2083, in __getitem__
>> File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
>> abase.py", line 2325, in __getitem__
>> File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\MetaDataTabl
>> e.py", line 65, in Create
>> OperationalError: unable to open database file
>> 
>> 
>> - Failed -
>> 12:00:45, May.18 2010 [00:02]
>> Andrew Fish
>> 
>> 
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> 
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@...
>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>> 
>> ------------------------------------------------------------------------------
>> 
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@...
>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
> 
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel

Sorry Huang,

This is starting to look like a VMware caching issue? I BootCamped to XP and I was also able to get it to work. After it worked in XP proper, the VMware issue went away. 

Sorry for the false alarm....

Andrew Fish





On May 18, 2010, at 8:22 PM, Huang, Qing wrote:

> Andrew,
> 
> We have tried to reproduce the issue on our development machine. Unfortunately, we still cannot reproduce the issue on a brand clean tree.
> Looks like this is a regression issue on your machine. Could you please let us know the last working build.exe SVN revision that works fine on your machine? Maybe this will give us some clue for source code?
> 
> Thanks & Best regards,
> Huang, Qing
> 
> -----Original Message-----
> From: Andrew Fish [mailto:afish@...] 
> Sent: Wednesday, May 19, 2010 10:20 AM
> To: edk2-devel@...
> Subject: Re: [edk2] I've been seeing build crashes after the tools update last night?
> 
> I pulled a clean tree and got the same error.
> 
> C:\work\edk2test>build -t VS2003
> 19:17:58, May.18 2010 [Windows-XP-5.1.2600]
> 
> WORKSPACE                = c:\work\edk2test
> ECP_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
> EDK_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
> EFI_SOURCE               = c:\work\edk2test\edkcompatibilitypkg
> EDK_TOOLS_PATH           = c:\work\edk2test\basetools
> 
> TARGET_ARCH              = IA32
> TARGET                   = DEBUG
> TOOL_CHAIN_TAG           = VS2003
> 
> Active Platform          = c:\work\edk2test\Nt32Pkg\Nt32Pkg.dsc
> Flash Image Definition   = c:\work\edk2test\Nt32Pkg\Nt32Pkg.fdf
> 
> Processing meta-data .
> 
> 
> build...
> : error C0DE: Unknown fatal error when processing [c:\work\edk2test\Nt32Pkg\Nt3
> 2Pkg.dsc]
> 
> (Please send email to edk2-buildtools-devel@... for help, atta
> ching following call stack trace!)
> 
> (Python 2.5.2 on win32) Traceback (most recent call last):
>  File "build.py", line 1861, in Main
>  File "build.py", line 1627, in Launch
>  File "build.py", line 1462, in _MultiThreadBuildPlatform
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
> ine 82, in __new__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
> ine 176, in _Init
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
> abase.py", line 2083, in __getitem__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
> abase.py", line 2325, in __getitem__
>  File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\MetaDataTabl
> e.py", line 65, in Create
> OperationalError: unable to open database file
> 
> 
> - Failed -
> 19:17:59, May.18 2010 [00:02]
> 
> 
> Andrew Fish
> 
> 
> 
> 
> 
> On May 18, 2010, at 6:35 PM, Huang, Qing wrote:
> 
>> Andrew,	
>> 
>> I suspect this should be related to the $(WORKSPACE)/Conf/.cache
>> Could you please remove that directory and try rebuilding NT32 platform?
>> 
>> Thanks & Best regards,
>> Huang, Qing 
>> 
>> -----Original Message-----
>> From: Andrew Fish [mailto:afish@...] 
>> Sent: Wednesday, May 19, 2010 3:29 AM
>> To: edk2-devel@...
>> Subject: [edk2] I've been seeing build crashes after the tools update last night?
>> 
>> Any one have an idea on whats going on? My Cygwin an OS X builds still work. Is it some issue with how the Python was frozen? 
>> 
>> C:\work\Edk2TOT>build -t VS2003
>> 12:00:43, May.18 2010 [Windows-XP-5.1.2600]
>> 
>> WORKSPACE                = c:\work\edk2tot
>> ECP_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
>> EDK_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
>> EFI_SOURCE               = c:\work\edk2tot\edkcompatibilitypkg
>> EDK_TOOLS_PATH           = c:\work\edk2tot\basetools
>> 
>> TARGET_ARCH              = IA32
>> TARGET                   = DEBUG
>> TOOL_CHAIN_TAG           = VS2003
>> 
>> Active Platform          = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.dsc
>> Flash Image Definition   = c:\work\edk2tot\Nt32Pkg\Nt32Pkg.fdf
>> 
>> Processing meta-data .
>> 
>> 
>> build...
>> : error C0DE: Unknown fatal error when processing [c:\work\edk2tot\Nt32Pkg\Nt32
>> Pkg.dsc]
>> 
>> (Please send email to edk2-buildtools-devel@... for help, atta
>> ching following call stack trace!)
>> 
>> (Python 2.5.2 on win32) Traceback (most recent call last):
>> File "build.py", line 1861, in Main
>> File "build.py", line 1627, in Launch
>> File "build.py", line 1462, in _MultiThreadBuildPlatform
>> File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
>> ine 82, in __new__
>> File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\AutoGen\AutoGen.py", l
>> ine 176, in _Init
>> File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
>> abase.py", line 2083, in __getitem__
>> File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\WorkspaceDat
>> abase.py", line 2325, in __getitem__
>> File "C:\NightlyTest\FreezeTool\BaseTools\Source\Python\Workspace\MetaDataTabl
>> e.py", line 65, in Create
>> OperationalError: unable to open database file
>> 
>> 
>> - Failed -
>> 12:00:45, May.18 2010 [00:02]
>> Andrew Fish
>> 
>> 
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> 
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@...
>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>> 
>> ------------------------------------------------------------------------------
>> 
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@...
>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
> 
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel

Andrew,

Thanks a lot for pointing out this issue.  I have updated that package to fix that.

Best regards,
Huang, Qing
From: Andrew Fish [mailto:afish@...]
Sent: Tuesday, May 18, 2010 6:20 AM
To: edk2-devel@...
Subject: [edk2] Minor PerformancePkg issue: Library compiled for processor architectures that do not support the hardware.

TscTimerLib compiles for Itanium & ARM, but does not make sense for those processor types.

I think:

[Components]

  PerformancePkg/Library/TscTimerLib/TscTimerLib.inf

  PerformancePkg/Dp_App/Dp.inf





Should be:


[Components.IA32, Components.X64]

  PerformancePkg/Library/TscTimerLib/TscTimerLib.inf

[Components]

  PerformancePkg/Dp_App/Dp.inf





It also looks like a Unicode character is in the TscTimerLib.c file header:

  A Processor�s support for invariant TSC is indicated by CPUID.0x80000007.EDX[8].



Andrew Fish

Keshav,

I don't believe the DUET uses those drivers.  It uses the platform specific
FSVariable driver.

The MdeModulePkg\Universal\Variable\RuntimeDxe driver is used by many
platforms which are known to function properly at runtime.  One example from
edk2 is the OVMF platform, which I know can boot UEFI Fedora.

I think we should investigate using the same variable storage mechanism in
DUET as we use in OVMF, but I do not know of a plan currently to work on
this.

Can you share which distro you used as you found that the issue occured in
the virt_efi_get_next_variable call?

-Jordan


On Mon, May 17, 2010 at 11:27, KESHAV P.R. <skodabenz@...> wrote:

> Hi Ken,
>           The problem with virt_efi_get_next_variable linux kernel
> panic (or GetNextVariableName() function in EDK2) might have some
> thing to do with differences between EDK's
> <EDK_SVN_TRUNK>\Sample\Universal\Variable\RuntimeDxe folder and EDK2's
> <EDK2_SVN_TRUNK>\MdeModulePkg\Universal\Variable\RuntimeDxe folder. If
> the problem is indeed here then it is not specific to DUET like in
> case of FSVariable module. Please check these files.
>
> Regards,
> Keshav
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@...
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>