[Buildroot] JFFS2 Question

[Buildroot] JFFS2 Question

[Charles Krinke]

I seem to have gotten myself into a pickle (again) now that I have worked
out the details of mounting a buildroot generated rootfs.jffs2.

It boots on my MPC8323 target. I can "ls", "cd", "cat". But, .... when it
boots, it complains a bit

*Write of 68 bytes at 0x002fc498 failed. returned -30, retlen 67087004
Erase at 0x008a0000 failed immediately: -EROFS. Is the sector locked?*

A "df" shows it is 100% full and 13MByte in size (the entire balance of the
NOR flash) and I know that is not true.

And, after it boots, a "rm" of a file, gives me something like

# rm boa.conf
*Write error in obliterating obsoleted node at 0x000741b4: -30*

I am hoping for a spot of advice to help me research and figure out why I
seem to have a read only file system even though I did mount it with "rw" on
the kernel command line. Is this a mkfs.jffs2 issue? A kernel command line
issue? A kernel .config issue? Do I need to rotate my monitor 37 degrees
counter-clockwise to get it to work?

-- 
Charles Krinke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110424/fa3d8e53/attachment.html>

[Buildroot] JFFS2 Question

[Peter Korsgaard]

>>>>> "Charles" == Charles Krinke <charles.krinke@gmail.com> writes:

Hi,

 Charles> I seem to have gotten myself into a pickle (again) now that I
 Charles> have worked out the details of mounting a buildroot generated
 Charles> rootfs.jffs2.

 Charles> It boots on my MPC8323 target. I can "ls", "cd", "cat". But,
 Charles> .... when it boots, it complains a bit

 Charles> Write of 68 bytes at 0x002fc498 failed. returned -30, retlen 67087004
 Charles> Erase at 0x008a0000 failed immediately: -EROFS. Is the sector locked?

Did you configure jffs2 for the correct flash size? Are your flash
sectors locked (protected?) You can normally check in u-boot.

-- 
Bye, Peter Korsgaard

[Buildroot] JFFS2 Question

[Charles Krinke]

I believe the sector size is correct but I am suspecting that the original
Freescale engineer that created the 8323 support did not complete the nor
flash. Meaning I think it is probably locked.

You woldn't know off hand which file an unlocking subroutine should go into,
would you?
On Apr 24, 2011 2:51 PM, "Peter Korsgaard" <jacmet@uclibc.org> wrote:
>>>>>> "Charles" == Charles Krinke <charles.krinke@gmail.com> writes:
>
> Hi,
>
> Charles> I seem to have gotten myself into a pickle (again) now that I
> Charles> have worked out the details of mounting a buildroot generated
> Charles> rootfs.jffs2.
>
> Charles> It boots on my MPC8323 target. I can "ls", "cd", "cat". But,
> Charles> .... when it boots, it complains a bit
>
> Charles> Write of 68 bytes at 0x002fc498 failed. returned -30, retlen
67087004
> Charles> Erase at 0x008a0000 failed immediately: -EROFS. Is the sector
locked?
>
> Did you configure jffs2 for the correct flash size? Are your flash
> sectors locked (protected?) You can normally check in u-boot.
>
> --
> Bye, Peter Korsgaard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110424/cf4180a6/attachment.html>

[Buildroot] JFFS2 Question

[Peter Korsgaard]

>>>>> "Charles" == Charles Krinke <charles.krinke@gmail.com> writes:

 Charles> I believe the sector size is correct but I am suspecting that
 Charles> the original Freescale engineer that created the 8323 support
 Charles> did not complete the nor flash. Meaning I think it is probably
 Charles> locked.

 Charles> You woldn't know off hand which file an unlocking subroutine
 Charles> should go into, would you?

I think the easiest is just to do a 'protect off all' in u-boot.

-- 
Bye, Peter Korsgaard