linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Poselenov <sposelenov@emcraft.com>
To: JH <jupiter.hce@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND user space program
Date: Wed, 12 Jun 2019 13:26:43 +0300	[thread overview]
Message-ID: <b931537d9268184b1c98e316a6b95a72847bbe69.camel@emcraft.com> (raw)
In-Reply-To: <CAA=hcWRTPsk=zX=bnV6xAt-EpnyXy+dZdYGuLk8M-0UAjWHM1g@mail.gmail.com>

Hello JH,

Going back to your original question, if your intention is to write a
Linux image to a raw (ie without filesystem) NAND partition, so the
bootloader (eg U-Boot) could be able to read the kernel image from
there, then the suggestion is to use the mtd-utils "nandwrite", which
is able to deal with the NAND bad blocks.

Regards,
Sergei

On Wed, 2019-06-12 at 09:01 +1000, JH wrote:
> Thanks Richard, can the Linux zImage or rootfs load to NAND directly
> via JTAG or serial line?
> 
> Thank you.
> 
> Kind regards,
> 
> - JH
> 
> On 6/11/19, Richard Weinberger <richard.weinberger@gmail.com> wrote:
> > On Tue, Jun 11, 2019 at 12:20 PM JH <jupiter.hce@gmail.com> wrote:
> > > Hi,
> > > 
> > > In NOR flash, access flash in user space is integrated to the
> > > Linux
> > > system read / write, is it the same story for NAND flash? I
> > > installed
> > > mtd-utils, but not sure if I can still use Linux system read /
> > > write
> > > to access NAND flash or not.
> > 
> > Well, Linux exposes both NOR and NAND flashes as MTD.
> > So there shouldn't be much difference.
> > But make sure you can deal with specialties of NAND, such as
> > bad blocks.
> > 
> > 
> > --
> > Thanks,
> > //richard
> > 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2019-06-12 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 10:17 NAND user space program JH
2019-06-11 13:21 ` Richard Weinberger
2019-06-11 23:01   ` JH
2019-06-12  7:28     ` Richard Weinberger
2019-06-12 10:26     ` Sergei Poselenov [this message]
2019-06-13 10:41       ` JH

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=b931537d9268184b1c98e316a6b95a72847bbe69.camel@emcraft.com \
    --to=sposelenov@emcraft.com \
    --cc=jupiter.hce@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).