From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND DMA timed out with i.mx boot source code.
Date: Fri, 29 Jun 2012 06:18:19 +0200 [thread overview]
Message-ID: <201206290618.19404.marex@denx.de> (raw)
In-Reply-To: <1e984755.385d.138360e13ba.Coremail.laub923@163.com>
Dear alex,
> No network on my board, so nand_update_full can't be run.
I'm sure you can figure out how to transfer the update file, the rest is the
same.
> I use command
> "kobs-ng init u-boot.sb" to update(default: /dev/mtd0) or mfgtools from
> freescale.
That won't work, see vim doc/README.mx28_common (section 4) about NAND, around
line 150)
> I just add support NAND to mx28evk configs file copied from
> m28evk configs. Sub-page size of nand flash is 2048bytes with oob size is
> 64byte, and size is 128M.
>
> At 2012-06-28 18:49:39,"Marek Vasut" <marex@denx.de> wrote:
> >Dear alex,
> >
> >> Hi:
> >> I have one board which hardware copied from mx28evk board, and
> >> compiled
> >>
> >> the source code cloned from u-boot mainline git. The rom in mx28 print
> >> 0x80508008, that is "NAND DMA timed out". I compile the source from
> >> u-boot-testing, and it's no any wrong print, and the start is OK. I
> >> don't know why result in this issue.
> >
> >u-boot-testing is quite ancient. But the code you're getting is during
> >bootrom booting from NAND, not in uboot, correct? Does your nand chip
> >have 2048b pages with 64b OOB? Did you use nand_update_full() to reload
> >the NAND?
> >
> >> Best Regards,
> >> Alex
> >
> >Best regards,
> >Marek Vasut
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-06-29 4:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 6:18 [U-Boot] NAND DMA timed out with i.mx boot source code alex
2012-06-28 10:49 ` Marek Vasut
2012-06-29 2:24 ` alex
2012-06-29 2:51 ` Fabio Estevam
2012-06-29 3:28 ` alex
2012-06-29 4:18 ` Marek Vasut [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=201206290618.19404.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.