All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] UBI and UBIFS on ARM64
Date: Wed, 7 Sep 2016 06:39:20 +0200	[thread overview]
Message-ID: <57CF99F8.1060607@denx.de> (raw)
In-Reply-To: <CADBxsQWhd96ve+o_HgWsY1VGbSSNE8m_+AnuDa=FHwhHn=dcKw@mail.gmail.com>

Hello Adam,

Am 06.09.2016 um 16:44 schrieb Adam Oleksy:
> Dear U-Boot community,
> I'm developing software for Xilinx ZynqMP platform, which is made in
> 64-bit architecture. I would like to store every artifact needed to
> boot up on the UBIFS partition. I faced problem, that u-boot does not
> want to compile with enabled UBI/UBIFS support, due to lack of some
> atomic operations on longs. So, I've written them (see
> http://pastebin.com/ibp0Zt99). Please note, that I've written only
> that functions, which are needed by UBI/UBIFS. Then UBIFS started work
> on the target. Almost... because I've found that large files (~20MiB)
> can't be read. I've enabled debug messages, but I don't know how to
> interpret them (please see http://pastebin.com/gByDcdvw). Maybe you
> are able to help me?
> I've also checked how the UBIFS behaves in the Linux, and the result
> is that everything works as expected. It means that I can write large
> files to UBIFS, and read them back successfully.
> Should you need any further information, please do not hesitate to contact me.

Hard to say ... here an extract of your debug log:

UBI DBG io (pid 1): read 509 bytes from PEB 1059:10040
UBIFS error (ubi0:0 pid 0): ubifs_check_node: bad magic 0x61018ce, expected 0x6101831

Here begin your problem ... for some reasons you do not read the
correct magic number ... I tend to say some problem with your nand
driver and/or io functions, maybe cache setup? Sorry, more I cannot say ...

UBIFS error (ubi0:0 pid 0): ubifs_check_node: bad node at LEB 417:9912
Not a node, first 24 bytes:UBIFS error (ubi0:0 pid 0): ubifs_read_node: expected node type 1
UBIFS DBG tnc: key (67, data, 4679)
UBIFS error (ubi0:0 pid 0): do_readpage: cannot read page 4679 of inode 67, error -117
Error reading file 'rfsw-image_ramdisk.itb'
UBI DBG gen (pid 1): close device 0, volume 0, mode 1

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2016-09-07  4:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 14:44 [U-Boot] UBI and UBIFS on ARM64 Adam Oleksy
2016-09-07  4:39 ` Heiko Schocher [this message]
2016-09-07  4:49   ` Heiko Schocher
2016-09-07  9:26     ` Adam Oleksy
2016-09-07 10:26       ` Heiko Schocher
2016-09-07 10:42         ` Adam Oleksy
  -- strict thread matches above, loose matches on Subject: below --
2016-09-06 10:05 Oleksy, Adam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57CF99F8.1060607@denx.de \
    --to=hs@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.