[flashrom] Re: Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D)
Hi Ocean
On Tue, Mar 24, 2020 at 2:41 AM Ocean Huang wrote:
>
> Hi Angel:
>
> "0xa1c8" seems is the "QS/PRQ" SKU, but it does not mark it as "QS/PRQ" SKU
> in the eds spec "568202-d-2100-eds-rev2-1-review.pdf", the detail you can see
> the below image.
>
>
> However, I think the device id 0xa1c8 whether QS/PRQ SKU or Super SKU will
> not affect for flashrom tool.
Right, looks like the Xeon D-2100 integrates a Lewisburg PCH inside.
That explains why I couldn't find that ID anywhere: there is no
publicly available datasheet for these Xeons.
> Anyway, thank you very much for the support.
>
> Thanks,
> Best Regards,
> Ocean
>
> On Mon, Mar 23, 2020 at 11:08 PM Angel Pons wrote:
>>
>> Hi Ocean,
>>
>> On Mon, Mar 23, 2020 at 2:00 PM Ocean Huang via flashrom
>> wrote:
>> >
>> > Hi David:
>> >
>> > For flashrom could update BIOS successfully on the Intel Bakerville
>> > platform(CPU:SKY-D), we need to add device id to chipset_enables table in
>> > the file of"chipset_enables.c", or it will cause below error:
>> > WARNING: No chipset found. Flash detection will most likely fail.
>> > No EEPROM/flash device found.
>> > Note: flashrom can never write if the flash chip isn't found automatically.
>> >
>> > So could you please help to add these three device ids to the
>> > chipset_enable table and upload to the Github?
>> > Attached the changed file.
>>
>> I see that you have added these three new device IDs:
>>
>> {0x8086, 0xa1c8, NT, "Intel", "C620 Series Chipset Supersku",
>> enable_flash_c620},
>> {0x8086, 0xa248, NT, "Intel", "C620 Series Chipset Supersku",
>> enable_flash_c620},
>> {0x8086, 0xa249, NT, "Intel", "C620 Series Chipset Supersku",
>> enable_flash_c620},
>>
>> I can confirm that the last two IDs are for Super SKUs, but "0xa1c8"
>> (the first one) seems to be a "QS/PRQ" SKU. Could you please confirm
>> it? I have created a change to add these IDs:
>>
>> https://review.coreboot.org/39780
>>
>> In addition, since flashrom can successfully update the BIOS on these
>> chipsets, knowing the Device IDs that have been tested would be much
>> appreciated. That way, we can mark the chipsets as tested.
>>
>> > Thanks,
>> > Best Regards,
>> > Ocean
>> >
>> > --
>> > Thanks,
>> > Best Regards,
>> > Ocean Huang
>> > BIOS Engineer
>> > Celestica(Shanghai) R Center, China
>> > email: hah...@celestica.com
>> > www.celestica.com
>> > ___
>> > flashrom mailing list -- flashrom@flashrom.org
>> > To unsubscribe send an email to flashrom-le...@flashrom.org
>>
>> Thanks in advance,
>>
>> Angel Pons
>
>
>
> --
> Thanks,
> Best Regards,
> Ocean Huang
> BIOS Engineer
> Celestica(Shanghai) R Center, China
> email: hah...@celestica.com
> www.celestica.com
Best regards,
Angel Pons
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org
[flashrom] Re: Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D)
Hi Ocean,
On Mon, Mar 23, 2020 at 2:00 PM Ocean Huang via flashrom
wrote:
>
> Hi David:
>
> For flashrom could update BIOS successfully on the Intel Bakerville
> platform(CPU:SKY-D), we need to add device id to chipset_enables table in the
> file of"chipset_enables.c", or it will cause below error:
> WARNING: No chipset found. Flash detection will most likely fail.
> No EEPROM/flash device found.
> Note: flashrom can never write if the flash chip isn't found automatically.
>
> So could you please help to add these three device ids to the chipset_enable
> table and upload to the Github?
> Attached the changed file.
I see that you have added these three new device IDs:
{0x8086, 0xa1c8, NT, "Intel", "C620 Series Chipset Supersku",
enable_flash_c620},
{0x8086, 0xa248, NT, "Intel", "C620 Series Chipset Supersku",
enable_flash_c620},
{0x8086, 0xa249, NT, "Intel", "C620 Series Chipset Supersku",
enable_flash_c620},
I can confirm that the last two IDs are for Super SKUs, but "0xa1c8"
(the first one) seems to be a "QS/PRQ" SKU. Could you please confirm
it? I have created a change to add these IDs:
https://review.coreboot.org/39780
In addition, since flashrom can successfully update the BIOS on these
chipsets, knowing the Device IDs that have been tested would be much
appreciated. That way, we can mark the chipsets as tested.
> Thanks,
> Best Regards,
> Ocean
>
> --
> Thanks,
> Best Regards,
> Ocean Huang
> BIOS Engineer
> Celestica(Shanghai) R Center, China
> email: hah...@celestica.com
> www.celestica.com
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org
Thanks in advance,
Angel Pons
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org
[flashrom] Re: Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D)
Hi David: For flashrom could update BIOS successfully on the Intel Bakerville platform(CPU:SKY-D), we need to add device id to chipset_enables table in the file of"chipset_enables.c", or it will cause below error: WARNING: No chipset found. Flash detection will most likely fail. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. So could you please help to add these three device ids to the chipset_enable table and upload to the Github? Attached the changed file. Thanks, Best Regards, Ocean On Wed, Mar 4, 2020 at 2:47 PM Ocean Huang wrote: > Thanks a lot. > > On Wed, Mar 4, 2020 at 2:43 PM David Hendricks wrote: > >> (Resending to the mailing list) >> -- >> *From:* David Hendricks >> *Sent:* Monday, March 2, 2020 2:50:24 PM >> *To:* flashrom@flashrom.org ; Ocean Huang < >> hah...@celestica.com> >> *Subject:* Re: [flashrom] Flashrom tool failed on the Intel Bakerville >> platform(CPU:SKY-D) >> >> Hello Ocean, >> At the moment we do not support updating the Intel ME region. You may >> target other regions described by the flash descriptor using the --ifd >> option, for example `flashrom -p internal --ifd -i bios --noverify-all -w >> CBR.1.00.01.bin`*.* >> >> Depending on your use case, another option is to modify the flash >> descriptor to allow the host to write to the ME region. However Intel >> recommends locking the ME region so that reads and writes to the ME region >> from the host are not allowed. >> >> Please also see https://flashrom.org/ME#Suggested_workarounds for >> additional guidance. >> -- >> *From:* Ocean Huang via flashrom >> *Sent:* Wednesday, February 26, 2020 5:20 AM >> *To:* flashrom@flashrom.org >> *Subject:* [flashrom] Flashrom tool failed on the Intel Bakerville >> platform(CPU:SKY-D) >> >> Hi Vendor: >> >> We have some issue when using flashrom tool update BIOS & ME firmware on >> the Intel Bakeville platform, you can refer to the below error log, could >> you please help give some comments or suggestions about this issue? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *[root@localhost flashrom-v1.1]# ./flashrom -p internal -w >> CBR.1.00.01.bin flashrom v1.1 on Linux 3.10.0-957.el7.x86_64 (x86_64) >> flashrom is free software, get the source code at https://flashrom.org >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org=DwMFaQ=5VD0RTtNlTh3ycd41b3MUw=4-bAjA7rj5_lsAnGYQCM_w=532SYzVno7CxakMNFHC-ELomxuPqcWKaBcM1kqjV6qc=lw-AUImht5ouHueP-_e7nSmbqEDP4RPihF9Y8o5_70A=> >> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found >> chipset "Intel C620 Series Chipset Supersku". This chipset is marked as >> untested. If you are using an up-to-date version of flashrom *and* were >> (not) able to successfully update your firmware with it, then please email >> a report to flashrom@flashrom.org including a >> verbose (-V) log. Thank you! Enabling flash write... SPI Configuration is >> locked down. FREG2: Management Engine region (0x3000-0x00a15fff) is >> locked. Not all flash regions are freely accessible by flashrom. This is >> most likely due to an active ME. Please see https://flashrom.org/ME >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org_ME=DwMFaQ=5VD0RTtNlTh3ycd41b3MUw=4-bAjA7rj5_lsAnGYQCM_w=532SYzVno7CxakMNFHC-ELomxuPqcWKaBcM1kqjV6qc=X8yqTjX2TTNy16DkSDCTNXyOc8FAG1Yfn126AxBHqVI=> >> for details. At least some flash regions are read protected. You have to >> use a flash layout and include only accessible regions. For write >> operations, you'll additionally need the --noverify-all switch. See manpage >> for more details. Enabling hardware sequencing because some important >> opcode is locked. OK. Found Programmer flash chip "Opaque flash chip" >> (32768 kB, Programmer-specific) mapped at physical address >> 0x. Reading old flash chip contents... Transaction error >> between offset 0x3000 and 0x303f (= 0x3000 + 63)! FAILED. >> [root@localhost flashrom-v1.1]# ./flashrom -p internal -r 111.bin --ifd -i >> bios flashrom v1.1 on Linux 3.10.0-957.el7.x86_64 (x86_64) flashrom is free >> software, get the source code at https://f
[flashrom] Re: Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D)
Thanks a lot. On Wed, Mar 4, 2020 at 2:43 PM David Hendricks wrote: > (Resending to the mailing list) > -- > *From:* David Hendricks > *Sent:* Monday, March 2, 2020 2:50:24 PM > *To:* flashrom@flashrom.org ; Ocean Huang < > hah...@celestica.com> > *Subject:* Re: [flashrom] Flashrom tool failed on the Intel Bakerville > platform(CPU:SKY-D) > > Hello Ocean, > At the moment we do not support updating the Intel ME region. You may > target other regions described by the flash descriptor using the --ifd > option, for example `flashrom -p internal --ifd -i bios --noverify-all -w > CBR.1.00.01.bin`*.* > > Depending on your use case, another option is to modify the flash > descriptor to allow the host to write to the ME region. However Intel > recommends locking the ME region so that reads and writes to the ME region > from the host are not allowed. > > Please also see https://flashrom.org/ME#Suggested_workarounds for > additional guidance. > -- > *From:* Ocean Huang via flashrom > *Sent:* Wednesday, February 26, 2020 5:20 AM > *To:* flashrom@flashrom.org > *Subject:* [flashrom] Flashrom tool failed on the Intel Bakerville > platform(CPU:SKY-D) > > Hi Vendor: > > We have some issue when using flashrom tool update BIOS & ME firmware on > the Intel Bakeville platform, you can refer to the below error log, could > you please help give some comments or suggestions about this issue? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > *[root@localhost flashrom-v1.1]# ./flashrom -p internal -w > CBR.1.00.01.bin flashrom v1.1 on Linux 3.10.0-957.el7.x86_64 (x86_64) > flashrom is free software, get the source code at https://flashrom.org > <https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org=DwMFaQ=5VD0RTtNlTh3ycd41b3MUw=4-bAjA7rj5_lsAnGYQCM_w=532SYzVno7CxakMNFHC-ELomxuPqcWKaBcM1kqjV6qc=lw-AUImht5ouHueP-_e7nSmbqEDP4RPihF9Y8o5_70A=> > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found > chipset "Intel C620 Series Chipset Supersku". This chipset is marked as > untested. If you are using an up-to-date version of flashrom *and* were > (not) able to successfully update your firmware with it, then please email > a report to flashrom@flashrom.org including a > verbose (-V) log. Thank you! Enabling flash write... SPI Configuration is > locked down. FREG2: Management Engine region (0x3000-0x00a15fff) is > locked. Not all flash regions are freely accessible by flashrom. This is > most likely due to an active ME. Please see https://flashrom.org/ME > <https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org_ME=DwMFaQ=5VD0RTtNlTh3ycd41b3MUw=4-bAjA7rj5_lsAnGYQCM_w=532SYzVno7CxakMNFHC-ELomxuPqcWKaBcM1kqjV6qc=X8yqTjX2TTNy16DkSDCTNXyOc8FAG1Yfn126AxBHqVI=> > for details. At least some flash regions are read protected. You have to > use a flash layout and include only accessible regions. For write > operations, you'll additionally need the --noverify-all switch. See manpage > for more details. Enabling hardware sequencing because some important > opcode is locked. OK. Found Programmer flash chip "Opaque flash chip" > (32768 kB, Programmer-specific) mapped at physical address > 0x. Reading old flash chip contents... Transaction error > between offset 0x3000 and 0x303f (= 0x3000 + 63)! FAILED. > [root@localhost flashrom-v1.1]# ./flashrom -p internal -r 111.bin --ifd -i > bios flashrom v1.1 on Linux 3.10.0-957.el7.x86_64 (x86_64) flashrom is free > software, get the source code at https://flashrom.org > <https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org=DwMFaQ=5VD0RTtNlTh3ycd41b3MUw=4-bAjA7rj5_lsAnGYQCM_w=532SYzVno7CxakMNFHC-ELomxuPqcWKaBcM1kqjV6qc=lw-AUImht5ouHueP-_e7nSmbqEDP4RPihF9Y8o5_70A=> > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found > chipset "Intel C620 Series Chipset Supersku". This chipset is marked as > untested. If you are using an up-to-date version of flashrom *and* were > (not) able to successfully update your firmware with it, then please email > a report to flashrom@flashrom.org including a > verbose (-V) log. Thank you! Enabling flash write... SPI Configuration is > locked down. FREG2: Management Engine region (0x3000-0x00a15fff) is > locked. Not all flash regions are freely accessible by flashrom. This is > most likely due to an active ME. Please see https://flashrom.org/ME > <https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org_ME=DwMFaQ=5VD0RTtNlTh3ycd41b3MUw=4-bAjA7rj5_lsAnGYQCM_w=532SYz
[flashrom] Re: Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D)
(Resending to the mailing list) From: David Hendricks Sent: Monday, March 2, 2020 2:50:24 PM To: flashrom@flashrom.org ; Ocean Huang Subject: Re: [flashrom] Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D) Hello Ocean, At the moment we do not support updating the Intel ME region. You may target other regions described by the flash descriptor using the --ifd option, for example `flashrom -p internal --ifd -i bios --noverify-all -w CBR.1.00.01.bin`. Depending on your use case, another option is to modify the flash descriptor to allow the host to write to the ME region. However Intel recommends locking the ME region so that reads and writes to the ME region from the host are not allowed. Please also see https://flashrom.org/ME#Suggested_workarounds for additional guidance. From: Ocean Huang via flashrom Sent: Wednesday, February 26, 2020 5:20 AM To: flashrom@flashrom.org Subject: [flashrom] Flashrom tool failed on the Intel Bakerville platform(CPU:SKY-D) Hi Vendor: We have some issue when using flashrom tool update BIOS & ME firmware on the Intel Bakeville platform, you can refer to the below error log, could you please help give some comments or suggestions about this issue? [root@localhost flashrom-v1.1]# ./flashrom -p internal -w CBR.1.00.01.bin flashrom v1.1 on Linux 3.10.0-957.el7.x86_64 (x86_64) flashrom is free software, get the source code at https://flashrom.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org=DwMFaQ=5VD0RTtNlTh3ycd41b3MUw=4-bAjA7rj5_lsAnGYQCM_w=532SYzVno7CxakMNFHC-ELomxuPqcWKaBcM1kqjV6qc=lw-AUImht5ouHueP-_e7nSmbqEDP4RPihF9Y8o5_70A=> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel C620 Series Chipset Supersku". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom@flashrom.org<mailto:flashrom@flashrom.org> including a verbose (-V) log. Thank you! Enabling flash write... SPI Configuration is locked down. FREG2: Management Engine region (0x3000-0x00a15fff) is locked. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see https://flashrom.org/ME<https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org_ME=DwMFaQ=5VD0RTtNlTh3ycd41b3MUw=4-bAjA7rj5_lsAnGYQCM_w=532SYzVno7CxakMNFHC-ELomxuPqcWKaBcM1kqjV6qc=X8yqTjX2TTNy16DkSDCTNXyOc8FAG1Yfn126AxBHqVI=> for details. At least some flash regions are read protected. You have to use a flash layout and include only accessible regions. For write operations, you'll additionally need the --noverify-all switch. See manpage for more details. Enabling hardware sequencing because some important opcode is locked. OK. Found Programmer flash chip "Opaque flash chip" (32768 kB, Programmer-specific) mapped at physical address 0x. Reading old flash chip contents... Transaction error between offset 0x3000 and 0x303f (= 0x3000 + 63)! FAILED. [root@localhost flashrom-v1.1]# ./flashrom -p internal -r 111.bin --ifd -i bios flashrom v1.1 on Linux 3.10.0-957.el7.x86_64 (x86_64) flashrom is free software, get the source code at https://flashrom.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org=DwMFaQ=5VD0RTtNlTh3ycd41b3MUw=4-bAjA7rj5_lsAnGYQCM_w=532SYzVno7CxakMNFHC-ELomxuPqcWKaBcM1kqjV6qc=lw-AUImht5ouHueP-_e7nSmbqEDP4RPihF9Y8o5_70A=> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel C620 Series Chipset Supersku". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom@flashrom.org<mailto:flashrom@flashrom.org> including a verbose (-V) log. Thank you! Enabling flash write... SPI Configuration is locked down. FREG2: Management Engine region (0x3000-0x00a15fff) is locked. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see https://flashrom.org/ME<https://urldefense.proofpoint.com/v2/url?u=https-3A__flashrom.org_ME=DwMFaQ=5VD0RTtNlTh3ycd41b3MUw=4-bAjA7rj5_lsAnGYQCM_w=532SYzVno7CxakMNFHC-ELomxuPqcWKaBcM1kqjV6qc=X8yqTjX2TTNy16DkSDCTNXyOc8FAG1Yfn126AxBHqVI=> for details. At least some flash regions are read protected. You have to use a flash layout and include only accessible regions. For write operations, you'll additionally need the --noverify-all switch. See manpage for more details. Enabling hardware sequencing because some important opcode is locked. OK. Found Programmer flash chip "Opaque flash chip" (32768 kB, Programmer-specific) mapped at physical address 0x. Reading ich descriptor... done. Using region: "bios&q
