Coreboot FSP fails to initialize RAM - "Configuration not in POR table"

[Naveen Chaudhary]

I am using Faceboot Watson image (with no code changes) on a custom BroadwellDE based motherboard. Current the FSP_FSP_INIT api never returns back. I enabled the FSP logs and got the following messages :

bootMode = NormalBoot
subBootMode = ColdBoot
Dispatch Slaves -- Started
Dispatch Slaves - 0ms
Promote Warning Exception List -- Started
Promote Warning Exception List - 0ms
Initialize Throttling Early -- Started
Initialize Throttling Early - 0ms
Detect DIMM Configuration -- Started
Checkpoint Code: Socket 0, 0xB0, 0x00, 0x0000
N0: IMC 0 SMB Clock Period = 0x1F2C
Socket | Channel | DIMM |  Bus Segment | SMBUS Address
-------|---------|------|--------------|--------------
   0   |     0   |   0  |      0       |       0      - Present
N0.C0.D0: NVDIMM:N(380)=0x0
   0   |     0   |   1  |      0       |       1      - Not Present
   0   |     1   |   0  |      0       |       2      - Present
N0.C1.D0: NVDIMM:N(380)=0x0
   0   |     1   |   1  |      0       |       3      - Not Present
Entering no zone 1
Detect DIMM Configuration - 238ms
Get Slave Data -- Started
Get Slave Data - 0ms
Check POR Compatibility -- Started
primaryWidthDDR4: 1, rowBitsDDR4: 16, columnBitsDDR4: 10, bankGroupsDDR4: 4
primaryWidthDDR4: 1, rowBitsDDR4: 16, columnBitsDDR4: 10, bankGroupsDDR4: 4
Unknown DIMM population
Check POR Compatibility - 17ms
Initialize DDR Clocks -- Started
Checkpoint Code: Socket 0, 0xB1, 0x00, 0x0000
Configuration not in POR table!
Memory Configuration: Vdd = 3, procType = 0x5066, socketType = 3, dramType = 12, spc = 2, dpc = 1, dimmType = 5, numRanks = 2
GetPORDDRFreq returns ddrfreq = 255
N0.C0: FPT: DisableChannel()
N0.C0.D0: FPT: DisableDIMM()

A warning has been logged! Warning Code = 0x7, Minor Warning Code = 0x8, Data = 0xFFFF
S0 Ch0

Warning upgraded to Fatal Error!

FatalError: SocketId = 0 registered Major Code = 0x 7, Minor Code = 0x 8

What does "Configuration not in POR table mean? Does this mean that FSP can no longer initialize my DRAM automatically? If yes, what's the solution here? Or shall I try tweaking other settings such as MemEccSupport, MemDdrMemoryType, etc.

Regards,
Naveen