mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Vanhauwaert Wouter <W.Vanhauwaert@TELEVIC.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: bareboxenv on userspace - wrong crc on env
Date: Fri, 11 Oct 2013 16:08:15 +0200	[thread overview]
Message-ID: <E78BBE677EB9144B8F0A0A29674CD5338F2D4436DC@SRV-VS06.TELEVIC.COM> (raw)
In-Reply-To: <20130829184422.GB30088@pengutronix.de>

> -----Original Message-----
> From: Sascha Hauer [mailto:s.hauer@pengutronix.de]
> Sent: donderdag 29 augustus 2013 20:44
> To: Vanhauwaert Wouter
> Cc: barebox@lists.infradead.org
> Subject: Re: bareboxenv on userspace - wrong crc on env
> 
> On Thu, Aug 29, 2013 at 11:24:41AM +0200, Vanhauwaert Wouter wrote:
> > Hello all,
> >
> > I'm having issues accessing my barebox environment from within linux....
> >
> > My barebox and environment are located on a SPI NOR flash.
> > This boots ok, and barebox is able to save its environment to it.
> >
> > When I want to load it in userspace through:
> >
> > $ bareboxenv -l /mnt /dev/mtd1
> > Or
> > $ dd if=/dev/mtd1 /tmp/barebox
> > Or
> > $ dd if=/dev/mdtblock1 /tmp/barebox
> >
> > Result is:
> > Wrong crc on env
> >
> > However it's working fine in barebox itself
> >
> > What can be wron?
> 
> The only idea I have is that /dev/mtd1 might not be the place where barebox
> stores it's environment, maybe because of different probe order in the kernel or
> different partition layout. Could you send a hexdump of the first 256 bytes or so
> of /dev/mtd1?
> 
> Sascha

I had general issues reading and writing spi nor flash in userspace (without being aware of it). Now it works, I can read / write from nor flash from within linux.
I can copy the barebox bootloader and uImage to it through dd and this works fine. I can also load my barebox environment, change things and write it back and read it back out.
However, when I restart my board afterwards, I get an invalid crc on superblock.

(Sorry, some kind of double post with my new topic today)

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

      reply	other threads:[~2013-10-11 14:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  9:24 Vanhauwaert Wouter
2013-08-29 10:44 ` Yi Qingliang
2013-08-29 11:35   ` Vanhauwaert Wouter
2013-08-30  2:29     ` Yi Qingliang
2013-08-29 18:44 ` Sascha Hauer
2013-10-11 14:08   ` Vanhauwaert Wouter [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=E78BBE677EB9144B8F0A0A29674CD5338F2D4436DC@SRV-VS06.TELEVIC.COM \
    --to=w.vanhauwaert@televic.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox