Hello,Now we are using the ETFS nand system in the bsp "bsp-nto650-ti-am335x-evm-sp1-trunk-201211211248". In the 
previous days all of our products run ok, but some of the products suddenly have an "ETFS nand system" error in these 
days. We don't know why the error happen. When i run "fs-etfs-omap3530_micron -D gpmc=0x50000000  -m /app" again, the 
products with the error print:
Starting etfs driver2...
fs-etfs-omap3530_micron: readtrans BADBLK on cluster 38848
fs-etfs-omap3530_micron: readtrans BADBLK on cluster 190144
fs-etfs-omap3530_micron: readtrans BADBLK on cluster 504384
fs-etfs-omap3530_micron: No filesystem detected. Entering stopped mode.
fs-etfs-omap3530_micron: Unable to initialise ETFS systems (Corrupted file system detected)

    when the error happen, if I run "fs-etfs-omap3530_micron -D gpmc=0x50000000  -e -m /app", the ETFS nand system will 
resume to use.
    I have the following questions to ask for help:
    1.How the nand driver program judge if it detected the Corrupted file system? Does the driver read some fixed 
position of the nand block? 
    2.when I run "fs-etfs-omap3530_micron -D gpmc=0x50000000  -m /app -vvv", it print:
Readtran 7672: 0 491008 ret 2 -> 16937692    0     8,3688
Readtran 7673: 0 491072 ret 2 -> 16937692    0     8,3688
Readtran 7674: 0 491136 ret 2 -> 16937692    0     8,3688
Readtran 7675: 0 491200 ret 2 -> 16937692    0     8,3688
Readtran 7676: 0 491264 ret 2 -> 16937692    0     8,3688
Readtran 7677: 0 491328 ret 2 -> 16937692    0     8,3688
Readtran 7678: 0 491392 ret 2 -> 16937692    0     8,3688
Readtran 7679: 0 491456 ret 2 -> 16937692    0     8,3688
Readtran 7680: 0 491520 ret 2 -> 16937692    0     8,3688
Readtran 7681: 0 491584 ret 2 -> 16937692    0     8,3688
Readtran 7682: 0 491648 ret 2 -> 16937692    0     8,3688
Readtran 7683: 0 491712 ret 2 -> 16937692    0     8,3688
Readtran 7684: 0 491776 ret 2 -> 16937692    0     8,3688
Readtran 7685: 0 491840 ret 2 -> 16937692    0     8,3688
     what each of the below number means ?
     3.How to find the reason of this error? Maybe a power failure? I have tested with a lot power failure, but the 
error didn't happen again.
     thank you very much!