Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 30 Jul 2010 09:22 AM by  mjb
Kernel panic when booting linux, Zoom OMAP35x Torpedo Dev
 0 Replies
Sort:
You are not authorized to post a reply.
Author Messages
mjb
New Member
New Member
Posts:


--
30 Jul 2010 09:22 AM
    I am trying to boot linux on a Zoom OMAP35x Torpedo Dev board, with the filesystem in NAND, using the latest yaffs2 image provided by Logic. Following the instructions in the Zoom OMAP35x Dev Kit section 4.13.6, I receive this error:

    Quote:
    yaffs: Attempting MTD mount on 31.4, "mtdblock4"
    yaffs: auto selecting yaffs2
    yaffs: NAND geometry problems: chunk size 2048, type is yaffs2, inbandTags 0
    List of all partitions:
    1f00 128 mtdblock0 (driver?)
    1f01 2176 mtdblock1 (driver?)
    1f02 12800 mtdblock2 (driver?)
    1f03 246784 mtdblock3 (driver?)
    1f04 256 mtdblock4 (driver?)
    No filesystem could mount root, tried: yaffs
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,4)


    Why is it attempting to mount on mtdblock4? Naively, I would expect it to be set up for mtdblock3, since that is where the filesystem has to go.

    Suggestions on how to proceed, or where to find the relevant information would be appreciated.
    You are not authorized to post a reply.