From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mxc nand: Add support for i.MX5
Date: Sat, 2 Feb 2013 16:04:39 +0100 [thread overview]
Message-ID: <201302021604.39454.marex@denx.de> (raw)
In-Reply-To: <1324725733.406116.1359812625783.JavaMail.root@advansee.com>
Dear Beno?t Th?baudeau,
> Hi Marek,
>
> On Tuesday, January 8, 2013 12:18:05 PM, Beno?t Th?baudeau wrote:
> > Dear Marek Vasut,
> >
> > On Tuesday, January 8, 2013 12:05:26 PM, Marek Vasut wrote:
> > > Dear Beno?t Th?baudeau,
> > >
> > > [...]
> > >
> > > > > > > NOTE: I'm seeing issues when this is compiled into U-Boot.
> > > > > > > U-Boot
> > > > > > > won't boot on
> > > > > > > my MX53 board and will hang right after printing "DRAM:" and
> > > > > > > before
> > > > > > > printing the
> > > > > > > CPU info. I suspect it's some kind of unaligned access.
> > > > > >
> > > > > > OK. I'm waiting for your test results. It works for me on
> > > > > > i.MX51
> > > > > > with
> > > > > > 2012.07.
> > > > >
> > > > > It works with 2013.01-rc1, but I have issues. When I boot the
> > > > > board
> > > > > from SD, it
> > > > > hangs. When I load via JTAG, it doesn't hang. I suspect it's
> > > > > something related
> > > > > to the MXC NAND driver, since if the driver is not compiled in,
> > > > > it
> > > > > works like
> > > > > charm both ways.
> > > > >
> > > > > Otherwise, when booted, the NAND works fine.
> > > > >
> > > > > I wonder if there's some unaligned access or something happening
> > > > > in
> > > > > the NAND
> > > > > driver. Or maybe some other issue where the code is miscompiled.
> > > >
> > > > Or there is something wrong with the Flash header or SPL?
> > >
> > > Flash header?
> >
> > The IVT from imximage stuff.
>
> Did you have a chance to further investigate this hang issue with non-JTAG
> boot and the NFC driver compiled in?
I recall there being some patch from Scott and there was a guy on IRC who met
this issue too (can you join irc? #u-boot @ irc.freenode.net). No activity on
this from my side, since the issue magically disappeared once and didn't pop up
again (weird, I know).
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-02-02 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 9:33 [U-Boot] [PATCH 1/2] mxc nand: Add support for i.MX5 Marek Vasut
2013-01-08 10:23 ` Fabio Estevam
2013-01-08 10:40 ` Marek Vasut
2013-01-08 10:24 ` Benoît Thébaudeau
2013-01-08 10:38 ` Marek Vasut
2013-01-08 10:54 ` Benoît Thébaudeau
2013-01-08 11:05 ` Marek Vasut
2013-01-08 11:18 ` Benoît Thébaudeau
2013-02-02 13:43 ` Benoît Thébaudeau
2013-02-02 15:04 ` Marek Vasut [this message]
2013-02-04 19:55 ` Scott Wood
2013-01-08 18:34 ` Scott Wood
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=201302021604.39454.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.