Modify

Opened 22 months ago

#22242 new defect

cannot get RW rootfs on MLC NAND equipped RB450G boards

Reported by: leonardogyn Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: Cc:

Description

Hi ... i'm having a hard time getting OpenWRT to run on which appears to be newer versions of RB450G boards. The main difference i found among boards is that some are equipped with SLC NAND chipsets (these are the ones that works just fine) and others are equipped with MLC NAND chipsets (these are the ones that DON'T work fine, rootfs is mounted RO only and i wasn't able to change that)

On both boards i can successfully netboot, wget2nand OpenWRT images and even boot from the NAND. That means, clarly, that writing to the NAND is OK on both boards/NAND chipsets. However, on the MLC NAND equipped boards, rootfs is mounted RO after booting from NAND and that's not good for me :(

From the good RB450G ones (SLC NAND equipped), i have:

root@OpenWrt:/# grep r4 /etc/banner
DESIGNATED DRIVER (Bleeding Edge, r49195)
root@OpenWrt:/# dmesg | grep -i nand
NAND flash driver for RouterBoard 4xx series version 0.2.0
nand: Could not find valid ONFI parameter page; aborting
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc
nand: Hynix NAND 512MiB 3,3V 8-bit
nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Creating 3 MTD partitions on "NAND 512MiB 3,3V 8-bit":
root@OpenWrt:/#

from the bad ones, MLC NAND equipped ones:

root@OpenWrt:/# grep r4 /etc/banner
DESIGNATED DRIVER (Bleeding Edge, r49195)
root@OpenWrt:/# dmesg | grep -i nand
NAND flash driver for RouterBoard 4xx series version 0.2.0
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc
nand: Hynix NAND 512MiB 3,3V 8-bit
nand: 512 MiB, MLC, erase size: 256 KiB, page size: 2048, OOB size: 64
Creating 3 MTD partitions on "NAND 512MiB 3,3V 8-bit":
yaffs: MTD device is not NAND it's type 8
root@OpenWrt:/#

despite the 'Could not find valid ONFI parameter page' on some RB450Gs, those are the ones who are working fine.

i also really think the 'MTD device is not NAND' is related to the failure, altough i couldn't find a workaround for that.

tests were done from images i compiled myself based on the git source tree i download yesterday, that means, a VERY recent git tree.

Attachments (0)

Change History (0)

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.