- The attached diff sets up a config for the Advantech gx533 eval board I have. - It also adds some verbosity and pass fail logic to the ram test. Since the ram test always printed "DRAM verified" regardless of pass or fail I worked for a long time trying to understand why I died when I jumped to RAM. When the real reason was that my RAM is hosed.
So now if the RAM test fails then its _obvious_.
Is 256 failed attempts before aborting really necessary? I mean > 1 is problem. Will anyone object to making the abort number much smaller?
The changes are trivial so unless someone has objections I'll commit.
Ok on to my debugging. So my RAM isn't playing nice. From the log you can see that Bit 8 is not clearing. Any suggestions on what register I should go tweak on to tune up my RAM?
LinuxBIOS-1.1.8.0Fallback Sat Mar 25 03:09:37 CST 2006 starting... reboot from BIOS reset done cs5535 early Cpu core is 0000014e reboot from BIOS reset done pll_reset Ram1.00 Ram2.00 Ram3 Ram4 Done sdram_initialize Disable watchdog ffCAN NOT READ SUPERIO VID ff:ff Testing DRAM : 00000000-00004000 DRAM fill: 00000000-00004000 00000000 00004000 DRAM filled DRAM verify: 00000000-00004000 00000000 Fail: @0x00000000 Read value=0x00001000 Fail: @0x00000004 Read value=0x00001004 Fail: @0x00000008 Read value=0x00001008 Fail: @0x0000000c Read value=0x0000100c Fail: @0x00000010 Read value=0x00001010 Fail: @0x00000014 Read value=0x00001014 Fail: @0x00000018 Read value=0x00001018 Fail: @0x0000001c Read value=0x0000101c Fail: @0x00000020 Read value=0x00001020 <snip> Fail: @0x000003fc Read value=0x000013fc Fail: @0x00000400 Read value=0x00001400 Aborting. 00000400 DRAM did _NOT_ verify! Done. Testing DRAM : 00020000-00024000 DRAM fill: 00020000-00024000 00020000 00024000 DRAM filled DRAM verify: 00020000-00024000 00020000 Fail: @0x00020000 Read value=0x00021000 Fail: @0x00020004 Read value=0x00021004 Fail: @0x00020008 Read value=0x00021008 Fail: @0x0002000c Read value=0x0002100c Fail: @0x00020010 Read value=0x00021010 Fail: @0x00020014 Read value=0x00021014 Fail: @0x00020018 Read value=0x00021018 Fail: @0x0002001c Read value=0x0002101c <snip> Fail: @0x000203f0 Read value=0x000213f0 Fail: @0x000203f4 Read value=0x000213f4 Fail: @0x000203f8 Read value=0x000213f8 Fail: @0x000203fc Read value=0x000213fc Fail: @0x00020400 Read value=0x00021400 Aborting. 00020400 DRAM did _NOT_ verify! Done. Testing DRAM : 00000000-000a0000 DRAM fill: 00000000-000a0000 00000000 00010000 00020000 00030000 00040000 00050000 00060000 00070000 00080000 00090000 000a0000 DRAM filled DRAM verify: 00000000-000a0000 00000000 Fail: @0x00000000 Read value=0x00001000 Fail: @0x00000004 Read value=0x00001004 Fail: @0x00000008 Read value=0x00001008 Fail: @0x0000000c Read value=0x0000100c Fail: @0x00000010 Read value=0x00001010 Fail: @0x00000014 Read value=0x00001014 Fail: @0x00000018 Read value=0x00001018 Fail: @0x0000001c Read value=0x0000101c Fail: @0x00000020 Read value=0x00001020 <snip> Fail: @0x000003f0 Read value=0x000013f0 Fail: @0x000003f4 Read value=0x000013f4 Fail: @0x000003f8 Read value=0x000013f8 Fail: @0x000003fc Read value=0x000013fc Fail: @0x00000400 Read value=0x00001400 Aborting. 00000400 DRAM did _NOT_ verify! Done. Copying LinuxBIOS to ram. Jumping to LinuxBIOS.
-- Richard A. Smith
On Sat, 2006-03-25 at 03:26 -0600, Richard Smith wrote:
- The attached diff sets up a config for the Advantech gx533 eval board I have.
- It also adds some verbosity and pass fail logic to the ram test.
Since the ram test always printed "DRAM verified" regardless of pass or fail I worked for a long time trying to understand why I died when I jumped to RAM. When the real reason was that my RAM is hosed.
Are you sure the value to set to msr 0x20000018 and 0x20000019 are correct? The value is for the rumba board with 256MB DDR.
-
Li-Ta Lo -
Richard Smith