From: Guy Raviv <guyraviv8@gmail.com>
To: Andrew Fish <afish@apple.com>, edk2-devel@lists.01.org
Subject: Re: Crc32 Calculation Miss
Date: Thu, 7 Jun 2018 09:18:30 +0300 [thread overview]
Message-ID: <CALFDPeW_aoAK2cdK+kyPQ0OznT_=A4dsb2zdo48et9gZ6KiqOQ@mail.gmail.com> (raw)
In-Reply-To: <8C61C5DC-F3B9-4AA2-A5BF-3264CC1E2BE6@apple.com>
Hi Andrew,
1. i checked the region which stores the code itself (called it MainFV), so
it is supposed to get updated only if i change the code.
2. i compared the binaries after the build, not in the system.
Thanks!
On Wed, Jun 6, 2018 at 6:43 PM, Andrew Fish <afish@apple.com> wrote:
>
> > On Jun 6, 2018, at 7:18 AM, Guy Raviv <guyraviv8@gmail.com> wrote:
> >
> > 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.
>
> Guy,
>
> What region did you check? There are areas of the FLASH that get updated
> (NVRAM, region used by an embedded controller, etc.), or never get updated
> (system serial # programmed at the factory).
>
> > 2. i also compared two different binaries and found they are exactly the
> > same.
> >
>
> Did you compare the binaries as part of the build or on the system?
>
> Thanks,
>
> Andrew Fish
>
> > 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
>
>
prev parent reply other threads:[~2018-06-07 6:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 14:18 Crc32 Calculation Miss Guy Raviv
2018-06-06 15:00 ` Gao, Liming
2018-06-07 6:34 ` Guy Raviv
2018-06-10 6:59 ` Guy Raviv
2018-06-11 2:34 ` Gao, Liming
2018-06-11 8:38 ` Guy Raviv
2018-06-11 15:44 ` Gao, Liming
2018-06-12 5:36 ` Guy Raviv
2018-06-13 2:42 ` Gao, Liming
2018-06-06 15:43 ` Andrew Fish
2018-06-07 6:18 ` Guy Raviv [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALFDPeW_aoAK2cdK+kyPQ0OznT_=A4dsb2zdo48et9gZ6KiqOQ@mail.gmail.com' \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox