Peter, It is an easy answer to say that RAM is not initialized correctly! While I am pretty sure that RAM is OK, I have an assembly language which can verify that.
Peter, you do not make the problem clear. The problem is that the registers of RAM controller are initialized with some correct values, but the Intel board had 82810 as its GMCH.
My GMCH is 82815. I guess Coreboot at some point extracts some information from the config registers of GMCH and sets some variables and this is exactly the point which the problem occurs.
I do not have enough information about the source code of Coreboot but logically where Coreboot is specifying the top of memory? Coreboot needs to know the size of memory, right? Where it is specified?
Does my words make sense?
Regards
On Tue, Feb 7, 2012 at 6:58 PM, Peter Stuge peter@stuge.se wrote:
ali hagigat wrote:
Stage: loading fallback/coreboot_ram @ 0x100000 (180224 bytes), entry @ 0x100000 Stage: done loading. Jumping to image.
..
When it wants to do a jump inside cbfs_and_run_core(), the processor halts some how.
RAM is not initialized correctly.
//Peter
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot