From: Alexander Aring <alex.aring@gmail.com>
To: Ashutosh Singh <embedded.ashu@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Can i access the barebox env from linux
Date: Mon, 31 Mar 2014 02:12:11 +0200 [thread overview]
Message-ID: <20140331001145.GB28141@omega.Speedport_W_921V_1_24_000> (raw)
In-Reply-To: <20140328095241.GB21559@omega.Speedport_W_921V_1_24_000>
Hi,
On Fri, Mar 28, 2014 at 10:52:41AM +0100, Alexander Aring wrote:
> On Fri, Mar 28, 2014 at 03:04:40PM +0530, Ashutosh Singh wrote:
> > ya i tried with that too please have a look over barebox log after reboot:
> >
> > nand: ONFI param page 0 valid
> > nand: ONFI flash detected ...
> > nand: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron MT29F4G08ABADAH4),
> > page size: 2048, OOB size: 64
> > malloc space: 0x83ff4000 -> 0x87ff3fff (size 64 MiB)
> > err -74
> well, 74 is EBADMSG.
>
> I run a 'grep -nr "EBADMSG" .' into the current barebox directory and it
> seems that the uncompress env functions doesn't return this errno. So
> maybe your enviroment is correct (I can't check it I need a hexdump for
> this).
>
>
> What I can see is:
> ./drivers/mtd/nand/nand_base.c:1464: return -EBADMSG;
> ./drivers/mtd/nand/nand_base.c:1739: return -EBADMSG;
> ./drivers/mtd/nand/nand_ecc.c:192: return -EBADMSG;
>
>
> and especially "./drivers/mtd/nand/nand_ecc.c", try to enable more debug
> functionality in barebox "make menuconfig" there exist some option to
> enable set some debug level in "Debugging --->".
>
> Or maybe try to instrument the code there to see if it's really some ecc
> failure.
>
today I tested it with nandsim but I can't use a real barebox to read
the environment.
I used nandwrite and nanddump afterwards. Maybe you can run a easy test,
too. Read the image back after you ran nandwrite and extract the image
wit bareboxenv. Then we know the env is successful written and there
exists some other problem between linux<->barebox.
... and please keep the mailinglist in cc.
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-03-31 0:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 5:55 Ashutosh Singh
2014-03-26 6:26 ` Sascha Hauer
2014-03-26 6:57 ` Alexander Aring
2014-03-26 11:14 ` Ashutosh Singh
2014-03-26 11:31 ` Alexander Aring
2014-03-26 11:33 ` Alexander Aring
2014-03-26 11:53 ` Michel Stam
2014-03-26 11:58 ` Alexander Aring
2014-03-26 12:14 ` Michel Stam
[not found] ` <CA+dawz2HSTYcR4Lv_0Q_ECELh2i9kq6vnZTEdnD8e+qu4pyamA@mail.gmail.com>
[not found] ` <20140328091854.GA20774@omega.Speedport_W_921V_1_24_000>
[not found] ` <CA+dawz3gfhFv3mtAOjXVoooE5WqJb6sH1qbMmPw--OD-p_N4Qg@mail.gmail.com>
[not found] ` <20140328095241.GB21559@omega.Speedport_W_921V_1_24_000>
2014-03-31 0:12 ` Alexander Aring [this message]
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=20140331001145.GB28141@omega.Speedport_W_921V_1_24_000 \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=embedded.ashu@gmail.com \
/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