Thank you for advice. I followed the instructions of this change, and after fixing a few compilation errors (had to replace a few %x with %llu at printf's) - using the same .config - I got a ROM which is unbootable! Maybe because I don't have AMD HDT Debugger, and it should've been connected to some usually-not-soldered header for this ROM to boot?
Perhaps I can manually redirect these IDS prints to a standard coreboot log - if that will give some useful info. Or I could dive into AGESA and replace all DDR1333 stuff with a DDR1866 one, to force it running as 1866MHz CL9 - since that "#define BLDCFG_MEMORY_CLOCK_SELECT" seemingly doesn't work for some reason.
Do you have any other ideas to fix this "turtle RAM" AMD 16h problem?
Best regards, Mike Banon
On Fri, Jul 5, 2019 at 8:44 AM Kyösti Mälkki firstname.lastname@example.org wrote:
On Wed, Jul 3, 2019 at 8:54 PM Mike Banon email@example.com wrote:
A pair of 1866MHz CL9 RAM modules* runs only as 1333MHz CL9 on 16h AM1I-A with coreboot is installed, but worked faster when a proprietary UEFI was installed. To fix this "turtle RAM" coreboot problem I tried to play with buildOpts.c - https://review.coreboot.org/c/coreboot/+/33920 , but the things like "#define BLDCFG_MEMORY_CLOCK_SELECT DDR1866_FREQUENCY" sadly did not help.
Any ideas how to improve the RAM speeds? How I can force this RAM to run faster?
Maybe AGESA debugging / IDS tracing is of some assistance? I have not tried it for a while, though.