From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: FW: Barebox on Karo TX25
Date: Thu, 5 Dec 2013 16:24:57 +0100 [thread overview]
Message-ID: <20131205152456.GT24559@pengutronix.de> (raw)
In-Reply-To: <20131203190126.GD27628@ns203013.ovh.net>
On Tue, Dec 03, 2013 at 08:01:26PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 10:26 Tue 03 Dec , Sascha Hauer wrote:
> > BTW Please don't top-post.
> >
> > On Mon, Dec 02, 2013 at 09:13:31AM +0000, John Parker wrote:
> > > Hi again
> > >
> > > So now my problem is that I really could do with the LED and UBIFS stuff that happened since February.
> > >
> > > Should I try to fix mx25 in the latest code, or undo the problematic commit?
> >
> > Well preferably you should fix the latest code and send a patch to make
> > it work again ;) However, that could become tricky. For doing so the
> > patch to enable the debug UART early may become useful. With this you
> > can use putc_ll and puthex_ll in early code.
> >
> > I did some investigation. What happens here is really strange. First I
> > added a missing instruction cache invalidation. That alone doesn't fix
> > the problem. Inserting a nop fixes booting for me, see the attached
> > patch. If I move the nop up in the code it still works. If I move it
> > down, then the board does not work. I have no idea what's happening here
> > :(
>
> could be that the sdram controler need times to stabelized and that you miss a
> delay for this
I thought about this aswell, but I don't believe that a single nop could
make such a reproducable difference. I tried all this with JTAG
debugging aswell which should make all timing issues vanish.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-12-05 15:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 11:28 John Parker
2013-11-27 12:56 ` [PATCH 1/2] ARM: imx: karo tx25: Add config file for imx-image Sascha Hauer
2013-11-27 12:56 ` [PATCH 2/2] scripts: imx-image: Add i.MX25 support Sascha Hauer
2013-11-27 14:49 ` [PATCH 1/2] ARM: imx: karo tx25: Add config file for imx-image John Parker
2013-11-27 13:02 ` FW: Barebox on Karo TX25 Sascha Hauer
2013-11-27 13:18 ` John Parker
2013-11-27 15:49 ` John Parker
2013-11-27 21:01 ` Sascha Hauer
2013-11-28 16:13 ` John Parker
2013-11-28 16:22 ` Baruch Siach
2013-11-29 8:16 ` John Parker
2013-11-29 9:46 ` Sascha Hauer
2013-11-29 10:27 ` John Parker
2013-11-29 10:41 ` John Parker
2013-12-02 9:13 ` John Parker
2013-12-03 9:26 ` Sascha Hauer
2013-12-03 19:01 ` Jean-Christophe PLAGNIOL-VILLARD
2013-12-05 15:24 ` Sascha Hauer [this message]
2013-12-05 16:48 ` Jean-Christophe PLAGNIOL-VILLARD
2013-12-19 14:14 ` John Parker
2013-11-27 19:45 ` John Parker
2013-11-27 20:15 ` Eric Bénard
2013-11-27 20:54 ` Sascha Hauer
2013-11-28 4:16 ` Alexander Aring
2013-11-28 7:20 ` Sascha Hauer
2013-11-28 7:37 ` Alexander Aring
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=20131205152456.GT24559@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.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