public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Compiling U-Boot
Date: Wed, 27 Nov 2013 14:39:25 +0100	[thread overview]
Message-ID: <5295F60D.5030304@gmail.com> (raw)
In-Reply-To: <5295E4FE.3000004@xtech2.lv>

Dear Alexey Smishlayev,

On 11/27/2013 01:26 PM, Alexey Smishlayev wrote:
> Hello!
> I would like to compile U-Boot with custom configuration.
> I downloaded source from the master git repository
> (http://git.denx.de/?p=u-boot.git;a=summary).
> I am trying to compile using following commands:
> $ cd u-boot/
> $ make ARCH=arm CROSS_COMPILE=arm-unknown-linux-gnu-
> at91sam9g20ek_nandflash_config
> $ make ARCH=arm CROSS_COMPILE=arm-unknown-linux-gnu- all

seems good to me.

> It goes on for a while, and then I get the error:
> crt0.S: Assembler messages:
> crt0.S:70: Error: register expected, not '#(184)' -- `sub sp,#(184)'
>
> make[1]: *** [crt0.o] Error 1
> make[1]: Leaving directory `/root/u-boot/arch/arm/lib'
> make: *** [arch/arm/lib/built-in.o] Error 2

crt0.S:70 subtracts the GD_SIZE from current stack pointer. The code
written seems to miss the Rn according to [1]. Could you please test to
change it from to: 'sub sp, sp, #GD_SIZE'?

I wonder why my toolchain ignore this. It obviously take Rd == Rn when
Rn is missing.

Best regards

Andreas Bie?mann

[1]
http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001m/QRC0001_UAL.pdf

  reply	other threads:[~2013-11-27 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 12:26 [U-Boot] Compiling U-Boot Alexey Smishlayev
2013-11-27 13:39 ` Andreas Bießmann [this message]
2013-11-27 13:53   ` Alexey Smishlayev
2013-11-27 13:59     ` Andreas Bießmann

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=5295F60D.5030304@gmail.com \
    --to=andreas.devel@googlemail.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