From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2a00:1450:400c:c09::22d; helo=mail-wm0-x22d.google.com; envelope-from=guyraviv8@gmail.com; receiver=edk2-devel@lists.01.org Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id BBE6221130E6F for ; Mon, 11 Jun 2018 22:36:52 -0700 (PDT) Received: by mail-wm0-x22d.google.com with SMTP id j15-v6so20702749wme.0 for ; Mon, 11 Jun 2018 22:36:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vPg3uC04HwgbK+OqNF6MXwazZE0m6HwNCaXgNuXh+TQ=; b=GcL4b/EX5NKA1VC6cfOHAnjjTCwaZbqb9QdqTzv8G3QzIOPUl1JQ4svjwahrFZ3H/q NInOSif2W8ruShujvR14VE/kSxLdheOpAE7wm5kZL2GF5cWDFiB+/gqA67MkPP5Q7iX7 5Wij9OzNlva5lNv/OSAEof8unO4mDQJP4N2Wr9t3TMlWsc+XJvtowUVUEq0I+AOnXI9v DLYvsRxggoRhDImPZMwY/ZLQJ7nMKjNaGCtX4OzyJZO/DbgdzT18Gig3iEiK6rqU2g8V 9ovrr8RQrJlgYpiXXqteGT2iQOTyudeO9dGah0R0+k+/sNE++dtYSjDg0U0jmaWekFfM iYaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vPg3uC04HwgbK+OqNF6MXwazZE0m6HwNCaXgNuXh+TQ=; b=Vp9r4hKo39wFe5PrxuJ7bh7j48q49rAdldV115xh4gauC4L4M45Gu5xmV2Z8hGOHzx WJe/MbA2nCtm2xFmtb+YjyK0AW3T7gTEideuubmYFTMBiUmOAYpZUHPPgGPxGeRG8RZd pqwyDvBWKqusaRMw7Qf8UfINkmNDIvV5PDUpa3Bzlt6ra4CvQ8eI/JVpZOsIcUNgQA8a 93fqvU4odMWpJC5gzfmn0A5yp2MB45cqCg5VQQGvX27ds4+KxQQqNbNKqJkcpVw61z9Q E9kt7OIzyOGNc8tcl8AnSPqqu/gSz0HYQE4tPgNoEGELVJwhb7ie0Vju1ZyZWnAsdEza V5gw== X-Gm-Message-State: APt69E0ZV5sunD2mYKkPxuLxyV8aT+lIsrfGe/i4P1XPiCUO6n7IKsTK e2+ChQp8GyQWSr3Chnt9+if+p3TwR57BBrTP4Nw= X-Google-Smtp-Source: ADUXVKLcIG88pTtya4YSI/OS1gVyX4WL8upPtsGvq+CjgS69iGsymn4pfyGr7/Yj4V4b9SDQzm3ZSTqQUuc8/HjNkyE= X-Received: by 2002:a1c:4a9d:: with SMTP id n29-v6mr970269wmi.46.1528781811049; Mon, 11 Jun 2018 22:36:51 -0700 (PDT) MIME-Version: 1.0 References: <4A89E2EF3DFEDB4C8BFDE51014F606A14E2939F2@SHSMSX104.ccr.corp.intel.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E2953D0@SHSMSX104.ccr.corp.intel.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E2958F2@SHSMSX104.ccr.corp.intel.com> In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E2958F2@SHSMSX104.ccr.corp.intel.com> From: Guy Raviv Date: Tue, 12 Jun 2018 08:36:38 +0300 Message-ID: To: "Gao, Liming" Cc: edk2-devel@lists.01.org X-Content-Filtered-By: Mailman/MimeDel 2.1.26 Subject: Re: Crc32 Calculation Miss X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 05:36:53 -0000 Content-Type: text/plain; charset="UTF-8" I need to reach the pre memory code. Is it also loaded to the RAM(even though it is already been executed?) On Mon, 11 Jun 2018, 18:44 Gao, Liming, wrote: > In pre memory, PEI code run in flash. After memory is ready, PEI code will > be loaded into memory. There is no interface to access the whole flash > data. But, you can access the firmware image that contains PEI and DXE > driver. In PEI phase, you can locate FvInfoPpi > (gEfiPeiFirmwareVolumeInfoPpiGuid) to get FV image base address and size; > in DXE phase, you can locate FVB protocol > (gEfiFirmwareVolumeBlockProtocolGuid) to get FV image base address and > size. > > > > *From:* Guy Raviv [mailto:guyraviv8@gmail.com] > *Sent:* Monday, June 11, 2018 4:38 PM > *To:* Gao, Liming > *Cc:* edk2-devel@lists.01.org > *Subject:* Re: [edk2] Crc32 Calculation Miss > > > > EFI_CALCULATE_CRC32() just calculate the crc for the given address and > size. > > > > my question is whether PEI *code *is loaded into the RAM or not. > > if it doesn't which seems reasonable, how can i reach it? some interface > for accessing the whole flash data. > > > > Thanks, > > > > On Mon, Jun 11, 2018 at 5:34 AM Gao, Liming wrote: > > Guy: > > Does EFI_CALCULATE_CRC32() cover the flash data that includes PEI > module? > > > > Thanks > > Liming > > *From:* Guy Raviv [mailto:guyraviv8@gmail.com] > *Sent:* Sunday, June 10, 2018 2:59 PM > *To:* Gao, Liming > *Cc:* edk2-devel@lists.01.org > *Subject:* Re: [edk2] Crc32 Calculation Miss > > > > Update - it seems that only in the Pei modules a code change doesn't > change the crc. > > Does it make sense? > > if so, is there any interface to calculate the flash data itself in the > Dxe phase? > > > > Thanks! > > Guy > > > > On Thu, Jun 7, 2018 at 9:34 AM Guy Raviv wrote: > > Hi Gao, > > > > I used the EFI_CALCULATE_CRC32 function from > edkCompatibilityPkg\Foundation. > > > > Thanks, > > > > Guy > > > > On Wed, Jun 6, 2018 at 6:00 PM, Gao, Liming wrote: > > Do you use CalculateCrc32() in BaseLib to calculate CRC32 value for the > different buffer? > > > > -----Original Message----- > > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > Guy Raviv > > Sent: Wednesday, June 6, 2018 10:18 PM > > To: edk2-devel@lists.01.org > > Subject: [edk2] Crc32 Calculation Miss > > > > Hi Everyone, > > > > I have an odd problem. > > In a specific module in my code (MRC training), code modification doesn't > > change the BIOS Crc calculation. > > 1. i checked in my project's fdf file if the FV base address and region > > size defined are the same as the parameters i'm putting in the > calculation. > > 2. i also compared two different binaries and found they are exactly the > > same. > > > > does anyone have any idea what can be wrong here or where should i check? > > > > Thanks, > > Guy > > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel > > > >