All of lore.kernel.org
 help / color / mirror / Atom feed
From: mar.krzeminski <mar.krzeminski@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot and UBI problem with vexpress board.
Date: Sun, 29 Mar 2015 21:57:51 +0200	[thread overview]
Message-ID: <5518593F.7090504@gmail.com> (raw)
In-Reply-To: <55157CEC.2010804@gmail.com>

Hi,

It seem that I have found the root cause of the problem.
This board in qemu is set in this way, that device width is set to 2 and 
interface to 4.
That is why CFI driver in u-boot calculates wrongly sector size ( 
because size ratio variable was wrong ),
so in the end every odd sector (counting from 0 ) was not available.
I've changed vexpress board code in qemu and for now it is working.
I do not have real vexpress board to check if the root cause is u-boot 
or qemu,
but i think CFI driver i popular so propapbly there is something wrong 
in qemu site.

Regards,
Marcin


W dniu 27.03.2015 o 16:53, mar.krzeminski pisze:
> Hi Stefan,
>
> I've changed malloc pool size to 2MiB and nothing changed.
> I've also disabled UBIFS support and that does not make any changes.
> Still after qemu restart u-boot can not attach to ubi device.
>
> Regards,
> Marcin
>
> W dniu 27.03.2015 o 16:01, Stefan Roese pisze:
>> Hi Marcin,
>>
>> On 27.03.2015 13:59, Marcin Krzemi?ski wrote:
>>> I want to test some UBI fs behavior in U-Boot using qemu and 
>>> vexpress_ca9x4
>>> board ( U-Boot 2015.1)
>>> To tst UBI I added lines to vexpress_ca9x4.h:
>>>
>>> #define CONFIG_MTD_DEVICE   /* needed for mtdparts commands */
>>> #define CONFIG_MTD_PARTITIONS   /* needed for UBI */
>>> #define CONFIG_FLASH_CFI_MTD
>>> #define MTDIDS_DEFAULT      "nor0=flash0-0"
>>> #define MTDPARTS_DEFAULT "mtdparts=flash0-0:1m(empty),10m(ubi),-(rest)"
>>> #define CONFIG_LZO          /* needed for UBI */
>>> #define CONFIG_RBTREE           /* needed for UBI */
>>> #define CONFIG_CMD_MTDPARTS
>>> #define CONFIG_CMD_UBI
>>> #define CONFIG_CMD_UBIFS
>>> #define CONFIG_FIT
>>>
>>> also I've changed malloc pool size to 512kB in vexpress_common.h:
>>> #define CONFIG_SYS_MALLOC_LEN (CONFIG_ENV_SIZE + 512 * 1024)
>>
>> Without looking deeper into your mail, I would recommend to increase 
>> the malloc size to at least 2MiB and test again.
>>
>> Thanks,
>> Stefan
>>
>>
>

  reply	other threads:[~2015-03-29 19:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 12:59 [U-Boot] U-boot and UBI problem with vexpress board Marcin Krzemiński
2015-03-27 15:01 ` Stefan Roese
2015-03-27 15:53   ` mar.krzeminski
2015-03-29 19:57     ` mar.krzeminski [this message]
2015-03-30  6:05       ` Heiko Schocher
2015-03-30 18:07         ` mar.krzeminski
2015-03-31  5:24           ` Heiko Schocher
2015-03-31  5:33             ` Marcin Krzemiński
2015-03-30  5:40     ` Heiko Schocher

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=5518593F.7090504@gmail.com \
    --to=mar.krzeminski@gmail.com \
    --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.