From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Can I read env from RAM in uboot script?
Date: Tue, 29 Jan 2013 17:58:06 +0800 [thread overview]
Message-ID: <51079D2E.90607@atmel.com> (raw)
In-Reply-To: <1359419103.7974.169.camel@genx>
Hi John Stile,
On 01/29/2013 08:25 AM, John Stile wrote:
[snip]
> I saw that.
>
> I tried to update u-boot-1.3.4 to u-boot-2013.
>
> I changed at91bootstrap's JUMP_ADDR from 0x23F00000 to 0x21F00000, as
> advised by previous posts.
>
> Now I am getting the wrong board type error from the kernel.
> my board is an AT91SAM9G20EK_2MMC
>
> I am having a hard time setting:
> #define MACH_TYPE_AT91SAM9G20EK_2MMC 2288
> insted of
> #define MACH_TYPE_AT91SAM9G20EK 1624
>
> In had to change buildroot's .config from:
> BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek_2mmc_nandflash"
> to
> BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek_nandflash"
> whihch I suspect is the problem.
>
> I'm trying to change the buildroots output/build/uboot-custom manually,
> and rerun the build, but no luck yet.
>
> My kernel is built with CONFIG_MACH_AT91SAM9G20EK_2MMC=y
>
> So how do I force u-boot to agree?
Please have test with the following patch (add at91sam9g20ek 2mmc
nandflash boot support) and check whether it will solve you problem.
You should use at91sam9g20ek_2mmc_nandflash to configure the u-boot
------------------------------------------------
diff --git a/board/atmel/at91sam9260ek/at91sam9260ek.c
b/board/atmel/at91sam9260ek/at91sam9260ek.c
index 2555672..ce475df 100644
--- a/board/atmel/at91sam9260ek/at91sam9260ek.c
+++ b/board/atmel/at91sam9260ek/at91sam9260ek.c
@@ -157,6 +157,10 @@ int board_early_init_f(void)
int board_init(void)
{
+#ifdef CONFIG_AT91SAM9G20EK_2MMC
+ /* arch number of AT91SAM9260EK-Board */
+ gd->bd->bi_arch_number = MACH_TYPE_AT91SAM9G20EK_2MMC;
+#else
#ifdef CONFIG_AT91SAM9G20EK
/* arch number of AT91SAM9260EK-Board */
gd->bd->bi_arch_number = MACH_TYPE_AT91SAM9G20EK;
@@ -164,6 +168,7 @@ int board_init(void)
/* arch number of AT91SAM9260EK-Board */
gd->bd->bi_arch_number = MACH_TYPE_AT91SAM9260EK;
#endif
+#endif
/* adress of boot parameters */
gd->bd->bi_boot_params = CONFIG_SYS_SDRAM_BASE + 0x100;
diff --git a/boards.cfg b/boards.cfg
index e4b0d44..fa863dc 100644
--- a/boards.cfg
+++ b/boards.cfg
@@ -95,6 +95,7 @@ at91sam9g10ek_nandflash arm arm926ejs
at91sam9261ek atmel
at91sam9g20ek_dataflash_cs0 arm arm926ejs at91sam9260ek
atmel at91
at91sam9260ek:AT91SAM9G20,SYS_USE_DATAFLASH_CS0
at91sam9g20ek_dataflash_cs1 arm arm926ejs at91sam9260ek
atmel at91
at91sam9260ek:AT91SAM9G20,SYS_USE_DATAFLASH_CS1
at91sam9g20ek_nandflash arm arm926ejs at91sam9260ek
atmel at91 at91sam9260ek:AT91SAM9G20,SYS_USE_NANDFLASH
+at91sam9g20ek_2mmc_nandflash arm arm926ejs at91sam9260ek
atmel at91
at91sam9260ek:AT91SAM9G20,AT91SAM9G20EK_2MMC,SYS_USE_NANDFLASH
at91sam9m10g45ek_nandflash arm arm926ejs at91sam9m10g45ek
atmel at91
at91sam9m10g45ek:AT91SAM9M10G45,SYS_USE_NANDFLASH
at91sam9rlek_dataflash arm arm926ejs at91sam9rlek
atmel at91 at91sam9rlek:AT91SAM9RL,SYS_USE_DATAFLASH
at91sam9rlek_nandflash arm arm926ejs at91sam9rlek
atmel at91 at91sam9rlek:AT91SAM9RL,SYS_USE_NANDFLASH
---------------------------------------------------------------------------
Best Regards,
Bo Shen
next prev parent reply other threads:[~2013-01-29 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 1:56 [U-Boot] Can I read env from RAM in uboot script? John Stile
2013-01-26 7:41 ` Wolfgang Denk
2013-01-28 21:19 ` John Stile
2013-01-28 21:48 ` Jeroen Hofstee
2013-01-28 22:01 ` Jeroen Hofstee
2013-01-29 0:25 ` John Stile
2013-01-29 9:58 ` Bo Shen [this message]
2013-01-29 17:33 ` John Stile
2013-01-30 1:20 ` Bo Shen
2013-01-29 6:37 ` 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=51079D2E.90607@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox