I'm planning to build this for an ASROCK IMB-180 this week or next.
I previously had trouble booting until Wim Vervoon wvervoorn@eltan.com suggested that it might be dual-ranked dimms. Replacing the dual-rank dimm with a single rank did the trick.
I'll test both configurations with the new code and post the results.
Mark Mason Engineering Design Team
Send coreboot mailing list submissions to coreboot@coreboot.org
To subscribe or unsubscribe via the World Wide Web, visit http://www.coreboot.org/mailman/listinfo/coreboot or, via email, send a message with subject or body 'help' to coreboot-request@coreboot.org
You can reach the person managing the list at coreboot-owner@coreboot.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of coreboot digest..."
Today's Topics:
1. Re: Flash access on ASUS F2A85 variants (Rudolf Marek) 2. Re: Flash access on ASUS F2A85 variants (Rudolf Marek) 3. Is there a payload to test SeaBIOS? BIOS mouse interface? (Paul Menzel) 4. [RFH] Please test latest cleanups on AGESA boards (Paul Menzel)
Message: 1 Date: Sun, 04 May 2014 13:56:03 +0200 From: Rudolf Marek r.marek@assembler.cz To: coreboot@coreboot.org Cc: flashrom@flashrom.org Subject: Re: [coreboot] Flash access on ASUS F2A85 variants Message-ID: 53662AD3.3030304@assembler.cz Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Stefan,
I could not find any details but the error message one receives: "ERROR: State of SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access."
Found ITE Super I/O, ID 0x8603 on port 0x2e Found chipset "AMD FCH" with PCI ID 1022:780e. Enabling flash write... SPI base address is at 0xfec10000 Hudson-2/3/4 detected. SpiRomEnable=1, PrefetchEnSPIFromIMC=0, PrefetchEnSPIFromHost=1 (0x6f4c2105) SpiArbEnable=1, SpiAccessMacRomEn=1, SpiHostAccessRomEn=0, ArbWaitCount=7, SpiBridgeDisable=1, SpiBusy=0 ERROR: State of SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access.
If I read the documentation of SpiHostAccessRomEn correctly then it should not bother us at all. It indicates it the ethernet firmware can access the host partition of the flash chip. If however the other bit (SpiAccessMacRomEn) is reset to 0 then we indeed have a problem.
Yes I tried to disable the check and got following (I was testing BIOS version 6502)
Found Winbond flash chip "W25Q64.V" (8192 kB, SPI). This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). coreboot last image size (not ROM size) is 8388608 bytes. Manufacturer: ASUS Mainboard ID: F2A85-M Reading old flash chip contents... FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. FAILED.
Can someone please send me the verbose output of flashrom to confirm which one it is? And I am also looking for testers with these boards, because I think the abort on SpiHostAccessRomEn is a bug in flashrom.
Hm looks like something will happen, becuase it does not work. This board has external ethernet chip. So the only master accessing the chip could be USB 3.0 firmware. But, this works fine with coreboot and also removing the XHCI drivers did not help.
Maybe some protection bits are set elsewhere.
This is dump of MMIO space:
hexdump -C a.bin 00000000 05 21 4c 6f 00 00 00 00 00 06 00 00 00 70 00 02 |.!Lo.........p..| 00000010 06 20 04 04 06 04 9f 05 03 0b 0a 02 ff 88 00 3b |. .............;| 00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
It looks like (look to 48751 Rev 3.00 - May 30, 2013 BKDG for AMD Family 16h Models 00h-0Fh Processors)
SPIx1D Alt_SPI_CS 0x88
SpiProtectEn0. IF (SPIx1D[SpiProtectLock]==1) THEN Read-only. ELSE Read-write. ENDIF.
Reset: 0. 1=Enable SPI read/write protection ranges specified by D14F3x[5C,58,54,50].
Funny is that the SPiProtectLock is not set to 1
00:14.3 ISA bridge: Advanced Micro Devices [AMD] Hudson LPC Bridge (rev 11) 00: 22 10 0e 78 0f 00 20 02 11 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 27 85 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 04 00 00 00 d5 ff 03 ff 07 ff 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
And all protection ranges are 0 anyway...
60: 00 00 00 00 30 02 00 00 00 00 0f 00 00 ff ff ff 70: 67 45 23 00 00 00 00 00 9c 00 00 00 05 0b 00 00 80: 08 00 03 a8 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 02 00 c1 fe 2f 01 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 e9 45 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 17 00 82 ff d0: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
And clearing the bit 4 of 1d also did not help. So it must be something else elsewhere.
I hope this is enough information for the start ;)
Thanks Rudolf
Message: 2 Date: Sun, 04 May 2014 21:38:58 +0200 From: Rudolf Marek r.marek@assembler.cz To: coreboot@coreboot.org Cc: flashrom@flashrom.org Subject: Re: [coreboot] Flash access on ASUS F2A85 variants Message-ID: 53669752.8060200@assembler.cz Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Stefan,
I just tried with v6402 which is open:
00:14.3 ISA bridge: Advanced Micro Devices [AMD] Hudson LPC Bridge (rev 11) 00: 22 10 0e 78 0f 00 20 02 11 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 27 85 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 04 00 00 00 d5 ff 03 ff 07 ff 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 30 02 00 00 00 00 0f 00 00 ff ff ff 70: 67 45 23 00 00 00 00 00 9c 00 00 00 05 0a 00 00 80: 08 00 03 a8 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 02 00 c1 fe 2f 01 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 e9 45 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 17 00 82 ff d0: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ruiktest ~ # hexdump -C a.bin 00000000 05 21 cc 6f 00 00 00 00 00 00 00 00 00 70 00 02 |.!.o.........p..| 00000010 06 20 04 04 06 04 9f 05 03 0b 0a 02 ff 88 00 3b |. .............;| 00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
The newer (locked) version from last email:
hexdump -C a.bin 00000000 05 21 4c 6f 00 00 00 00 00 06 00 00 00 70 00 02 |.!Lo.........p..| 00000010 06 20 04 04 06 04 9f 05 03 0b 0a 02 ff 88 00 3b |. .............;| 00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
It looks that the the SPI CMD 06 is now restricted CMD for MAC and SPIhostaccesRomEn is clear.
I tried to boot with open version v6402 and then just clear the SpiHostAccessRomEn without setting any other bits and I receive failure even for read:
./flashrom/flashrom -V -p internal -r bios_open.bin
Found Winbond flash chip "W25Q64.V" (8192 kB, SPI). This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). Reading flash... FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Read operation failed! FAILED.
Yes it looks like something is happening with flashrom / controller if SpiHostAccessRomEn is cleared.
Thanks Rudolf
Message: 3 Date: Mon, 05 May 2014 00:54:55 +0200 From: Paul Menzel paulepanter@users.sourceforge.net To: coreboot@coreboot.org Subject: [coreboot] Is there a payload to test SeaBIOS? BIOS mouse interface? Message-ID: 1399244095.7732.188.camel@mattotaupa Content-Type: text/plain; charset="utf-8"
Dear coreboot folks,
on the ASRock E350M1 [1] with coreboot and SeaBIOS payload, starting KolibriOS from GRUB 2 on the hard drive, it loads fine but neither keyboard nor mouse work. This is true for USB and PS/2 [2].
Do you know of a payload I can use to test SeaBIOS? BIOS mouse interface?
Thanks,
Paul
[1] http://www.coreboot.org/Board:asrock/e350m1 [2] http://bugs.kolibrios.org/view.php?id=84