[coreboot] ASROCK e350m1 ASSERTION FAIL on CPU capability detection / No serial

Vibrans, Frank Frank.Vibrans at amd.com
Tue Aug 9 19:06:54 CEST 2011

Hi Andrew,

The assert failed because the structure involved didn’t pick up its default value out of PlatformInstall.h which is included in buildOpts.c.  I’m suspicious of the hard path to the Family14 code in the Makefile.inc, but I don’t know that that is the definitive failure.  You might also try uncommenting line 196 in you r buildOpts.c file since that is the particular option that is not getting set.  That should get you going.


From: Andrew Bolster [mailto:me at andrewbolster.info]
Sent: Tuesday, August 09, 2011 4:03 AM
To: coreboot at coreboot.org
Cc: Vibrans, Frank
Subject: ASROCK e350m1 ASSERTION FAIL on CPU capability detection / No serial

Morning all;
Quick bug report on the 'latest' master (commit ebbfbd59115c1a8ccf380041aecd6e903dcf925a)
Build's fine but on boot:

BSP Family_Model: 00500f10
cpu_init_detectedx = 00000000
Got past sb800_early_setup
BSP Family_Model: 00500f10
cpu_init_detectedx = 00000001
Got past sb800_early_setup
ASSERTION FAILED: file 'src/vendorcode/amd/agesa/f14/Proc/CPU/Table.c',  line 1388

Also, as florz already mentioned, applying the relevant patch (http://review.coreboot.org/#change,139), the serial port is dead.

Andrew Bolster

No trees were killed to send this message, but a large number of electrons were terribly inconvenienced.I enjoy the massacre of ads. This sentence will slaughter ads without a messy bloodbath.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20110809/1660eb33/attachment.html>

More information about the coreboot mailing list