Re: [flashrom] FLASHROM fails on my AM1 Kabinis with

2018-10-07 Thread awokd via flashrom

Branko Badrljica wrote on 10/5/18 12:55 PM:

I'm in dire need te reflash a couple of BIOS chips.


Unfotunately, all my boards which I used to use for this purpose are 
rebellign against me.



I have a couple of Kabinis ( Athlon 5370) on cheap AM1 boards and have 
noticed that "flashrom -p internal" fails on each one with


"Found chipset AMD FCH"

"Enabling flash write... ERROR: State of SpiAccesMacRomEn or 
SpiHostAccessRomEn prohibits full access"


At first, I thot that I might have miscompiled something in the kernel 
or that flashrom doesn't jive with my Hardened Gentoo or something like 
that. So I used Kali Linux and burned it toUSB stick ( it has flasrom 
packaged).



With the exactly the same end result.

I've tried git version and versions 0.98 and 0.99. Older one ( 0.96 ?) 
compained that it doesn't know Kabini's chipset...


THis HW used to work with flashrom. What changed ?


Looks like it would generate a different error, but you might need 
iomem=relaxed in the kernel options.



___
flashrom mailing list
flashrom@flashrom.org
https://mail.coreboot.org/mailman/listinfo/flashrom


Re: [flashrom] FLASHROM fails on my AM1 Kabinis with

2018-10-05 Thread Branko Badrljica

Here it is.


Stefan Tauner je 5. 10. 2018 ob 15:06 napisal:

On Fri, 5 Oct 2018 14:55:32 +0200
Branko Badrljica  wrote:


I'm in dire need te reflash a couple of BIOS chips.


Unfotunately, all my boards which I used to use for this purpose are
rebellign against me.


I have a couple of Kabinis ( Athlon 5370) on cheap AM1 boards and have
noticed that "flashrom -p internal" fails on each one with

"Found chipset AMD FCH"

"Enabling flash write... ERROR: State of SpiAccesMacRomEn or
SpiHostAccessRomEn prohibits full access"

At first, I thot that I might have miscompiled something in the kernel
or that flashrom doesn't jive with my Hardened Gentoo or something like
that. So I used Kali Linux and burned it toUSB stick ( it has flasrom
packaged).


With the exactly the same end result.

I've tried git version and versions 0.98 and 0.99. Older one ( 0.96 ?)
compained that it doesn't know Kabini's chipset...

THis HW used to work with flashrom. What changed ?

Hi,

possibly a firmware update that set one of the two bits mentioned by
flashrom's output. Can you please post a complete verbose log file (e.g.
by adding "-o logfile.txt" to the command line)?



flashrom p1.0-123-g1a7fb6e on Linux 4.18.12-gentoo (x86_64)
flashrom was built with libpci 3.5.6, GCC 8.2.0, little endian
Command line (4 args): flashrom -p internal -o /flashrom_logfile.txt
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.
DMI string chassis-type: "Desktop"
DMI string system-manufacturer: "ASUS"
DMI string system-product-name: "All Series"
DMI string system-version: "System Version"
DMI string baseboard-manufacturer: "ASUSTeK COMPUTER INC."
DMI string baseboard-product-name: "AM1M-A"
DMI string baseboard-version: "Rev X.0x"
Found ITE Super I/O, ID 0x8623 on port 0x2e
Found chipset "AMD FCH" with PCI ID 1022:780e.
Enabling flash write... SPI base address is at 0xfec1
Trying to determine the generation of the SPI interface... Yangtze detected.
SpiRomEnable=1, RouteTpm2Sp=0, PrefetchEnSPIFromIMC=0, PrefetchEnSPIFromHost=1
(0x6f4c2105) SpiArbEnable=1, IllegalAccess=0, SpiAccessMacRomEn=1, 
SpiHostAccessRomEn=0, ArbWaitCount=7, SpiBusy=0
ERROR: State of SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access.
ROM strap override is not active
PROBLEMS, continuing anyway
Super I/O ID 0x8623 is not on the list of flash-capable controllers.
The following protocols are supported: LPC, FWH.
Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, 
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xff, id2 0xff, 
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, 
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, 
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 
parity violation, id1 is normal flash content, id2 is normal flash 

Re: [flashrom] FLASHROM fails on my AM1 Kabinis with

2018-10-05 Thread Stefan Tauner
On Fri, 5 Oct 2018 14:55:32 +0200
Branko Badrljica  wrote:

> I'm in dire need te reflash a couple of BIOS chips.
> 
> 
> Unfotunately, all my boards which I used to use for this purpose are 
> rebellign against me.
> 
> 
> I have a couple of Kabinis ( Athlon 5370) on cheap AM1 boards and have 
> noticed that "flashrom -p internal" fails on each one with
> 
> "Found chipset AMD FCH"
> 
> "Enabling flash write... ERROR: State of SpiAccesMacRomEn or 
> SpiHostAccessRomEn prohibits full access"
> 
> At first, I thot that I might have miscompiled something in the kernel 
> or that flashrom doesn't jive with my Hardened Gentoo or something like 
> that. So I used Kali Linux and burned it toUSB stick ( it has flasrom 
> packaged).
> 
> 
> With the exactly the same end result.
> 
> I've tried git version and versions 0.98 and 0.99. Older one ( 0.96 ?) 
> compained that it doesn't know Kabini's chipset...
> 
> THis HW used to work with flashrom. What changed ?

Hi,

possibly a firmware update that set one of the two bits mentioned by
flashrom's output. Can you please post a complete verbose log file (e.g.
by adding "-o logfile.txt" to the command line)?

-- 
Kind regards/Mit freundlichen Grüßen, Stefan Tauner

___
flashrom mailing list
flashrom@flashrom.org
https://mail.coreboot.org/mailman/listinfo/flashrom