This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

NAND ECC error: Read of newly-erased block at <address> failed: -74. Putting on bad_list. JFFS2: marking eraseblock at <address> as bad

Hello.

The latest Appro IPNC Beta 2.8.0 (PSP 04.04.00.01) includes the NAND ECC change to running BCH8 on both u-boot and Linux. This runs okay, but occasionally (~every 20 minutes) spits out the following:

Read of newly-erased block at <block address> failed: -74. Putting on bad_list
JFFS2: marking eraseblock at <block address> as bad

I have looked at the flash content and it looks fine to me. Occasionally, the OOB data will not be totally cleared, but I don't know if that is valid or not.

I can continue with development for now, but eventually I'm going to be out of flash blocks (which aren't bad). I see this with both the Mistral 8148 EVM and my custom 8148 board (using the same NAND part). Both boards work fine with the previous PSP/linux version.

What's going wrong here?

Thanks,
Christopher

  • Christopher,

    We are working to fix this in ver.3.0 release of IPNC RDK. 

    The issue seems to be with JFFS2 file system not able to work with 8-BIT BCH ECC scheme. 

    Regards

    Rajat

  • Rajat,

    Thanks for the quick response.

    Two questions:

    1. When will IPNC RDK 3.0 be available?
    2. Is there a work-around I can use? If I revert U-Boot ti81xx_nand_switch_ecc() back to '0' and Linux board_nand_data.ecc_opt=OMAP_ECC_HAMMING_CODE_HW, will things work properly until v3.0 is ready?

    Thanks,
    Christopher

  • GA 3.0 release will be available in second week of June.

    you will need to revert to 1-BIT ECC in UBOOT as well as in kernel (nand driver) to make it work. For example if you check the GA 2.0 release you will find that the issue is not present.

    Regards

    Rajat

  • Hi, Rajat

    we develop on dm8168 using dvrrdk2.80,i also met this problem,

    the problem is that we do our develop work on dvrrdk 2.80 for a long time, it is not so convenient to using  GA 3.0 release

    to replace immediately, so could you tell me how to solve this problem in dvrrdk 2.80 then?

    Should i have to rewrite both u-boot and the kernel then ?

    I also read the release note for dvrrdk 3.0, it fixs this problem, and a web site is supplied as follow

    http:/ / ap-fpdsp-swapps. dal. design. ti. com/ index. php/ DVR_RDK_V3. 0_GA_App_Notes_Flash_FS

    but it can not access any more

    best regards

    xavier