ubifs crossupport between Linux and U-Boot

ubifs crossupport between Linux and U-Boot

[matti kaasinen]

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

Hi!

I Have been using Angstrom distribution for my beaglebone (+ nand flash)
based board. Problem with Angstrom baked Linux/U-boot images is that
whereas both support ubifs partition on nand flash they both seem to handle
it in their own ways. Does Aragon distribution have this same problem?

Cheers,
Matti

[-- Attachment #2: Type: text/html, Size: 386 bytes --]

Re: ubifs crossupport between Linux and U-Boot

[Denys Dmytriyenko]

On Mon, Jan 20, 2014 at 04:29:52PM +0200, matti kaasinen wrote:
> Hi!
> 
> I Have been using Angstrom distribution for my beaglebone (+ nand flash)
> based board. Problem with Angstrom baked Linux/U-boot images is that
> whereas both support ubifs partition on nand flash they both seem to handle
> it in their own ways. Does Aragon distribution have this same problem?

Can you please provide more detailed report for the issue? Otherwise it's 
quite difficult to give any recommendations. Thanks.

-- 
Denys

Re: ubifs crossupport between Linux and U-Boot

[matti kaasinen]

[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]

In short:
If I create UBIFS partition on Linux side, it works quite fine. I can
create directories, files update them without  problems. But if I open this
volume on U-Boot side, I'll get thousands of ecc error messages. Now, if I
try to access this same volume from Linux side after this episode, it also
provides these ecc errors. Therefore, Linux created UBIFS partition gets
corrupted by accessing it from U-Boot side. Volume opening is enough for
this. This I have experienced by Angstrom distribution with Linux 3.8.13
and it possibly was U-Boot 10.04. Anyhow, as it seems that you are now
working with Linux 3.12 - U-Boot 2013-10 combination, you'll need patching
to cope with this issue. By my understanding required patching is not made
before U-Boot 2014-01 and Linux 3.14.

Patching required include:
Quote from Pekon's answer to me:

"
I don't think any earlier kernel versions ever supported beaglebone
Its only recently that a major patch-series of NAND driver was
accepted and  tested on beaglebone.
The patches  are currently in l2-mtd.git tree which should make into
3.13 kernel, before being in linux-next for sometime.
(a) Reference:
http://lists.infradead.org/pipermail/linux-mtd/2013-October/049462.html

(b) In addition to above series, you might need beaglebone DTS updates
which you can refer from below ..
http://lists.infradead.org/pipermail/linux-mtd/2013-October/049438.html
"

U-Boot patching over U-Boot 2013-10 should be found from:
http://patchwork.ozlabs.org/project/uboot/list/?submitter=17320&state=*.

I'm not sure how valid above link is anymore. Maybe Pekon can comment that.

-Matti

2014-01-29 Denys Dmytriyenko <denys@ti.com>

> On Mon, Jan 20, 2014 at 04:29:52PM +0200, matti kaasinen wrote:
> > Hi!
> >
> > I Have been using Angstrom distribution for my beaglebone (+ nand flash)
> > based board. Problem with Angstrom baked Linux/U-boot images is that
> > whereas both support ubifs partition on nand flash they both seem to
> handle
> > it in their own ways. Does Aragon distribution have this same problem?
>
> Can you please provide more detailed report for the issue? Otherwise it's
> quite difficult to give any recommendations. Thanks.
>
> --
> Denys
>

[-- Attachment #2: Type: text/html, Size: 3306 bytes --]

Re: ubifs crossupport between Linux and U-Boot

[Denys Dmytriyenko]

+Tom Rini

Tom, can you please comment? Thanks.


On Wed, Jan 29, 2014 at 05:20:26PM +0200, matti kaasinen wrote:
> In short:
> If I create UBIFS partition on Linux side, it works quite fine. I can
> create directories, files update them without  problems. But if I open this
> volume on U-Boot side, I'll get thousands of ecc error messages. Now, if I
> try to access this same volume from Linux side after this episode, it also
> provides these ecc errors. Therefore, Linux created UBIFS partition gets
> corrupted by accessing it from U-Boot side. Volume opening is enough for
> this. This I have experienced by Angstrom distribution with Linux 3.8.13
> and it possibly was U-Boot 10.04. Anyhow, as it seems that you are now
> working with Linux 3.12 - U-Boot 2013-10 combination, you'll need patching
> to cope with this issue. By my understanding required patching is not made
> before U-Boot 2014-01 and Linux 3.14.
> 
> Patching required include:
> Quote from Pekon's answer to me:
> 
> "
> I don't think any earlier kernel versions ever supported beaglebone
> Its only recently that a major patch-series of NAND driver was
> accepted and  tested on beaglebone.
> The patches  are currently in l2-mtd.git tree which should make into
> 3.13 kernel, before being in linux-next for sometime.
> (a) Reference:
> http://lists.infradead.org/pipermail/linux-mtd/2013-October/049462.html
> 
> (b) In addition to above series, you might need beaglebone DTS updates
> which you can refer from below ..
> http://lists.infradead.org/pipermail/linux-mtd/2013-October/049438.html
> "
> 
> U-Boot patching over U-Boot 2013-10 should be found from:
> http://patchwork.ozlabs.org/project/uboot/list/?submitter=17320&state=*.
> 
> I'm not sure how valid above link is anymore. Maybe Pekon can comment that.
> 
> -Matti
> 
> 2014-01-29 Denys Dmytriyenko <denys@ti.com>
> 
> > On Mon, Jan 20, 2014 at 04:29:52PM +0200, matti kaasinen wrote:
> > > Hi!
> > >
> > > I Have been using Angstrom distribution for my beaglebone (+ nand flash)
> > > based board. Problem with Angstrom baked Linux/U-boot images is that
> > > whereas both support ubifs partition on nand flash they both seem to
> > handle
> > > it in their own ways. Does Aragon distribution have this same problem?
> >
> > Can you please provide more detailed report for the issue? Otherwise it's
> > quite difficult to give any recommendations. Thanks.
> >
> > --
> > Denys
> >

Re: ubifs crossupport between Linux and U-Boot

[Tom Rini]

On 01/29/2014 11:23 AM, Denys Dmytriyenko wrote:
> +Tom Rini
> 
> Tom, can you please comment? Thanks.
> 
> 
> On Wed, Jan 29, 2014 at 05:20:26PM +0200, matti kaasinen wrote:
>> In short:
>> If I create UBIFS partition on Linux side, it works quite fine. I can
>> create directories, files update them without  problems. But if I open this
>> volume on U-Boot side, I'll get thousands of ecc error messages. Now, if I
>> try to access this same volume from Linux side after this episode, it also
>> provides these ecc errors. Therefore, Linux created UBIFS partition gets
>> corrupted by accessing it from U-Boot side. Volume opening is enough for
>> this. This I have experienced by Angstrom distribution with Linux 3.8.13
>> and it possibly was U-Boot 10.04. Anyhow, as it seems that you are now
>> working with Linux 3.12 - U-Boot 2013-10 combination, you'll need patching
>> to cope with this issue. By my understanding required patching is not made
>> before U-Boot 2014-01 and Linux 3.14.

If you do not have sufficient malloc space in U-Boot (and by default, we
do not right now on TI armv7 platforms, in some cases, I will be fixing
this shortly), UBI/UBIFS support can go whacky.  I've not seen ECC
errors, but I've seen other things.

Also you made sure that step one was a 'nand erase' on the whole of the
area you're going to be using, right?

-- 
Tom