Hi, I'm new here. I've installed U-Boot on my brand new Mini2440(1GB). So far so good :-) Now I've tried mtest (output is included). Writing zeroes throws some errors. Writing FFs hangs then. Is there a defect on my dram? Or is there any problem with U-Boot mtest? Any advise? Kind Regards Dirk U-Boot 1.3.2-mini2440 (Jan 12 2011 - 17:16:16) I2C: ready DRAM: 64 MB NOR Flash not found. Use hardware switch and 'flinit' Flash: 0 kB NAND: 1024 MiB Found Environment offset in OOB.. USB: S3C2410 USB Deviced In: serial Out: serial Err: serial MAC: 08:08:11:18:12:27 Hit any key to stop autoboot: 0 MINI2440 # mtest Pattern 00000000 Writing... Reading... Mem error @ 0x33D5FB2C: found 00000001, expected 00F57ECB Mem error @ 0x33D5FB30: found 33D5FB2C, expected 00F57ECC Mem error @ 0x33D5FB34: found 33D5FB2C, expected 00F57ECD Mem error @ 0x33D5FB38: found 00F57ECD, expected 00F57ECE Pattern FFFFFFFF Writing...
Mini2440 U-Boot mtest hangs
Only based on u-boot and 64M experience. There are 4 blocks that show up bad on my machine, but believe this is normal as they are reserved for something (BBT?) Never ran <mtest>, always use <nand scrub> and <nand createbbt> HTH Dave
the commands <nand scrub> and <nand createbbt> are working fine on my board. But aren't those for the NAND-Flash and not for RAM? Does U-Boot check the ram, where itself is located?
Now I've tried: mtest 0x30000000 0x33D5FB00 That seems to work. Is it right, that the last MB of RAM is reserved for Frame Buffer? May it be a problem, writing something in the FB without initialising?