All,
I have an Asus A88XM-E, and I am trying to install Coreboot on it.  

1 ) The chip that came with the board says "GD25Q64(B)" (8192 kB, SPI). I think 
the chip definitely broken somehow. Everytime I tried to flashrom, it says

Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, 
Found=0x00, failed byte count from 0x00000000-0x00000fff: 0xd0c

ERASE FAILED!

when I tried sudo flashrom -w build/coreboot.rom --programmer ch341a_spi, it 
says

Verifying flash... FAILED at 0x00000000! Expected=0x5f, Found=0xff, failed byte 
count from 0x00000000-0x007fffff: 0xb5

Your flash chip is in an unknown state.

I am having a hard time flashing back to original bios as well. Can I buy 
W25Q64FVAIG to replace? The chip says GD25B64BP1G . Is that caused by using 5 V 
to be broken? I only performed flashrom -w and flashrom -r .

2) For configuration, I copied this configuration:

https://review.coreboot.org/cgit/board-status.git/tree/asus/a88xm-e/4.12-3285-ga2118c7b54/2020-10-15T00_01_02Z/config.short.txt?

to .config and added the board. I have exported the vga bios from Linux using: 
cp /sys/devices/pci0000:00/0000:00:01.0/rom vgabios.bin .

The above config does not work with make, it tries to go to a webpage for 
secondary payload, and that webpage is changed. Removing those two lines 
CONFIG_COREINFO_SECONDARY_PAYLOAD=y && CONFIG_TINT_SECONDARY_PAYLOAD=y will let 
me build the rom. When I do sudo flashrom -w build/coreboot.rom --programmer 
ch341a_spi, it sometimes says write done:

Erasing and writing flash chip... Erase/write done.

Verifying flash... FAILED at 0x00000000! Expected=0x5f, Found=0xff, failed byte 
count from 0x00000000-0x007fffff: 0xb5

Your flash chip is in an unknown state.

When I boot with Coreboot, I see a black screen. I renamed vgabios.bin to 
pci1002,990c.rom, and I put that file in the ~/Coreboot/ folder.

Thanks for helping out,
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

Reply via email to