From: VOC <vishnuc80@yahoo.co.in>
To: u-boot@lists.denx.de
Subject: [U-Boot] u boot error
Date: Tue, 29 Jun 2010 06:35:29 -0700 (PDT) [thread overview]
Message-ID: <29023668.post@talk.nabble.com> (raw)
In-Reply-To: <20100629124911.0787014EBF8@gemini.denx.de>
Hi,
I am using uboot and atmel patch from
http://://www.at91.com/linux4sam/bin/view/Linux4SAM/U-Boot
http://://www.at91.com/linux4sam/bin/view/Linux4SAM/U-Boot . I hope I' not
doing some mistakes.
wd wrote:
>
> Dear VOC,
>
> In message <29023152.post@talk.nabble.com> you wrote:
>>
>> Hi,
>>
>> i am trying to build the uboot for at91sam9xeek board.But while building
>> the
>> uboot by using cross compiler it gives some error from start.s
>> file.Please
>> let me know how can I correct it.
>>
>> I tried the same for at91sam9260 board also.I gives the same error.
>>
>> arm-linux-as -o start.o start.s
>> start.s: Assembler messages:
>> start.s:387: Error: symbol `irq' is already defined
>> start.s:393: Error: symbol `fiq' is already defined
>> make[1]: *** [start.o] Error 1
>> make[1]: Leaving directory
>> `/root/test/ubootAtmel/uBootNew/u-boot-1.3.4/u-boot-1.3.4/cpu/arm926ejs
>
> I cannot confirm this. Current code builds just fine:
>
> MAKEALL_LOGDIR=/work/wd/tmp-arm-LOG \
> BUILD_DIR=/work/wd/tmp-arm \
> ./MAKEALL at91sam9xeek
> ... with environment variable in SPI DATAFLASH CS1
> Configuring for at91sam9xeek board...
> cpu.c:26:2: warning: #warning Your board is using legacy SoC access.
> Please update!
> text data bss dec hex filename
> 170718 7563 267520 445801 6cd69 /work/wd/tmp-arm/u-boot
>
> --------------------- SUMMARY ----------------------------
> Boards compiled: 1
> Boards with warnings or errors: 1 ( at91sam9xeek )
> ----------------------------------------------------------
>
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> The biggest difference between time and space is that you can't reuse
> time. - Merrick Furst
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>
http://old.nabble.com/file/p29023668/UBOOTERROR UBOOTERROR
--
View this message in context: http://old.nabble.com/u-boot-error-tp29023152p29023668.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-06-29 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 12:34 [U-Boot] u boot error VOC
2010-06-29 12:49 ` Wolfgang Denk
2010-06-29 13:35 ` VOC [this message]
2010-06-29 14:16 ` 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=29023668.post@talk.nabble.com \
--to=vishnuc80@yahoo.co.in \
--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.