From: Friedrich Lobenstock <f.lobenstock@scottygroup.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] mcf5272 hanging while relocating
Date: Thu, 02 Jun 2005 01:06:40 +0200 [thread overview]
Message-ID: <429E3F80.6000807@scottygroup.com> (raw)
In-Reply-To: <200506010943.19087.ngustavson@emacinc.com>
NZG wrote on 01.06.2005 16:43 MET:
>
>>Back to the real thread, if you could mail me privately how you got your
>>toolchain set up I would be very grateful. I've got the Cybertec's
>>Crossfire Tools for Linux <http://www.cybertec.com.au/crossfire.htm> but I
>>think as the option "-msep_data" is not supported that this is the missing
>>link to my problem of the missing GOT table. Using the stuff from
>><http://www.uclinux.org/pub/uClinux/m68k-elf-tools/gcc-3/> fails during
>>compile.
>
> I'm actually experimenting with several toolchains, but the most stable for me
> seems to be Gregs old pre-build one.
> You can get this directly off the uclinux website, but it appears to be down
> at the moment.
> We've also got it on our SoM ftp in the tools directory.
>
> ftp://SoM:sompublic at ftp.emacinc.com
Ok, got that one installed now. Now when I try to compile your version of
"Das-Uboot" configured for your board I get the same compile error when I
compile the standard uboot-1.1.2 configured for my board:
fl at linux:~/work/coldfire/uboot/Das-Uboot> make mrproper; make SOM5282EM_config;
make all
[...]
Configuring for SOM5282EM board...
[...]
make[1]: Leaving directory `/home/fl/work/coldfire/uboot/Das-Uboot/post/cpu'
m68k-elf-gcc -Wa,-gstabs -D__ASSEMBLY__ -g -Os -ffixed-d7 -msep-data
-D__KERNEL__ -DTEXT_BASE=0xf0000000
-I/home/fl/work/coldfire/uboot/Das-Uboot/include -fno-builtin -ffreestanding
-nostdinc -isystem /usr/lib/gcc-lib/i586-suse-linux/3.3.4/include -pipe
-DCONFIG_M68K -D__M68K__ -m5307 -c -o cpu/mcf52x2/start.o
/home/fl/work/coldfire/uboot/Das-Uboot/cpu/mcf52x2/start.S
/home/fl/work/coldfire/uboot/Das-Uboot/cpu/mcf52x2/start.S: Assembler messages:
/home/fl/work/coldfire/uboot/Das-Uboot/cpu/mcf52x2/start.S:421: Fatal error:
Tried to convert PC relative conditional branch to absolute jump
make: *** [cpu/mcf52x2/start.o] Fehler 1
("Fehler 1" .... "Errors 1")
I think there's a little problem in the uboot makefile, so I'll post a patch for
that soon to the u-boot mailinglist, but this one "only" relates to the includes
but does not solve the error message.
> This is a very valid Coldfire topic, so I don't really want to do this off
> list, but since your not really talking about using u-boot, you probably
> should move over to wildrice, you'll probably find more support in this area
> there.
>
> http://www.wildrice.com/ColdFire/
>
> (I know it looks a little clunky, but trust me it's very active)
Ok, I'm posting to both lists now and reply-to set to the coldfire list.
--
MfG / Regards
Friedrich Lobenstock
prev parent reply other threads:[~2005-06-01 23:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 12:46 [U-Boot-Users] mcf5272 hanging while relocating Friedrich Lobenstock
2005-05-17 12:53 ` Wolfgang Denk
2005-05-17 13:31 ` Zachary Landau
2005-05-30 22:10 ` Friedrich Lobenstock
2005-05-30 22:53 ` Friedrich Lobenstock
2005-05-30 23:10 ` Friedrich Lobenstock
2005-05-31 15:23 ` NZG
2005-05-31 20:17 ` Friedrich Lobenstock
2005-05-31 21:18 ` NZG
2005-05-31 23:30 ` Friedrich Lobenstock
2005-06-01 14:43 ` NZG
2005-06-01 23:06 ` Friedrich Lobenstock [this message]
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=429E3F80.6000807@scottygroup.com \
--to=f.lobenstock@scottygroup.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