Openmoko Bug #2057: 1bit errors in files
Openmoko Public Trac
bugs at docs.openmoko.org
Wed Oct 8 17:48:05 CEST 2008
#2057: 1bit errors in files
---------------------------------------------+------------------------------
Reporter: Richard.Kralovic | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: file corruption, 1bit errors | Blockedby:
Reproducible: rarely | Blocking:
---------------------------------------------+------------------------------
Comment(by Vladimir.Koutny):
I have a unit from the same (pulster.de) delivery as Richard and I don't
see any memory issues (yet). However, I also can't run mtest in the full
range - the range that doesn't cause crash/han
g is:
30000040 - 33e80000
34008000 - 38000000
(btw. first 0x40 bytes contains vector table - I guess you don't want to
mtest that area :) )
That might be influenced by uboot version - in my case it is 1.3.2-rc2
-dirty-moko12 (NAND) and 1.3.2-moko12 (NOR) (both as shipped), not sure
where uboot code/data are mapped.
Btw., when looking at Freerunner memory map at
http://wiki.openmoko.org/wiki/Neo_FreeRunner_Memory_Mapping, I would guess
that external ram chip would be mapped starting at 38000000...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2057#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list