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: at91sam9260-ek ...
Date: Thu, 6 Mar 2014 11:04:28 +0100 [thread overview]
Message-ID: <E78BBE677EB9144B8F0A0A29674CD5338F93D8D897@SRV-VS06.TELEVIC.COM> (raw)
In-Reply-To: <20140306095541.GY17250@pengutronix.de>
> -----Original Message-----
> From: Sascha Hauer [mailto:s.hauer@pengutronix.de]
> Sent: donderdag 6 maart 2014 10:56
> To: Vanhauwaert Wouter
> Cc: barebox@lists.infradead.org
> Subject: Re: at91sam9260-ek ...
>
> On Wed, Mar 05, 2014 at 10:55:16AM +0100, Vanhauwaert Wouter wrote:
> > Hello,
> >
> > Is the setup for a at91sam9260-ek still functioning?
> > I have troubles with my nand flash. At first it boots and writes BBT-tables.
> > However, next boot, it won't read the BBT, and has errors with the magic on
> the environment variables.
> > Erase /dev/env0 and saveenv do not make a difference.
> > Nandtest does not give me errors...
> >
> > I'm just using the latest barebox 2014.2 and loading it on a
> > at91sam9260-ek through usb (sam-ba). I'm just using the plain
> > at91sam9260ek_defconfig
>
> Seems there's something broken. I have no better idea other than bisecting it.
>
Is there a version which is definitely working and tested with at91sam9260-ek?
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-03-06 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 9:55 at91sam9260-ek Vanhauwaert Wouter
2014-03-05 14:56 ` at91sam9260-ek Vanhauwaert Wouter
2014-03-06 9:55 ` at91sam9260-ek Sascha Hauer
2014-03-06 10:04 ` Vanhauwaert Wouter [this message]
2014-03-06 10:18 ` at91sam9260-ek Sascha Hauer
2014-03-06 12:04 ` at91sam9260-ek Vanhauwaert Wouter
2014-03-06 12:20 ` at91sam9260-ek Vanhauwaert Wouter
2014-03-06 14:29 ` at91sam9260-ek Alexander Shiyan
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=E78BBE677EB9144B8F0A0A29674CD5338F93D8D897@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