From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] MXS NAND: DMA read error
Date: Tue, 17 Apr 2012 11:05:14 +0200 [thread overview]
Message-ID: <201204171105.14793.marex@denx.de> (raw)
In-Reply-To: <4F8D2C20.5000900@bluegiga.com>
Dear Lauri Hintsala,
> On 04/17/2012 11:29 AM, Marek Vasut wrote:
> >> On 04/17/2012 11:17 AM, Marek Vasut wrote:
> >>>> I'm trying to compile latest U-Boot to mx28evk (rev D) with NAND
> >>>> support. U-Boot boots up but NAND chip is not detected and DMA read
> >>>> error is popped up.
> >>>
> >>> MX28 EVK has no NAND, right?
> >>
> >> MX28 EVK has NAND slot and I have installed NAND chip on it. I'm using
> >> same chip with older pached U-Boot and Linux and chip is working fine
> >> with them.
> >>
> >>> Otherwise, check if you have APBH DMA enabled in your
> >>> include/configs/mx28evk.h
> >>
> >> Config file include/configs/mx28evk.h has following line.
> >>
> >> #define CONFIG_APBH_DMA
> >
> > And you have dcache and icache disabled ?
>
> Yes, they seem to be disabled:
>
> #define CONFIG_SYS_ICACHE_OFF
> #define CONFIG_SYS_DCACHE_OFF
>
> I'm using latest U-Boot and default mx28evk.h config:
> http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/mx28evk.h;h=02f33
> 66ed263ff66fe3b9b2089ec95ef461a92c0;hb=HEAD
>
> I have added only NAND related lines I sent in first message.
Lauri, as much as I'd love to help you, MX28EVK is Fabio's board. So let's see
what he has to say ;-)
>
> BR,
> Lauri
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-04-17 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 8:07 [U-Boot] MXS NAND: DMA read error Lauri Hintsala
2012-04-17 8:17 ` Marek Vasut
2012-04-17 8:23 ` Lauri Hintsala
2012-04-17 8:29 ` Marek Vasut
2012-04-17 8:38 ` Lauri Hintsala
2012-04-17 9:05 ` Marek Vasut [this message]
2012-04-17 9:26 ` Lauri Hintsala
2012-04-17 10:17 ` Marek Vasut
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=201204171105.14793.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.