[coreboot] "FCH SPI: Too much to write" on KGPE-D16

Iru Cai mytbk920423 at gmail.com
Fri Jan 6 16:02:45 CET 2017


Hi Timothy,

On 2017年01月06日 01:14, Timothy Pearson wrote:
> On 01/05/2017 04:33 AM, Iru Cai wrote:
> > Hello,
>
> > I've set up a computer with Asus KGPE-D16 recently. I use an Winbond
> > W25Q64.V 8M flash chip and tested with this config with only ROM size
> > changed:
>
> >
> https://review.coreboot.org/gitweb/cgit/board-status.git/tree/asus/kgpe-d16/4.5-759-gab8f7d3/2017-01-04T21_18_55Z/config.short.txt
>
> > And it can boot to my OS on disk. However, after I enabled the serial
> > console, I can only see:
> > "FCH SPI: Too much to write. Does your SPI chip driver use
> > spi_crop_chunk()?"
>
> Do you see any other messages at all from a cold start (i.e. AC power
> removed from the system, then reapplied after 15 seconds while the
> serial console is being logged)?
>

It seems that as long as I enable serial console output, system cannot
boot. Besides the SPI thing, I can also get stuck on some place when
booting. Now I post these logs in the attachment. Both logs are logged
when I'm using a 2MB flash chip.

Iru

> I have not personally tested the 8M chips; it could be that there is an
> issue with coreboot's generic driver for those devices.  I know it's not
> a general issue with large Flash chips since the 16M chips work fine.
>
> Thanks!
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: kgpe-spi.log
Type: text/x-log
Size: 837122 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20170106/f3c46427/attachment-0002.log>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kgpe-stuck.log
Type: text/x-log
Size: 296799 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20170106/f3c46427/attachment-0003.log>


More information about the coreboot mailing list