Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: UBI filesystem creation fails silently with 4k erase size
Date: Mon, 14 Jul 2014 14:07:04 +0200	[thread overview]
Message-ID: <53C3C7E8.2000806@topic.nl> (raw)

I have a NOR chip that reports a 4k erase size, so in my machine.conf I entered:

MKUBIFS_ARGS = "-m 1 -e 3968 -c 7040"
UBINIZE_ARGS = "-m 1 -p 4096"
UBI_VOLNAME = "qspi-rootfs"


When I create an image with "ubi" in the IMAGE_FSTYPES, the build runs and 
does not report any error, however it did NOT create the ubi filesystem image.

If I change the parameters for a 64k flash using:

MKUBIFS_ARGS = "-m 1 -e 65408 -c 440"

the ubi filesystem is created (both ubifs and ubi files).


Where can I find what went wrong? I'd expect big read error messages telling 
me that it failed to create an image for my device, but I cannot find such 
message anywhere.

So my questions are:

1) Why is there no error message when image creation fails?
2) Where is the log/output from the mkfs.ubi commands?
2) What could be wrong with my mkubifs parameters?

Mike.


Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Topic zoekt FPGA experts
http://topic.nl/vacatures/word-jij-onze-nieuwe-fpga-expert/



             reply	other threads:[~2014-07-14 12:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 12:07 Mike Looijmans [this message]
2014-07-14 13:06 ` UBI filesystem creation fails silently with 4k erase size Mike Looijmans
2014-07-15 15:15   ` Denys Dmytriyenko

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=53C3C7E8.2000806@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox