From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] ARM: at91sam9m10g45ek: add mmc environment configuration support
Date: Wed, 21 May 2014 09:32:22 +0800 [thread overview]
Message-ID: <537C0226.6060506@atmel.com> (raw)
In-Reply-To: <1400582283-31625-2-git-send-email-josh.wu@atmel.com>
Hi Josh,
On 05/20/2014 06:38 PM, Josh Wu wrote:
> In this configuration the environment will save in file: uboot.env of
> mmc card.
>
> Signed-off-by: Josh Wu <josh.wu@atmel.com>
> ---
> boards.cfg | 1 +
> include/configs/at91sam9m10g45ek.h | 20 ++++++++++++++++++++
> 2 files changed, 21 insertions(+)
>
> diff --git a/boards.cfg b/boards.cfg
> index 3a59686..9f7cfd8 100644
> --- a/boards.cfg
> +++ b/boards.cfg
> @@ -102,6 +102,7 @@ Active arm arm926ejs at91 atmel at91sam9263ek
> Active arm arm926ejs at91 atmel at91sam9263ek at91sam9263ek_norflash at91sam9263ek:AT91SAM9263,SYS_USE_NORFLASH Stelian Pop <stelian@popies.net>
> Active arm arm926ejs at91 atmel at91sam9263ek at91sam9263ek_norflash_boot at91sam9263ek:AT91SAM9263,SYS_USE_BOOT_NORFLASH Stelian Pop <stelian@popies.net>
> Active arm arm926ejs at91 atmel at91sam9m10g45ek at91sam9m10g45ek_nandflash at91sam9m10g45ek:AT91SAM9M10G45,SYS_USE_NANDFLASH Bo Shen<voice.shen@atmel.com>
> +Active arm arm926ejs at91 atmel at91sam9m10g45ek at91sam9m10g45ek_mmc at91sam9m10g45ek:AT91SAM9M10G45,SYS_USE_MMC Bo Shen<voice.shen@atmel.com>
> Active arm arm926ejs at91 atmel at91sam9n12ek at91sam9n12ek_mmc at91sam9n12ek:AT91SAM9N12,SYS_USE_MMC Josh Wu <josh.wu@atmel.com>
> Active arm arm926ejs at91 atmel at91sam9n12ek at91sam9n12ek_nandflash at91sam9n12ek:AT91SAM9N12,SYS_USE_NANDFLASH Josh Wu <josh.wu@atmel.com>
> Active arm arm926ejs at91 atmel at91sam9n12ek at91sam9n12ek_spiflash at91sam9n12ek:AT91SAM9N12,SYS_USE_SPIFLASH Josh Wu <josh.wu@atmel.com>
> diff --git a/include/configs/at91sam9m10g45ek.h b/include/configs/at91sam9m10g45ek.h
> index df277e7..07b2188 100644
> --- a/include/configs/at91sam9m10g45ek.h
> +++ b/include/configs/at91sam9m10g45ek.h
> @@ -147,6 +147,7 @@
> #define CONFIG_SYS_MEMTEST_START CONFIG_SYS_SDRAM_BASE
> #define CONFIG_SYS_MEMTEST_END 0x23e00000
>
> +#ifdef CONFIG_SYS_USE_NANDFLASH
> /* bootstrap + u-boot + env in nandflash */
> #define CONFIG_ENV_IS_IN_NAND
> #define CONFIG_ENV_OFFSET 0xc0000
> @@ -162,6 +163,25 @@
> "256k(env),256k(env_redundant),256k(spare)," \
> "512k(dtb),6M(kernel)ro,-(rootfs) " \
> "root=/dev/mtdblock7 rw rootfstype=jffs2"
> +#elif CONFIG_SYS_USE_MMC
> +/* bootstrap + u-boot + env + linux in mmc */
> +#define FAT_ENV_INTERFACE "mmc"
> +#define FAT_ENV_DEVICE 0
> +#define FAT_ENV_PART 1
> +#define FAT_ENV_FILE "uboot.env"
> +#define CONFIG_ENV_IS_IN_FAT
> +#define CONFIG_FAT_WRITE
> +#define CONFIG_ENV_SIZE 0x4000
> +
> +#define CONFIG_BOOTARGS "mem=128M console=ttyS0,115200 " \
I think we should remove "mem=128M" as we use device tree.
> + "mtdparts=atmel_nand:" \
> + "8M(bootstrap/uboot/kernel)ro,-(rootfs) " \
> + "root=/dev/mmcblk0p2 " \
> + "rw rootfstype=ext4 rootwait"
Can we remove rootfstype, so it can compatible with ext2, ext3 and ext4.
> +#define CONFIG_BOOTCOMMAND "fatload mmc 0:1 0x71000000 dtb; " \
> + "fatload mmc 0:1 0x72000000 uImage; " \
> + "bootm 0x72000000 - 0x71000000"
Can we switch to zImage? As we try to support multi-platform with single
image in kernel.
> +#endif
>
> #define CONFIG_BAUDRATE 115200
>
>
Best Regards,
Bo Shen
next prev parent reply other threads:[~2014-05-21 1:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 10:38 [U-Boot] [PATCH 1/2] ARM: at91sam9m10g45ek: enable mci0 support Josh Wu
2014-05-20 10:38 ` [U-Boot] [PATCH 2/2] ARM: at91sam9m10g45ek: add mmc environment configuration support Josh Wu
2014-05-21 1:32 ` Bo Shen [this message]
2014-05-21 2:31 ` Josh Wu
2014-05-21 1:27 ` [U-Boot] [PATCH 1/2] ARM: at91sam9m10g45ek: enable mci0 support Bo Shen
2014-05-21 2:33 ` Josh Wu
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=537C0226.6060506@atmel.com \
--to=voice.shen@atmel.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.