From: Fabio Estevam <fabio.estevam@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] ARM: mx31pdk: Use the new relocation scheme
Date: Mon, 7 Feb 2011 09:32:32 -0200 [thread overview]
Message-ID: <4D4FD850.3050800@freescale.com> (raw)
In-Reply-To: <4D4E8E11.2010906@gmail.com>
Hi Magnus,
On 2/6/2011 10:03 AM, Magnus Lilja wrote:
...
> I've done some testing now and ended up comparing start.S for ARM1136 with ARM926EJS since
> the latter is used on the Karo TX25 board which seems to have been updated and
> also boots from NAND.
Thanks for looking into this.
> The result is that applying the following patch on top of Fabios patch makes the i.MX31 PDK
> boot from NAND. Booting Linux from TFTP works nicely. However the first few lines of output
> from U-boot is missing, only the "NAND: 256 MB" line is shown. I haven't tried to understand
> how booting works nowadays and why these changes work, perhaps someone with more insight
> in the mechanisms can figure out the correct assembler code.
I think that the missing lines can be fixed by using a similar approach as to this patch:
http://git.denx.de/?p=u-boot.git;a=commitdiff;h=877eb0f91543dc5bca385bb6d22454b1d43f3e2d
> I have no idea if this breaks other boards but at least it's start for further work. I tried
> it on the imx31 litekit (which boots from NOR) but that board doesn't seem to boot even before applying Fabios patch,
> I'll see if I can figure out why that board is broken now. Don't know when though.
I will let others comment about the changes you did in arch/arm/cpu/arm1136/start.S
Will also try it later today.
Thanks,
Fabio Estevam
> Regards, Magnus Lilja
>
> diff --git a/arch/arm/cpu/arm1136/start.S b/arch/arm/cpu/arm1136/start.S
> index 12545c2..7d75ecf 100644
> --- a/arch/arm/cpu/arm1136/start.S
> +++ b/arch/arm/cpu/arm1136/start.S
> @@ -163,6 +163,9 @@ call_board_init_f:
> bic sp, sp, #7 /* 8-byte alignment for ABI compliance */
> ldr r0,=0x00000000
>
> +#if 1
> + bl board_init_f
> +#else
> #ifdef CONFIG_NAND_SPL
> bl nand_boot
> #else
> @@ -172,6 +175,7 @@ call_board_init_f:
> bl board_init_f
> #endif /* CONFIG_ONENAND_IPL */
> #endif /* CONFIG_NAND_SPL */
> +#endif
>
> /*------------------------------------------------------------------------------*/
>
> @@ -266,11 +270,19 @@ clbss_l:str r2, [r0] /* clear loop... */
> * initialization, now running from RAM.
> */
> #ifdef CONFIG_NAND_SPL
> +#if 1
> + ldr r0, _nand_boot_ofs
> + mov pc, r0
> +
> +_nand_boot_ofs:
> + .word nand_boot
> +#else
> ldr r0, _nand_boot_ofs
> adr r1, _start
> add pc, r0, r1
> _nand_boot_ofs:
> .word nand_boot - _start
> +#endif
> #else
> jump_2_ram:
> ldr r0, _board_init_r_ofs
>
next prev parent reply other threads:[~2011-02-07 11:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 12:49 [U-Boot] [RFC] ARM: mx31pdk: Use the new relocation scheme Fabio Estevam
2011-01-13 13:38 ` Stefano Babic
2011-01-14 18:33 ` Fabio Estevam
2011-02-06 12:03 ` Magnus Lilja
2011-02-06 15:07 ` Albert ARIBAUD
2011-02-07 11:32 ` Fabio Estevam [this message]
2011-02-07 14:13 ` Stefano Babic
2011-02-07 19:48 ` Magnus Lilja
2011-02-08 17:09 ` Fabio Estevam
2011-02-08 17:50 ` stefano babic
2011-02-08 19:26 ` Magnus Lilja
2011-02-08 20:18 ` stefano babic
2011-02-08 20:50 ` Albert ARIBAUD
2011-02-09 11:45 ` Fabio Estevam
2011-02-11 10:51 ` Aneesh V
2011-02-11 12:46 ` Albert ARIBAUD
2011-02-11 13:49 ` Aneesh V
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=4D4FD850.3050800@freescale.com \
--to=fabio.estevam@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.