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 14 Jan 2011 07:57 AM by
What happened to part-write imx31 LoLo command?
 2 Replies
You are not authorized to post a reply.
Author Messages
New Member
New Member

12 Jan 2011 09:52 AM
    I inherited the following SOM setup code that worked on an older version of LoLo :

    erase /dev/nand0 B1 B256
    part-add /dev/nand0 b 1 256
    part-write /dev/nand0

    LoLo version "2.4.12-IMX31_10 0001" doesn't understand the 'part-write" command. How do I write the partition so it remains after a power cycle?

    Ed Perkins
    Basic Member
    Basic Member

    13 Jan 2011 08:31 AM
    Instructions for YAFFS usage in LoLo 2.4.0 and above can be found in the LoLo Command description manual

    or by reviewing the LoLo Labs - - File Systems

    Partitions are now persistent, the part write command is no longer supported. You would mount the yaffs partition with the mount yaffs command.

    I hope that helps.
    Basic Member
    Basic Member

    14 Jan 2011 07:57 AM

    I'd need to see the whole script - you could send it to the Ask A Question if you don't want it on the forum - to be able to see exactly what needs to change besides removing the part-write command.

    If you have a script running when the device boots to set up yaffs and load and execute an image, then the

    part-add ...
    mount yaffs ...

    combination should get you access to the files that are in flash.
    You are not authorized to post a reply.