How can I make flash writeable?

Sat Oct 18 12:19:38 EST 2008

Hi Mark,

I guess you want to have RW filesystem for your Linux target.
If that's the case you need to have root filesystem as JFFS2.

There's a document MPC8313E-RDB BSP User's Guide comes with the MPC8313E-RDB 
package.
It has all info for several filesystems like NFS (network), Ramdisk 
(Read-Only), and JFFS2 (Read/Write)

Regards,

Duy-Ky

----- Original Message ----- 
From: <linuxppc-embedded-request at ozlabs.org>
To: <linuxppc-embedded at ozlabs.org>
Sent: Friday, October 17, 2008 6:00 PM
Subject: Linuxppc-embedded Digest, Vol 50, Issue 30

> Send Linuxppc-embedded mailing list submissions to
> linuxppc-embedded at ozlabs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> or, via email, send a message with subject or body 'help' to
> linuxppc-embedded-request at ozlabs.org
>
> You can reach the person managing the list at
> linuxppc-embedded-owner at ozlabs.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linuxppc-embedded digest..."
>
>
> Today's Topics:
>
>   1. Re: How can I make flash writeable? (Mark Bishop)
>   2. Re: How can I make flash writeable? (Marco Stornelli)
>   3. Re: Loadable module crashes at kernel stack overflow or
>      machine check (Ben Gardiner)
>   4. Re: Oops in during system run (Scott Wood)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 17 Oct 2008 08:33:52 -0400
> From: Mark Bishop <mark at bish.net>
> Subject: Re: How can I make flash writeable?
> To: linuxppc-embedded at ozlabs.org
> Message-ID: <20081017083352.hvn0g2q1es8skcwg at www.bish.net>
> Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
> format="flowed"
>
>
>
> Ok, so bear with me.  I've read booting-without-of.txt in the
> Documentation/powerpc directory and I modified a .dts file but now what?
>
> I use ltib or u-boot to load that into the device or do I roll a
> kernel with that file and flash the device with it?
>
> Apologies for the less than technical questions.
>
> Quoting Marco Stornelli <marco.stornelli at coritel.it>:
>
>> Hi Mark,
>>
>>> How can I tell which devices are mapped to /proc/mtd devices?
>>
>> If I well understand the question, you'd like to change the partitions
>> layout (?), so you should check out the dts file to see the flash
>> layout, then you can specify there the partitions and change the
>> dimensions, if they are read-only...and so on.
>>
>> Regards,
>>
>> Mark Bishop ha scritto:
>>> I am using the MPC8313E-RDB and I am having some problems using the
>>> flash that comes on the board.  Let me preface this by saying that I
>>> haven't worked in the embedded linux arena in about 10 years so I am
>>> trying to catch up with all the new toys.
>>>
>>> This board uses uBoot and it currently has 128M of DDR2, 8M flash and
>>> 32M NAND Flash.  I have a few questions:
>>>
>>> How can I tell which memory device it uses to boot out of?
>>> How can I tell which devices are mapped to /proc/mtd devices?
>>>
>>>
>>> I want to create a writeable flash partition, is there a FAQ out there I
>>> could look at.
>>>
>>> All of this is after a few days of using Google to try and glean some
>>> data from the internet.  And the books don't get here from Amazon until
>>> Monday.
>>>
>>> I would appreciate any help.  Even a RTFM - if you could point me to
>>> TFM, it would greatly help.
>>> _______________________________________________
>>> Linuxppc-embedded mailing list
>>> Linuxppc-embedded at ozlabs.org
>>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>
>>
>> --
>> Marco Stornelli
>> Embedded Software Engineer
>> CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
>> http://www.coritel.it
>>
>> marco.stornelli at coritel.it
>> +39 06 72582838
>>
>>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 17 Oct 2008 15:13:58 +0200
> From: Marco Stornelli <marco.stornelli at coritel.it>
> Subject: Re: How can I make flash writeable?
> To: Mark Bishop <mark at bish.net>
> Cc: linuxppc-embedded at ozlabs.org
> Message-ID: <48F88F96.3000804 at coritel.it>
> Content-Type: text/plain; charset=us-ascii
>
> You have to compile it with the dtc compiler and load it with the uboot
> bootm command, indeed, (at least with a recent uboot version) it has
> three parameters: kernel, dtb (the name of dts compiled) and initrd. If
> you want you can store the dtb in flash.
>
> Regards,
>
> Mark Bishop ha scritto:
>>
>>
>> Ok, so bear with me.  I've read booting-without-of.txt in the
>> Documentation/powerpc directory and I modified a .dts file but now what?
>>
>> I use ltib or u-boot to load that into the device or do I roll a kernel
>> with that file and flash the device with it?
>>
>> Apologies for the less than technical questions.
>>
>> Quoting Marco Stornelli <marco.stornelli at coritel.it>:
>>
>>> Hi Mark,
>>>
>>>> How can I tell which devices are mapped to /proc/mtd devices?
>>>
>>> If I well understand the question, you'd like to change the partitions
>>> layout (?), so you should check out the dts file to see the flash
>>> layout, then you can specify there the partitions and change the
>>> dimensions, if they are read-only...and so on.
>>>
>>> Regards,
>>>
>>> Mark Bishop ha scritto:
>>>> I am using the MPC8313E-RDB and I am having some problems using the
>>>> flash that comes on the board.  Let me preface this by saying that I
>>>> haven't worked in the embedded linux arena in about 10 years so I am
>>>> trying to catch up with all the new toys.
>>>>
>>>> This board uses uBoot and it currently has 128M of DDR2, 8M flash and
>>>> 32M NAND Flash.  I have a few questions:
>>>>
>>>> How can I tell which memory device it uses to boot out of?
>>>> How can I tell which devices are mapped to /proc/mtd devices?
>>>>
>>>>
>>>> I want to create a writeable flash partition, is there a FAQ out there 
>>>> I
>>>> could look at.
>>>>
>>>> All of this is after a few days of using Google to try and glean some
>>>> data from the internet.  And the books don't get here from Amazon until
>>>> Monday.
>>>>
>>>> I would appreciate any help.  Even a RTFM - if you could point me to
>>>> TFM, it would greatly help.
>>>> _______________________________________________
>>>> Linuxppc-embedded mailing list
>>>> Linuxppc-embedded at ozlabs.org
>>>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>>
>>>
>>> -- 
>>> Marco Stornelli
>>> Embedded Software Engineer
>>> CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
>>> http://www.coritel.it
>>>
>>> marco.stornelli at coritel.it
>>> +39 06 72582838
>>>
>>>
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded at ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>
> -- 
> Marco Stornelli
> Embedded Software Engineer
> CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
> http://www.coritel.it
>
> marco.stornelli at coritel.it
> +39 06 72582838
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 17 Oct 2008 09:12:07 -0400
> From: Ben Gardiner <BenGardiner at nanometrics.ca>
> Subject: Re: Loadable module crashes at kernel stack overflow or
> machine check
> To: Ganesh Kumar N M <ganeshkumar at signal-networks.com>
> Cc: linuxppc-dev at ozlabs.org, linuxppc-embedded at ozlabs.org
> Message-ID: <48F88F27.4040107 at nanometrics.ca>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> Ganesh Kumar N M wrote:
>> *Hi All,*
>> **
>> *    I'm working on MPC860 with Montavista linux 2.4.18*
>> *We have a Linux kernel loadable module which on loading*
>> *panicks after some random time say 8 hours, 4 hours or so*
>> *the oops outputs say either machine check exception or *
>> *kernel stack overflow (randomly both show up) a**re as below:*
> I don't know for sure what could be causing your problem. I can only
> suggest some patches that have helped us in the past.
>
> I'm not familiar with Montavista's kernel versions; but I know our
> 2.4.24 kernel did not have the 'separate I-TLB error and miss handling'
> patch (
> http://ozlabs.org/pipermail/linuxppc-embedded/2005-January/016382.html )
> which caused our applications to segfault for not apparent reason.
>
> I also suggest applying the CPU15 fix (
> http://git.denx.de/?p=linuxppc_2_4_devel.git;a=commit;h=baf9a6caca75b1f338ae370669e5882809000164
> and
> http://git.denx.de/?p=linuxppc_2_4_devel.git;a=commit;h=3ad403717f1d9c6a09ec41a5b016ac5245591122
> ) and enabling it temporarily to see if the problem could be the unlucky
> placement of a branch instruction at the end of a page; but evaluate the
> performance of your application carefully if you are considering running
> production code with the patch enabled as it introduces significant
> overhead.
>
> Regards,
>
> Ben Gardiner
> Nanometrics Seismological Instruments
> 250 Herzberg Rd., Kanata, ON, CA, K2K 2A1
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20081017/ba2e605f/attachment.html>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 17 Oct 2008 10:21:32 -0500
> From: Scott Wood <scottwood at freescale.com>
> Subject: Re: Oops in during system run
> To: Sreejith <sreejithmm at tataelxsi.co.in>
> Cc: linuxppc-dev at ozlabs.org, linuxppc-embedded at ozlabs.org
> Message-ID: <20081017152129.GA19584 at ld0162-tx32.am.freescale.net>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Oct 17, 2008 at 03:49:12PM +0530, Sreejith wrote:
>> This is a peculiar Oops we are encountering during the running of our 
>> board
>> (sh4) architecture
>
> So why are you posting to powerpc lists?
>
>> PC  : 844240f8 SP  : 88d1ff44 SR  : 400080f0 TEA : c0169d64    Tainted: P
>
> With proprietary modules, too.
>
>> Give you valuable suggestions!!
>
> Debug the code?
> Switch to powerpc? :-)
>
> -Scott
>
>
> ------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded at ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
> End of Linuxppc-embedded Digest, Vol 50, Issue 30
> *************************************************
> 