Re: [Yaffs] Problems with YAFFS support for RB532

Top Page
Attachments:
Message as email
+ (text/plain)
+ signature.asc (application/pgp-signature)
Delete this message
Reply to this message
Author: Giampaolo Mancini
Date:  
To: yaffs
Subject: Re: [Yaffs] Problems with YAFFS support for RB532
Hi,
Jiri Fojtasek spotted the problem in the swapped NAND pins on different
revision of RB532 boards.

To get OpenWRT+YAFFS work on the old (pre revision 5) RB532 please
revert from https://dev.openwrt.org/changeset/7777.

Thanks,
mancho.

Giampaolo Mancini wrote:
> Hi,
> it seems that we have same new problem with YAFFS support for Mikrotik's
> RouterBoard 532 NAND.
>
> I've already reported the issue to OpenWRT trac
>
> https://dev.openwrt.org/ticket/2038
>
> Please read the log:
>
> https://dev.openwrt.org/attachment/ticket/2038/rb532-nand.log
>
> I'm guessing if i am doing some mistake or if something got broken
> through various kernel updates.
>
> A clean YAFFS from CVS (without any OpenWRT's patches) gives the same
> results as in reported log.
>
> YAFFS Configuration as following (OpenWRT defaults):
>
> CONFIG_YAFFS_FS=y
> CONFIG_YAFFS_YAFFS1=y
> # CONFIG_YAFFS_9BYTE_TAGS is not set
> CONFIG_YAFFS_DOES_ECC=y
> CONFIG_YAFFS_ECC_WRONG_ORDER=y
> CONFIG_YAFFS_YAFFS2=y
> CONFIG_YAFFS_AUTO_YAFFS2=y
> # CONFIG_YAFFS_DISABLE_LAZY_LOAD is not set
> CONFIG_YAFFS_CHECKPOINT_RESERVED_BLOCKS=10
> # CONFIG_YAFFS_DISABLE_WIDE_TNODES is not set
> CONFIG_YAFFS_ALWAYS_CHECK_CHUNK_ERASED=y
> CONFIG_YAFFS_SHORT_NAMES_IN_RAM=y
> # CONFIG_OCFS2_FS is not set
>
>
> Any clue or suggestion? Someone experiencing same problems?
>
> Thanx in advance,
> mancho.
>



-- 
Giampaolo "mancho" Mancini
    Wi-Next Labs
mailto:giampaolo.mancini@winext.eu
mobile:(+39)3484148682
http://www.winext.eu