Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board

[Zheng Bao]

Plus, my board uses SODIMM, from which I assume System Agent should get SPD data.

Is the grabbing data from SPD in blob? I can not dump the SPD out, can I?

Zheng

________________________________
From: coreboot  on behalf of Zheng Bao 
Sent: Saturday, January 27, 2018 4:47 AM
To: Nico Huber; Robert Reeves
Cc: Matt DeVillier; [e-mail]
Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board

I traced the code more and found the accessing data in MCHBAR would hang the board. Just hang, not reboot.

Even if I move the accessing backward to haswell_setup_bars, it hangs as well. Why?

My board also has a superio(or EC?) IT8772, which I assume doesnt make this problem.

Thanks.

Zheng

________________________________
From: Nico Huber 
Sent: Friday, January 26, 2018 2:15 PM
To: Zheng Bao; Robert Reeves
Cc: [e-mail]
Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board

Hi Zheng,

On 24.01.2018 16:12, Zheng Bao wrote:
> After extract the shellball of chromebook, how can I know what the
> processor exactly is?

I don't know the blob for Haswell very well. But here's what I know
about other blobs:

* Sandy/Ivy Bridge mrc.bin: This one seems to run on every CPU so far.

* FSP is not built for specific SKUs. The code is supposed to work on
     any, I guess. But the releases are only validated for specific SKUs.

So it's not unlikely that a blob you extracted from a Chromebook firm-
ware "should" run with any Haswell CPU. But still it could make trouble
with your CPU, if nobody tested it before in that combination.

As you have very limited output from the blob about the failure. I
wonder why you suspect the blob itself to be the problem? other things
could go wrong as well (e.g. gathering data from SPDs).

Also, I'd first check that your revision of coreboot works together with
that specific blob on any board (e.g. the original Chromebook).

Nico