On 9/8/21 8:19 PM, Yao, Jiewen wrote:
Many reasons on an Entrypoint not called.
I share my experence below (I encountered all of them before):
1) You update the code in a wrong tree.
2) The image is not rebuild. You still use old image.
3) The image is rebuild, but the image is not reburn to the flash.
4) The driver is not in final image.
5) The dependency is not satisfied.
6) It is actually called and run, but it fails to dump debug message to the
console, which make you think it is not called.
7) It is actually called, but it gets some error and exits earlier than you
expect.
The entry point currently has an endless loop in it, thus should stop
edk2, but it doesn't.
Debug BKM:
1) Ensure you are working on the right tree.
2) Use a tool to scan the final image.
3) Burn the new image again.
4) Ensure driver is included in FDF.
5) Check the dependency in final build report.
6) Ensure you link a good debug lib, and debug lib can output something at that
time.
7) Add a debug as the first code at entrypoint.
I have tried a lot of things but it doesn't work . I don't know what is
wrong. My current tree is here:
git: https://github.com/stefanberger/edk2.git
branch: ovmf_disable_platform_hierarchy.v7
web:
https://github.com/stefanberger/edk2/tree/stefanberger/ovmf_disable_platform_hierarchy.v7
I am using the following command line to build it. Only
OvmfPkg/OvmfPkgX64.dsc needs to work it this point, the other targets
still need modification after v6.
build -p OvmfPkg/OvmfPkgX64.dsc -b DEBUG -a X64 -t GCC5 -D TPM_ENABLE -D
TPM_CONFIG_ENABLE -D SECURE_BOOT_ENABLE -D NETWORK_TLS_ENABLE
Stefan
Thank you
Yao Jiewen
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Stefan
Berger
Sent: Thursday, September 9, 2021 4:35 AM
To: Yao, Jiewen <jiewen....@intel.com>; devel@edk2.groups.io; Stefan Berger
<stef...@linux.vnet.ibm.com>
Cc: mhaeu...@posteo.de; spbro...@outlook.com;
marcandre.lur...@redhat.com; kra...@redhat.com
Subject: Re: [edk2-devel] [PATCH v5 0/8] Ovmf: Disable the TPM2 platform
hierarchy
On 9/8/21 10:37 AM, Yao, Jiewen wrote:
Hi Stefan
According to our security policy, the PPI must be sent before EndOfDxe.
Then registering PlatformAuth clear at EndOfDxe is safe. I still don’t get your
point on why we have do in PlatformBds.
At least, I do want to make sure all X86 implementation are align to one
solution.
Also, for PEI, I don’t think we shall modify the Tcg2Pei in this patch set.
The platform auth clear is platform action. I think we need a standalone PEIM,
to allow platform do its own stuff.
All in all, I try to understand, why not just copy the solution in
MinPlatformPkg?
A standalone TcgPlatformPei/Dxe?
I tried to import Tcg2PlatformDxe with it's .c and .inf files but cannot
get its EntryPoint invoked when running OvmfPkg/OvmfPkgX64.dsc
Thank you
Yao Jiewen
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#80428): https://edk2.groups.io/g/devel/message/80428
Mute This Topic: https://groups.io/mt/85316773/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
