From: S. Egbert <s.egbert@sbcglobal.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Regarding memory commands
Date: Thu, 09 Feb 2006 00:53:29 -0800 [thread overview]
Message-ID: <43EB0309.8090901@sbcglobal.net> (raw)
In-Reply-To: <2195AF8E2250C54D8D8A726C8AE84A3331C338@dbde01.ent.ti.com>
Because it is essentially a file-store system and is not easily memory
mappable in a direct sense of a word, the current memory command sets
would not be easily extensible to cover this.
Closer examination of the U-boot cmd_nand.c shows that this is already
done (Thanks Wolfgang and gang!)
A snippet of the NAND usage is given below:
"nand - NAND sub-system\n",
"info - show available NAND devices\n"
"nand device [dev] - show or set current device\n"
"nand read[.jffs2[s]] addr off size\n"
"nand write[.jffs2] addr off size - read/write `size' bytes
starting\n"
" at offset `off' to/from memory address `addr'\n"
"nand erase [clean] [off size] - erase `size' bytes from\n"
" offset `off' (entire device if not specified)\n"
"nand bad - show bad blocks\n"
"nand read.oob addr off size - read out-of-band data\n"
"nand write.oob addr off size - read out-of-band data\n"
S. Egbert
Herekar, Aniruddha wrote:
>
> As you said memory commands work in any memory region, is it only the
> internal flash memory or also external flash memory? By external memory
> I mean to say that the NOR or NAND memory is not in the processor chip
> (ARM). But NOR/NAND memories have separate chip and memory is mapped on
> to the ARM memory map.
>
> I suppose NAND memory has different command set like nand info, etc.
> Then are these (mm, mw, md, etc) commands applicable for NAND memory
> also?
>
>
> Herekar, Aniruddha wrote:
>
>> Does memory commands mm, mw, mn and tftp work only with RAM memory and
>> not flash (nor or nand) memory?
>> If so are there any other commands other than 'cp' that can be used to
>> write into flash (nor or nand) memory?
>
> Basic memory commands (mm. mw) work in any memory region that the
> hardware supports.
>
> You will have to be mindful of certain memory and interface devices
> using only 16-bit or 8-bit access in a 32-bit architecture. Otherwise,
> such attempts to use 32-bit read/write will result in the most
> significant short-word or byte NOT to carry valid data value.
>
> TFTP does work writing directly into unprotected FLASH region if the
>
> CFG_DIRECT_FLASH_TFTP is defined in your include/configs/<board>.h file.
>
next prev parent reply other threads:[~2006-02-09 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 6:20 [U-Boot-Users] Regarding memory commands Herekar, Aniruddha
2006-02-09 8:53 ` S. Egbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-09 9:35 Herekar, Aniruddha
2006-02-09 9:35 Herekar, Aniruddha
2006-02-09 3:26 Herekar, Aniruddha
2006-02-09 5:48 ` S. Egbert
2006-02-09 9:03 ` 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=43EB0309.8090901@sbcglobal.net \
--to=s.egbert@sbcglobal.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox