All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Kinar <n.kinar@usask.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] Booting kernel from NAND flash on AT91SAM9 custom board using fsload
Date: Tue, 29 Mar 2011 11:37:25 -0600	[thread overview]
Message-ID: <4D9218D5.70608@usask.ca> (raw)
In-Reply-To: <4D920553.8040809@usask.ca>

On 29/03/2011 10:14 AM, Nicholas Kinar wrote:
> Also as instructed in the README.NAND, README.JFFS2 and
> README.JFFS2_NAND files found in the /doc/ directory, I've tried
> defining the following in my
> /include/configs/at91sam9rlek.h configuration file:
>
> #define CONFIG_JFFS2_NAND  1
> #define CONFIG_CMD_JFFS2
> #define CONFIG_SYS_MAX_FLASH_BANKS 1
> #define CONFIG_CMD_NAND        1
>

I've now added the following #undef to the list of defines above:

#undef CONFIG_CMD_FLASH

Now after typing "help" at the U-Boot command line, I can finally see 
the fsload command listed.  However running fsload gives the following 
error:

U-Boot> fsload
support for FLASH devices not present
incorrect device: nor0

This appears to be due to some code in the /common/cmd_jffs2.c file.  
Can fsload be only used for NOR memory, or is there a way to use it for 
NAND flash as well?

  reply	other threads:[~2011-03-29 17:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 16:14 [U-Boot] Booting kernel from NAND flash on AT91SAM9 custom board using fsload Nicholas Kinar
2011-03-29 17:37 ` Nicholas Kinar [this message]
2011-03-29 17:56   ` Scott Wood
2011-03-29 20:35     ` Nicholas Kinar
2011-03-29 20:46       ` Scott Wood
2011-03-29 20:57         ` Nicholas Kinar
2011-03-29 21:05       ` Wolfgang Denk
2011-03-29 21:46         ` Nicholas Kinar
2011-03-29 21:51           ` Wolfgang Denk
2011-04-02 17:38             ` Nicholas Kinar
2011-04-03  1:50               ` Nicholas Kinar
2011-04-04  1:25                 ` Nicholas Kinar
2011-03-30  7:17         ` Joakim Tjernlund
2011-03-30  8:54           ` Wolfgang Denk

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=4D9218D5.70608@usask.ca \
    --to=n.kinar@usask.ca \
    --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.