Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: "Ezequiel García" <ezequiel@vanguardiasur.com.ar>,
	linux-mtd@lists.infradead.org, "Stefan Roese" <sr@denx.de>,
	"Pekon Gupta" <pekon@ti.com>
Subject: Re: Question about AM335x SoC supported NAND flash
Date: Wed, 19 Feb 2014 17:15:52 +0100	[thread overview]
Message-ID: <5304D8B8.4010303@zonque.org> (raw)
In-Reply-To: <CAAEAJfD4ddT0Av3ia-+hEf0aXKcyUK4j69YF-t=qTCLkum4a8A@mail.gmail.com>

On 02/19/2014 05:04 PM, Ezequiel García wrote:
> However, we cannot get the SoC to boot from NAND. We've double-checked
> the hardware
> and the SYSBOOT, but still no luck with it.
> 
> So, I thought about asking here, in case this device is (for some
> reason) not supported by the
> ROM code booting. Maybe someone already struggled with this and has
> some idea to suggest?

We're booting that SoC from an 8-bit NAND, connected to GPMC_CSN0.
SYSBOOT[11:10] is 00b.

The kernel output reads like this:

[    1.320533] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xda
[    1.327280] nand: Toshiba NAND 256MiB 3,3V 8-bit
[    1.332112] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.338077] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[    1.344122] 9 ofpart partitions found on MTD device omap2-nand.0

I wasn't around for early boot-strapping of the platform, so I'm not
aware of any typical pitfalls.

If you want to compare other details between our platforms, let me know.


HTH,
Daniel

  reply	other threads:[~2014-02-19 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 16:04 Question about AM335x SoC supported NAND flash Ezequiel García
2014-02-19 16:15 ` Daniel Mack [this message]
2014-02-19 17:55 ` Gupta, Pekon
2014-02-19 18:43   ` Ezequiel García

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=5304D8B8.4010303@zonque.org \
    --to=daniel@zonque.org \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.com \
    --cc=sr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox