Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
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; coreboot@coreboot.org 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: coreboot@coreboot.org 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 -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
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: coreboot@coreboot.org 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 -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
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 -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
I just bought this board on internet. the cpu is Haswell i7-4600. That is all I
know.
Zheng
From: Robert Reeves
Sent: Wednesday, January 24, 2018 3:33 PM
To: Zheng Bao
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin
match my board
You're right about ifdtool, my mistake. What is your board exactly?
Rob
On Jan 24, 2018 10:12 AM, Zheng Bao wrote:
Or, I can ask my quesion in another way.
After extract the shellball of chromebook, how can I know what the processor
exactly is?
Zheng
From: coreboot on behalf of Zheng Bao
Sent: Wednesday, January 24, 2018 2:53 PM
To: Robert Reeves
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin
match my board
But it seems that ifdtool can only get ME, not MRC.
Zheng
From: Robert Reeves
Sent: Wednesday, January 24, 2018 1:35 PM
To: Zheng Bao
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin
match my board
They might not be the same. I would try using ifdtool to get an mrc.bin from a
rom for your specific board.
Rob
On Jan 24, 2018 5:53 AM, Zheng Bao wrote:
>
> Hi, All,
> The output of my board is attached below. The MRC.bin is extracted from
> panther, which I assume matches my board.
> But the meminit fails. Do all the haswell use the same MRC, or how can I
> decide which mrc.bin is the one I should extract?
>
> Thanks.
>
> Zheng
>
> coreboot-4.6-894-ga26344d-dirty Wed Jan 24 05:38:45 UTC 2018 romstage
> starting...
> Disabling Watchdog reboot... done.
> SMBus controller enabled.
> Setting up static northbridge registers... done.
> Initializing Graphics...
> Back from haswell_early_initialization()
> CPU id(40651) ucode:001c Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
> AES supported, TXT supported, VT supported
> PCH type: LP Premium, device id: 9c43, rev id 4
> Starting UEFI PEI System Agent ___
> CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0)
> CBFS: Locating 'mrc.cache'
> CBFS: Found @ offset fec0 size 1
> find_current_mrc_cache_local: No valid MRC cache found.
> CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0)
> CBFS: Locating 'mrc.bin'
> CBFS: Found @ offset 9fec0 size 2eb04
> System Agent: Starting up...
> System Agent: Initializing PCH
> install_ppi: overwrite GUID {ed097352-9041-445a-80b6-b29d509e8845}
> install_ppi: overwrite GUID {908c7f8b-5c48-47fb-8357-f5fd4e235276}
> System Agent: Initializing PCH (SMBUS)
> System Agent: Initializing PCH (USB)
> System Agent: Initializing PCH (SA Init)
> System Agent: Initializing PCH (Me UMA)
> System Agent: Initializing Memory
> System Agent: Done.
> Sanity checking heap.
> sdram_initialize,153: rv=0
> here.
> sdram_initialize,186
> sdram_initialize,189
> ME: FW Partition Table : OK
> ME: Bringup Loader Failure : NO
> ME: Firmware Init Complete : NO
> ME: Manufacturing Mode : YES
> ME: Boot Options Present: NO
> ME: Update In Progress : NO
> ME: Current Working State : Normal
> ME: Current Operation State : Bring up
> ME: Current Operation Mode : Security Override via Jumper
> ME: Error Code : No Error
> ME: Progress Phase : BUP Phase
> ME: Power Management Event : Pseudo-global reset
> ME: Progress Phase State: 0x66
> RAM INIT FAILURE!
>
--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
You're right about ifdtool, my mistake. What is your board exactly?
Rob
On Jan 24, 2018 10:12 AM, Zheng Bao wrote:
Or, I can ask my quesion in another way.
After extract the shellball of chromebook, how can I know what the processor exactly is?
Zheng
From: coreboot on behalf of Zheng Bao
Sent: Wednesday, January 24, 2018 2:53 PM
To: Robert Reeves
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
But it seems that ifdtool can only get ME, not MRC.
Zheng
From: Robert Reeves
Sent: Wednesday, January 24, 2018 1:35 PM
To: Zheng Bao
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
They might not be the same. I would try using ifdtool to get an mrc.bin from a rom for your specific board.
Rob
On Jan 24, 2018 5:53 AM, Zheng Bao wrote:
>
> Hi, All,
> The output of my board is attached below. The MRC.bin is extracted from panther, which I assume matches my board.
> But the meminit fails. Do all the haswell use the same MRC, or how can I decide which mrc.bin is the one I should extract?
>
> Thanks.
>
> Zheng
>
> coreboot-4.6-894-ga26344d-dirty Wed Jan 24 05:38:45 UTC 2018 romstage starting...
> Disabling Watchdog reboot... done.
> SMBus controller enabled.
> Setting up static northbridge registers... done.
> Initializing Graphics...
> Back from haswell_early_initialization()
> CPU id(40651) ucode:001c Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
> AES supported, TXT supported, VT supported
> PCH type: LP Premium, device id: 9c43, rev id 4
> Starting UEFI PEI System Agent ___
> CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0)
> CBFS: Locating 'mrc.cache'
> CBFS: Found @ offset fec0 size 1
> find_current_mrc_cache_local: No valid MRC cache found.
> CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0)
> CBFS: Locating 'mrc.bin'
> CBFS: Found @ offset 9fec0 size 2eb04
> System Agent: Starting up...
> System Agent: Initializing PCH
> install_ppi: overwrite GUID {ed097352-9041-445a-80b6-b29d509e8845}
> install_ppi: overwrite GUID {908c7f8b-5c48-47fb-8357-f5fd4e235276}
> System Agent: Initializing PCH (SMBUS)
> System Agent: Initializing PCH (USB)
> System Agent: Initializing PCH (SA Init)
> System Agent: Initializing PCH (Me UMA)
> System Agent: Initializing Memory
> System Agent: Done.
> Sanity checking heap.
> sdram_initialize,153: rv=0
> here.
> sdram_initialize,186
> sdram_initialize,189
> ME: FW Partition Table : OK
> ME: Bringup Loader Failure : NO
> ME: Firmware Init Complete : NO
> ME: Manufacturing Mode : YES
> ME: Boot Options Present : NO
> ME: Update In Progress : NO
> ME: Current Working State : Normal
> ME: Current Operation State : Bring up
> ME: Current Operation Mode : Security Override via Jumper
> ME: Error Code : No Error
> ME: Progress Phase : BUP Phase
> ME: Power Management Event : Pseudo-global reset
> ME: Progress Phase State : 0x66
> RAM INIT FAILURE!
>
--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
Or, I can ask my quesion in another way.
After extract the shellball of chromebook, how can I know what the processor
exactly is?
Zheng
From: coreboot on behalf of Zheng Bao
Sent: Wednesday, January 24, 2018 2:53 PM
To: Robert Reeves
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin
match my board
But it seems that ifdtool can only get ME, not MRC.
Zheng
From: Robert Reeves
Sent: Wednesday, January 24, 2018 1:35 PM
To: Zheng Bao
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin
match my board
They might not be the same. I would try using ifdtool to get an mrc.bin from a
rom for your specific board.
Rob
On Jan 24, 2018 5:53 AM, Zheng Bao wrote:
>
> Hi, All,
> The output of my board is attached below. The MRC.bin is extracted from
> panther, which I assume matches my board.
> But the meminit fails. Do all the haswell use the same MRC, or how can I
> decide which mrc.bin is the one I should extract?
>
> Thanks.
>
> Zheng
>
> coreboot-4.6-894-ga26344d-dirty Wed Jan 24 05:38:45 UTC 2018 romstage
> starting...
> Disabling Watchdog reboot... done.
> SMBus controller enabled.
> Setting up static northbridge registers... done.
> Initializing Graphics...
> Back from haswell_early_initialization()
> CPU id(40651) ucode:001c Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
> AES supported, TXT supported, VT supported
> PCH type: LP Premium, device id: 9c43, rev id 4
> Starting UEFI PEI System Agent ___
> CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0)
> CBFS: Locating 'mrc.cache'
> CBFS: Found @ offset fec0 size 1
> find_current_mrc_cache_local: No valid MRC cache found.
> CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0)
> CBFS: Locating 'mrc.bin'
> CBFS: Found @ offset 9fec0 size 2eb04
> System Agent: Starting up...
> System Agent: Initializing PCH
> install_ppi: overwrite GUID {ed097352-9041-445a-80b6-b29d509e8845}
> install_ppi: overwrite GUID {908c7f8b-5c48-47fb-8357-f5fd4e235276}
> System Agent: Initializing PCH (SMBUS)
> System Agent: Initializing PCH (USB)
> System Agent: Initializing PCH (SA Init)
> System Agent: Initializing PCH (Me UMA)
> System Agent: Initializing Memory
> System Agent: Done.
> Sanity checking heap.
> sdram_initialize,153: rv=0
> here.
> sdram_initialize,186
> sdram_initialize,189
> ME: FW Partition Table : OK
> ME: Bringup Loader Failure : NO
> ME: Firmware Init Complete : NO
> ME: Manufacturing Mode : YES
> ME: Boot Options Present: NO
> ME: Update In Progress : NO
> ME: Current Working State : Normal
> ME: Current Operation State : Bring up
> ME: Current Operation Mode : Security Override via Jumper
> ME: Error Code : No Error
> ME: Progress Phase : BUP Phase
> ME: Power Management Event : Pseudo-global reset
> ME: Progress Phase State: 0x66
> RAM INIT FAILURE!
>
--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
But it seems that ifdtool can only get ME, not MRC.
Zheng
From: Robert Reeves
Sent: Wednesday, January 24, 2018 1:35 PM
To: Zheng Bao
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin
match my board
They might not be the same. I would try using ifdtool to get an mrc.bin from a
rom for your specific board.
Rob
On Jan 24, 2018 5:53 AM, Zheng Bao wrote:
>
> Hi, All,
> The output of my board is attached below. The MRC.bin is extracted from
> panther, which I assume matches my board.
> But the meminit fails. Do all the haswell use the same MRC, or how can I
> decide which mrc.bin is the one I should extract?
>
> Thanks.
>
> Zheng
>
> coreboot-4.6-894-ga26344d-dirty Wed Jan 24 05:38:45 UTC 2018 romstage
> starting...
> Disabling Watchdog reboot... done.
> SMBus controller enabled.
> Setting up static northbridge registers... done.
> Initializing Graphics...
> Back from haswell_early_initialization()
> CPU id(40651) ucode:001c Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
> AES supported, TXT supported, VT supported
> PCH type: LP Premium, device id: 9c43, rev id 4
> Starting UEFI PEI System Agent ___
> CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0)
> CBFS: Locating 'mrc.cache'
> CBFS: Found @ offset fec0 size 1
> find_current_mrc_cache_local: No valid MRC cache found.
> CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0)
> CBFS: Locating 'mrc.bin'
> CBFS: Found @ offset 9fec0 size 2eb04
> System Agent: Starting up...
> System Agent: Initializing PCH
> install_ppi: overwrite GUID {ed097352-9041-445a-80b6-b29d509e8845}
> install_ppi: overwrite GUID {908c7f8b-5c48-47fb-8357-f5fd4e235276}
> System Agent: Initializing PCH (SMBUS)
> System Agent: Initializing PCH (USB)
> System Agent: Initializing PCH (SA Init)
> System Agent: Initializing PCH (Me UMA)
> System Agent: Initializing Memory
> System Agent: Done.
> Sanity checking heap.
> sdram_initialize,153: rv=0
> here.
> sdram_initialize,186
> sdram_initialize,189
> ME: FW Partition Table : OK
> ME: Bringup Loader Failure : NO
> ME: Firmware Init Complete : NO
> ME: Manufacturing Mode : YES
> ME: Boot Options Present: NO
> ME: Update In Progress : NO
> ME: Current Working State : Normal
> ME: Current Operation State : Bring up
> ME: Current Operation Mode : Security Override via Jumper
> ME: Error Code : No Error
> ME: Progress Phase : BUP Phase
> ME: Power Management Event : Pseudo-global reset
> ME: Progress Phase State: 0x66
> RAM INIT FAILURE!
>
--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
They might not be the same. I would try using ifdtool to get an mrc.bin from a
rom for your specific board.
Rob
On Jan 24, 2018 5:53 AM, Zheng Bao wrote:
>
> Hi, All,
> The output of my board is attached below. The MRC.bin is extracted from
> panther, which I assume matches my board.
> But the meminit fails. Do all the haswell use the same MRC, or how can I
> decide which mrc.bin is the one I should extract?
>
> Thanks.
>
> Zheng
>
> coreboot-4.6-894-ga26344d-dirty Wed Jan 24 05:38:45 UTC 2018 romstage
> starting...
> Disabling Watchdog reboot... done.
> SMBus controller enabled.
> Setting up static northbridge registers... done.
> Initializing Graphics...
> Back from haswell_early_initialization()
> CPU id(40651) ucode:001c Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
> AES supported, TXT supported, VT supported
> PCH type: LP Premium, device id: 9c43, rev id 4
> Starting UEFI PEI System Agent ___
> CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0)
> CBFS: Locating 'mrc.cache'
> CBFS: Found @ offset fec0 size 1
> find_current_mrc_cache_local: No valid MRC cache found.
> CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0)
> CBFS: Locating 'mrc.bin'
> CBFS: Found @ offset 9fec0 size 2eb04
> System Agent: Starting up...
> System Agent: Initializing PCH
> install_ppi: overwrite GUID {ed097352-9041-445a-80b6-b29d509e8845}
> install_ppi: overwrite GUID {908c7f8b-5c48-47fb-8357-f5fd4e235276}
> System Agent: Initializing PCH (SMBUS)
> System Agent: Initializing PCH (USB)
> System Agent: Initializing PCH (SA Init)
> System Agent: Initializing PCH (Me UMA)
> System Agent: Initializing Memory
> System Agent: Done.
> Sanity checking heap.
> sdram_initialize,153: rv=0
> here.
> sdram_initialize,186
> sdram_initialize,189
> ME: FW Partition Table : OK
> ME: Bringup Loader Failure : NO
> ME: Firmware Init Complete : NO
> ME: Manufacturing Mode : YES
> ME: Boot Options Present : NO
> ME: Update In Progress : NO
> ME: Current Working State : Normal
> ME: Current Operation State : Bring up
> ME: Current Operation Mode : Security Override via Jumper
> ME: Error Code : No Error
> ME: Progress Phase : BUP Phase
> ME: Power Management Event : Pseudo-global reset
> ME: Progress Phase State : 0x66
> RAM INIT FAILURE!
>
--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot
