3cf06f4f85
This tests ECC biterror recovery on a single NAND page. Mostly intended
to test ECC hardware and low-level NAND driver.
There are two test modes:
0 - artificially inserting bit errors until the ECC fails
This is the default method and fairly quick. It should
be independent of the quality of the FLASH.
1 - re-writing the same pattern repeatedly until the ECC fails.
This method relies on the physics of NAND FLASH to eventually
generate '0' bits if '1' has been written sufficient times. Depending
on the NAND, the first bit errors will appear after 1000 or
more writes and then will usually snowball, reaching the limits
of the ECC quickly.
The test stops after 10000 cycles, should your FLASH be exceptionally
good and not generate bit errors before that. Try a different page
offset in that case.
Please note that neither of these tests will significantly 'use up' any FLASH
endurance. Only a maximum of two erase operations will be performed.
Signed-off-by: Iwo Mergler <Iwo.Mergler@netcommwireless.com.au>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
9 lines
392 B
Makefile
9 lines
392 B
Makefile
obj-$(CONFIG_MTD_TESTS) += mtd_oobtest.o
|
|
obj-$(CONFIG_MTD_TESTS) += mtd_pagetest.o
|
|
obj-$(CONFIG_MTD_TESTS) += mtd_readtest.o
|
|
obj-$(CONFIG_MTD_TESTS) += mtd_speedtest.o
|
|
obj-$(CONFIG_MTD_TESTS) += mtd_stresstest.o
|
|
obj-$(CONFIG_MTD_TESTS) += mtd_subpagetest.o
|
|
obj-$(CONFIG_MTD_TESTS) += mtd_torturetest.o
|
|
obj-$(CONFIG_MTD_TESTS) += mtd_nandecctest.o
|
|
obj-$(CONFIG_MTD_TESTS) += mtd_nandbiterrs.o
|