Hello, 
I have recently received a thinkpad T14s Gen 3 AMD (Ryzen 6850U) and given 
flashrom a try. However, the winbond chip inside wasn't detected. I wonder if 
the team at flashrom can work around it. For more infomation, I have attached 
the log as well as the images of the motherboard : 
https://postimg.cc/gallery/MqXWhHv. 



Thanks,
B83C
flashrom v1.2 on Linux 6.0.0+ (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
No DMI table found.
Found chipset "AMD FP4".
Enabling flash write... PROBLEMS, continuing anyway
========================================================================
You may be running flashrom on an unknown laptop. We could not
detect this for sure because your vendor has not set up the SMBIOS
tables correctly. Some internal buses have been disabled for
safety reasons. You can enforce using all buses by adding
  -p internal:laptop=this_is_not_a_laptop
to the command line, but please read the following warning if you
are not sure.

No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
flashrom v1.2 on Linux 6.0.0+ (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
No DMI table found.
Found chipset "AMD FP4".
Enabling flash write... Disabling read write protection of flash addresses from 
0xfffff800 to 0x0007f7ff failed.
Disabling read write protection of flash addresses from 0xfffff800 to 
0x0007f7ff failed.
Disabling read write protection of flash addresses from 0xfffff800 to 
0x0007f7ff failed.
Disabling read write protection of flash addresses from 0xfffff800 to 
0x0007f7ff failed.
FCH device found but SMBus revision 0x71 does not match known values.
Please report this to flashrom@flashrom.org and include this log and
the output of lspci -nnvx, thanks!.
Could not determine chipset generation.PROBLEMS, continuing anyway
========================================================================
You may be running flashrom on an unknown laptop. We could not
detect this for sure because your vendor has not set up the SMBIOS
tables correctly. Some internal buses have been disabled for
safety reasons. You can enforce using all buses by adding
  -p internal:laptop=this_is_not_a_laptop
to the command line, but please read the following warning if you
are not sure.

Laptops, notebooks and netbooks are difficult to support and we
recommend to use the vendor flashing utility. The embedded controller
(EC) in these machines often interacts badly with flashing.
See the manpage and https://flashrom.org/Laptops for details.

If flash is shared with the EC, erase is guaranteed to brick your laptop
and write may brick your laptop.
Read and probe may irritate your EC and cause fan failure, backlight
failure and sudden poweroff.
You have been warned.
========================================================================
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
flashrom v1.2 on Linux 6.0.0+ (x86_64)
flashrom is free software, get the source code at https://flashrom.org

More than one operation specified. Aborting.
Please run "flashrom --help" for usage info.
flashrom v1.2 on Linux 6.0.0+ (x86_64)
flashrom is free software, get the source code at https://flashrom.org

flashrom was built with libpci 3.8.0, GCC 13.0.0 20220922 (experimental), 
little endian
Command line (5 args): flashrom -V -p internal -r test
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Initializing internal programmer
/sys/class/mtd/mtd0 does not exist
No coreboot table found.
Using Internal DMI decoder.
No DMI table found.
W836xx enter config mode worked or we were already in config mode. W836xx leave 
config mode had no effect.
Active config mode, unknown reg 0x20 ID: 00.
W836xx enter config mode worked or we were already in config mode. W836xx leave 
config mode had no effect.
Active config mode, unknown reg 0x20 ID: 20.
Found chipset "AMD FP4" with PCI ID 1022:790e.
Enabling flash write... Chipset read write protected flash from 0xfffff800 to 
0x0007f7ff, unlocking...Disabling read write protection of flash addresses from 
0xfffff800 to 0x0007f7ff failed.
Chipset read write protected flash from 0xfffff800 to 0x0007f7ff, 
unlocking...Disabling read write protection of flash addresses from 0xfffff800 
to 0x0007f7ff failed.
Chipset read write protected flash from 0xfffff800 to 0x0007f7ff, 
unlocking...Disabling read write protection of flash addresses from 0xfffff800 
to 0x0007f7ff failed.
Chipset read write protected flash from 0xfffff800 to 0x0007f7ff, 
unlocking...Disabling read write protection of flash addresses from 0xfffff800 
to 0x0007f7ff failed.
SPI base address is at 0xffffffe0
FCH device found but SMBus revision 0x71 does not match known values.
Please report this to flashrom@flashrom.org and include this log and
the output of lspci -nnvx, thanks!.
Could not determine chipset generation.ROM strap override is active: SPI
PROBLEMS, continuing anyway
========================================================================
You may be running flashrom on an unknown laptop. We could not
detect this for sure because your vendor has not set up the SMBIOS
tables correctly. Some internal buses have been disabled for
safety reasons. You can enforce using all buses by adding
  -p internal:laptop=this_is_not_a_laptop
to the command line, but please read the following warning if you
are not sure.

Laptops, notebooks and netbooks are difficult to support and we
recommend to use the vendor flashing utility. The embedded controller
(EC) in these machines often interacts badly with flashing.
See the manpage and https://flashrom.org/Laptops for details.

If flash is shared with the EC, erase is guaranteed to brick your laptop
and write may brick your laptop.
Read and probe may irritate your EC and cause fan failure, backlight
failure and sudden poweroff.
You have been warned.
========================================================================
The following protocols are supported: None.
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
Restoring PCI config space for 00:14:3 reg 0x5c
Restoring PCI config space for 00:14:3 reg 0x58
Restoring PCI config space for 00:14:3 reg 0x54
Restoring PCI config space for 00:14:3 reg 0x50
_______________________________________________
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

Reply via email to