diff options
| author | Allen Martin <amartin@nvidia.com> | 2012-12-19 13:02:36 -0800 | 
|---|---|---|
| committer | Allen Martin <amartin@nvidia.com> | 2012-12-19 13:02:36 -0800 | 
| commit | a098cf41fdb2a6607c675f7fe4f3164617c9367e (patch) | |
| tree | b37acb36f65909e6f74cc537d73efd883a1485a6 /doc/README.nand | |
| parent | b8a7c467960ffb4d5a5e1eef5f7783fb6f594542 (diff) | |
| parent | 095728803eedfce850a2f85828f79500cb09979e (diff) | |
| download | olio-uboot-2014.01-a098cf41fdb2a6607c675f7fe4f3164617c9367e.tar.xz olio-uboot-2014.01-a098cf41fdb2a6607c675f7fe4f3164617c9367e.zip | |
Merge remote-tracking branch 'u-boot/master' into u-boot-arm-merged
Conflicts:
	README
	arch/arm/cpu/armv7/exynos/clock.c
	board/samsung/universal_c210/universal.c
	drivers/misc/Makefile
	drivers/power/power_fsl.c
	include/configs/mx35pdk.h
	include/configs/mx53loco.h
	include/configs/seaboard.h
Diffstat (limited to 'doc/README.nand')
| -rw-r--r-- | doc/README.nand | 21 | 
1 files changed, 21 insertions, 0 deletions
| diff --git a/doc/README.nand b/doc/README.nand index c13018958..a1a511c53 100644 --- a/doc/README.nand +++ b/doc/README.nand @@ -108,6 +108,9 @@ Configuration Options:     CONFIG_CMD_NAND        Enables NAND support and commmands. +   CONFIG_CMD_NAND_TORTURE +      Enables the torture command (see description of this command below). +     CONFIG_MTD_NAND_ECC_JFFS2        Define this if you want the Error Correction Code information in        the out-of-band data to be formatted to match the JFFS2 file system. @@ -213,6 +216,24 @@ Miscellaneous and testing commands:    DANGEROUS!!! Factory set bad blocks will be lost. Use only    to remove artificial bad blocks created with the "markbad" command. +  "torture offset" +  Torture block to determine if it is still reliable. +  Enabled by the CONFIG_CMD_NAND_TORTURE configuration option. +  This command returns 0 if the block is still reliable, else 1. +  If the block is detected as unreliable, it is up to the user to decide to +  mark this block as bad. +  The analyzed block is put through 3 erase / write cycles (or less if the block +  is detected as unreliable earlier). +  This command can be used in scripts, e.g. together with the markbad command to +  automate retries and handling of possibly newly detected bad blocks if the +  nand write command fails. +  It can also be used manually by users having seen some NAND errors in logs to +  search the root cause of these errors. +  The underlying nand_torture() function is also useful for code willing to +  automate actions following a nand->write() error. This would e.g. be required +  in order to program or update safely firmware to NAND, especially for the UBI +  part of such firmware. +  NAND locking command (for chips with active LOCKPRE pin) |