From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Using u-boot to update the kernel and root-file system on NAND chip on imx28evk from USB memory stick
Date: Fri, 10 Aug 2012 18:26:52 -0500 [thread overview]
Message-ID: <502598BC.2000004@freescale.com> (raw)
In-Reply-To: <5022DB3E.8070406@techsi.com>
On 08/08/2012 04:33 PM, Bill wrote:
> All,
>
> I'm needing the ability to upgrade the kernel and root-filesystem on
> the NAND chip on the imx28evk from new files that reside on a USB memory
> stick. That is I want to partition the NAND (mtd) into 3 sections that
> contain u-boot, kernel, rootfs. Then whenever the system is booted,
> u-boot will probe the USB memory stick (using fatls and looking for a
> kernel file and rootfs file) If the files exist on the USB memory
> stick, uboot will automatically (first it will verify a CRC/Checksum)
> erase the kernel and rootfs sections on the NAND chip, and then copy the
> new kernel and rootfs from the USB stick to their respective sections in
> the flash chip (I think using fatload)?. It will never write a new u-boot.
>
> I've also seen where u-boot can define the NAND flash partitions
> using the mtdparts command and pass these along to the kernel via
> command line args?
>
> Can u-boot write/erase to a nand partition (i.e. /dev/mtd0) instead
> of using absolute memory addresses?
If you use U-Boot's mtdparts support, you can reference partitions by
name (mtdparts name, not Linux device node name) in NAND commands.
-Scott
next prev parent reply other threads:[~2012-08-10 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 21:33 [U-Boot] Using u-boot to update the kernel and root-file system on NAND chip on imx28evk from USB memory stick Bill
2012-08-10 23:26 ` Scott Wood [this message]
2012-08-11 0:10 ` Otavio Salvador
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=502598BC.2000004@freescale.com \
--to=scottwood@freescale.com \
--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.