mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Gaurav Singh <gausinghnsit@gmail.com>
To: barebox@lists.infradead.org
Subject: Failing to load Barebox Environment
Date: Wed, 29 Sep 2010 12:20:20 +0530	[thread overview]
Message-ID: <AANLkTi=k3qTJtQeuOMoBDJMrrR3DQbF7GunjT10FRDSW@mail.gmail.com> (raw)

Hi all,
Currently I'm trying to load a barebox environment image from NAND
storage but can't load it correctly.

I have given the path of my environment in the config :

CONFIG_CONSOLE_FULL=y
CONFIG_CONSOLE_ACTIVATE_FIRST=y
# CONFIG_OF_FLAT_TREE is not set
CONFIG_PARTITION=y
CONFIG_DEFAULT_ENVIRONMENT=y
CONFIG_DEFAULT_ENVIRONMENT_PATH="arch/arm/boards/cartesio-evb2065/env/bin"

After registering the NAND device I prepared a couple of Bad Block
aware partitions :

devfs_add_partition("nand0", 0x00000, 0x200000, PARTITION_FIXED, "self_raw");
dev_add_bb_dev("self_raw", "self0");
devfs_add_partition("nand0", 0x200000, 0x200000, PARTITION_FIXED, "env_raw");
dev_add_bb_dev("env_raw", "env0");

On compilation I get a barebox environment image - barebox_default_env.
Flashed this image to the env0 partition via DFU -
dfu -V 1 -P 24 /dev/env0

From host sent the barebox_default_env (the default_env file is page
alinged) via DFU to the NAND.

The flashing worked fine.

But now when I re-boot the system :

barebox 2010.09.0-00003-ge5727b1-dirty (Sep 27 2010 - 17:18:50)

Board: STMicroelectronics EVB2065 with Cartesio Plus
NAND device: Manufacturer ID: 0x2c, Chip ID: 0x48 (Micron NAND 2GiB 3,3V 8-bit)
Scanning device for bad blocks
Malloc space: 0x00860000 -> 0x00e60000 (size  6 MB)
Stack space : 0x00850000 -> 0x00858000 (size 32 kB)


This system is stuck at this point. Investigating further - I see that
we are stuck at
in the common/environment.c
int envfs_load(char *filename, char *dir)
{
...
buf = xmalloc(size);
buf_free = buf;
ret = read(envfd, buf, size); - Stuck here

I'm wondering why this read is failing. Could the developers shed some
light on this ?

Regards
Gaurav

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2010-09-29  6:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29  6:50 Gaurav Singh [this message]
2010-09-29  7:29 ` Juergen Beisert
2010-09-29  7:48 ` Sascha Hauer
2010-09-29  9:01   ` Gaurav Singh
2010-09-29  9:08     ` Juergen Beisert
2010-09-29  9:14       ` Gaurav Singh
2010-09-29  9:23       ` Juergen Beisert
2010-09-29 10:03         ` Gaurav Singh
2010-09-29 10:08           ` Gaurav Singh
2010-09-30  6:39         ` Gaurav Singh
2010-10-01 11:10           ` Gaurav Singh

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='AANLkTi=k3qTJtQeuOMoBDJMrrR3DQbF7GunjT10FRDSW@mail.gmail.com' \
    --to=gausinghnsit@gmail.com \
    --cc=barebox@lists.infradead.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