[coreboot] How to get correct memory params for FSP
rene.shuster at bcsemail.org
Tue Nov 6 18:30:45 CET 2018
Faint memories... are you the ISO recorder author from 15 years ago?
On Tue, Nov 6, 2018 at 12:23 PM Alex Feinman <alexfeinman at hotmail.com>
> The two major issues with bringing up the memory subsystem on a new board
> are SPD parameters and DQ/DQS layout
> Specifically, if you look at the apollolake rvp subtree, you can see a
> whole bunch of parameters being set in romstage.c. Some of it is fairly
> straightforward. Swizzling tables are not and require you to be able to
> read schematic (and have access to it in the first place)
> Obviously, the problem could be elsewhere. I would start with enabling MRC
> debug and perhaps posting the MRC output
> *From:* coreboot <coreboot-bounces at coreboot.org> on behalf of Alexey
> Borovikov via coreboot <coreboot at coreboot.org>
> *Sent:* Saturday, November 3, 2018 5:38 AM
> *To:* coreboot at coreboot.org
> *Subject:* [coreboot] How to get correct memory params for FSP
> I port the Coreboot to a board with an SOC Intel Atom E3845 and use FSP
> for the Baytrail family. The result - postcode is 0x2A. From the
> descriptions on the Internet, I understand that the problem is in the
> incorrect memory parameters.
> Question: are there any utilities or methods that will help to get the
> correct memory parameters when working a regular BIOS from Linux or Windows
> Many thanks!
> coreboot mailing list: coreboot at coreboot.org
Tech III * AppControl * Endpoint Protection * Server Maintenance
Buncombe County Schools Technology Department Network Group
ComicSans Awareness Campaign <http://comicsanscriminal.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the coreboot