From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-lj1-f169.google.com (mail-lj1-f169.google.com [209.85.208.169]) by mx.groups.io with SMTP id smtpd.web10.13136.1677757571474620577 for ; Thu, 02 Mar 2023 03:46:11 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=dMRDlvmx; spf=pass (domain: gmail.com, ip: 209.85.208.169, mailfrom: alibanejad1376@gmail.com) Received: by mail-lj1-f169.google.com with SMTP id b13so17317305ljf.6 for ; Thu, 02 Mar 2023 03:46:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=caKbb6677V2mVREUJC1RWJTg9uQASNsElkl6v5BlEgE=; b=dMRDlvmxxJFlH46VDsBwoZCEYPDYXdK5aZCOtc3+wJPtA+0NLm/rVwQrdsATUjUUeR aISvbMRlCZyfeavrC5XsxCaE1xa6h6oFf28BXf6v8Qnjaa989no7Apdw0ojCs1xDEo6k 7tyrqqMu21OsceNQka2x/jl+tVnX+uBWIRj6s2YmmuMOVqHbbiYMSh3eIWl8jGVEIEUc E2WhkiF7qX396qRiuYdHuRSzAZ10ZTynZmvmZIla7G6jau6qUqLw7a2PteRjDVlCLg2R xO5W1DHkpq/4j333lGTOynb450tvmTjHeatkLhSx3SXaFR7VtRLFHwiOnhT25946/awQ ZQqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=caKbb6677V2mVREUJC1RWJTg9uQASNsElkl6v5BlEgE=; b=YmfqtHeVJA+b0B9YZyzJ0k3Jiw5co9iVjP34ZNMHZMUc8HFOuaL6SzzVHqkbq5eyA5 Ac7Daef67m6MrP8xw8E5kB4h1f+R56WvxCWZQiw7Ou5bVAez9eeqro7Q984s/TVplpII jQUTpYynVkfOihKDUHiSGIVL760CRmS67xycn4awe5GhJj48H4GzCS7I6NZJX5jRYRkX DhOGTmxah9tpU5Alx7kd0+i4UsPqf2iGiGCm9HV9KS5TaJZXWNWeX6/b0roLsE3aeU1o 7DhBOw4zn29ZYkQTuBHZuAQSQ0Gvtx7LKoLRZ+MFwA+clnEQmWCZdWaSEfg422mckJb6 v6bQ== X-Gm-Message-State: AO0yUKVmwY/+7KFByimsAoNIXx7lLKi0ZJx65mTod471FJp1BwUp7dZD LTOHglFQcJyPn+5ll6/jTtstbJ1V6oXCfBbFxMood2ESh+5WS8Fz X-Google-Smtp-Source: AK7set9IbKlBcK+qHO6C8STGetE4p01gEDE6llH5fea7mbohQ5XIERMzo5VxsyZEmMr1XSeLu6kJx6mxCCC+4H4N7i0= X-Received: by 2002:a2e:b5af:0:b0:295:af0c:33aa with SMTP id f15-20020a2eb5af000000b00295af0c33aamr3138496ljn.7.1677757569054; Thu, 02 Mar 2023 03:46:09 -0800 (PST) MIME-Version: 1.0 References: <1747FB5DED91B485.22517@groups.io> In-Reply-To: <1747FB5DED91B485.22517@groups.io> From: "Alireza Banejad" Date: Thu, 2 Mar 2023 15:16:06 +0330 Message-ID: Subject: Re: [edk2-devel] GetSectionFromAnyFv doesnt find file from FV To: devel@edk2.groups.io, alibanejad1376@gmail.com Content-Type: multipart/alternative; boundary="000000000000ec39a905f5e95f24" --000000000000ec39a905f5e95f24 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Any thoughts? On Tue, Feb 28, 2023 at 3:32=E2=80=AFPM Alireza Banejad via groups.io wrote: > Hi everyone, > I have this bmp file which I defined in the FV.FVMAIN_COMPACT section of > the OvmfPkgX64.fdf file. when I get the a hexdump on the built firmware > (OVMF.fd) I can see the file inside it. but whenever I call the > the GetSectionFromAnyFv() function from a Application it fails to find th= e > file. > This is how I defined the file in OvmfX64.fdf: > ____________________________________ > [FV.FVMAIN_COMPACT] > FvNameGuid =3D 48DB5E17-707C-472D-91CD-1613E7EF51B0 > FvAlignment =3D 16 > ERASE_POLARITY =3D 1 > MEMORY_MAPPED =3D TRUE > STICKY_WRITE =3D TRUE > LOCK_CAP =3D TRUE > LOCK_STATUS =3D TRUE > WRITE_DISABLED_CAP =3D TRUE > WRITE_ENABLED_CAP =3D TRUE > WRITE_STATUS =3D TRUE > WRITE_LOCK_CAP =3D TRUE > WRITE_LOCK_STATUS =3D TRUE > READ_DISABLED_CAP =3D TRUE > READ_ENABLED_CAP =3D TRUE > READ_STATUS =3D TRUE > READ_LOCK_CAP =3D TRUE > READ_LOCK_STATUS =3D TRUE > > > > > FILE FV_IMAGE =3D 9E21FD93-9C72-4c15-8C4B-E77F1DB2D792 { > SECTION GUIDED EE4E5898-3914-4259-9D6E-DC7BD79403CF PROCESSING_REQUIRE= D > =3D TRUE { > # > # These firmware volumes will have files placed in them uncompressed= , > # and then both firmware volumes will be compressed in a single > # compression operation in order to achieve better overall > compression. > # > SECTION FV_IMAGE =3D PEIFV > SECTION FV_IMAGE =3D DXEFV > } > } > FILE FREEFORM =3D AFDAEAB5-3F81-4E93-8EE3-228434BA283D { > SECTION RAW =3D OemPkg/FrontPage/Resources/FrontpageLogo.bmp > } > > > > !include FvmainCompactScratchEnd.fdf.inc > __________________________________________ > > and this is how I am using the GetSectionFromAnyFv() function: > Status =3D GetSectionFromAnyFv ( > FileGuid, > EFI_SECTION_RAW, > 0, > (VOID **)&BMPData, > &BMPDataSize > ); > So there's nothing much to it, yet I still don't know why it fails to fin= d > the file. I also must mention that I checked the GUID being passed to the > function and the GUID of the file, they are both the same. I still don't > know what's going on >=20 > > --000000000000ec39a905f5e95f24 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Any thoughts?

On Tue, Feb 28, 2023 at 3:32=E2=80=AFPM Alire= za Banejad via groups.io <alibanejad137= 6=3Dgmail.com@groups.io> wrot= e:
Hi everyone,
I have this bmp file which I defined in the FV.FVMAIN_= COMPACT section of the OvmfPkgX64.fdf file. when I get the a hexdump on the= built firmware (OVMF.fd) I can see the file inside it. but whenever I call= the the=C2=A0GetSectionFromAnyFv() function from a Application it fails to= find the file.
This is how I defined the file in OvmfX64.fdf:
____________________________________
[FV.FVMAIN_COMPACT]<= br>FvNameGuid =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D 48DB5E17-707C-472D-91CD-1613E= 7EF51B0
FvAlignment =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D 16
ERASE_POLARITY = =C2=A0 =C2=A0 =3D 1
MEMORY_MAPPED =C2=A0 =C2=A0 =C2=A0=3D TRUE
STICKY= _WRITE =C2=A0 =C2=A0 =C2=A0 =3D TRUE
LOCK_CAP =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =3D TRUE
LOCK_STATUS =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D TRUE
W= RITE_DISABLED_CAP =3D TRUE
WRITE_ENABLED_CAP =C2=A0=3D TRUE
WRITE_STA= TUS =C2=A0 =C2=A0 =C2=A0 =3D TRUE
WRITE_LOCK_CAP =C2=A0 =C2=A0 =3D TRUE<= br>WRITE_LOCK_STATUS =C2=A0=3D TRUE
READ_DISABLED_CAP =C2=A0=3D TRUE
= READ_ENABLED_CAP =C2=A0 =3D TRUE
READ_STATUS =C2=A0 =C2=A0 =C2=A0 =C2=A0= =3D TRUE
READ_LOCK_CAP =C2=A0 =C2=A0 =C2=A0=3D TRUE
READ_LOCK_STATUS = =C2=A0 =3D TRUE




FILE FV_IMAGE =3D 9E21FD93-9C72-4c15-8C4= B-E77F1DB2D792 {
=C2=A0 =C2=A0SECTION GUIDED EE4E5898-3914-4259-9D6E-DC7= BD79403CF PROCESSING_REQUIRED =3D TRUE {
=C2=A0 =C2=A0 =C2=A0#
=C2=A0= =C2=A0 =C2=A0# These firmware volumes will have files placed in them uncom= pressed,
=C2=A0 =C2=A0 =C2=A0# and then both firmware volumes will be co= mpressed in a single
=C2=A0 =C2=A0 =C2=A0# compression operation in orde= r to achieve better overall compression.
=C2=A0 =C2=A0 =C2=A0#
=C2=A0= =C2=A0 =C2=A0SECTION FV_IMAGE =3D PEIFV
=C2=A0 =C2=A0 =C2=A0SECTION FV_= IMAGE =3D DXEFV
=C2=A0 =C2=A0}
=C2=A0}
=C2=A0 FILE FREEFORM =3D AF= DAEAB5-3F81-4E93-8EE3-228434BA283D {
=C2=A0 =C2=A0 SECTION RAW =3D OemPk= g/FrontPage/Resources/FrontpageLogo.bmp
=C2=A0 }



!include= FvmainCompactScratchEnd.fdf.inc
____________________________= ______________

and this is how I am using the=C2= =A0GetSectionFromAnyFv() function:
=C2=A0 Status =3D GetSectionFr= omAnyFv (
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0FileGuid,
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0EFI_SECTION_RAW,
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0(VOID **)&BMPData,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0&BMPDataSize
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0);
So there's nothing much to it, yet I stil= l don't know why it fails to find the file. I also must mention that I = checked the GUID being passed to the function and the GUID of the file, the= y are both the same. I still don't know what's going on

--000000000000ec39a905f5e95f24--