From: Eelco Chaudron <echaudron@xiot.nl>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot support for OrangePI PC
Date: Sun, 20 Dec 2015 13:32:43 +0100 [thread overview]
Message-ID: <56769FEB.60400@xiot.nl> (raw)
In-Reply-To: <56748758.7040908@mind.be>
Hi All,
I decided to give this a shot, but I already get stuck at doing the
u-boot part...
Looks like some toolchain issue, so before I dig into it more let me see
if some one here has ran into something similar.
This is my config:
BR2_armeb=y
BR2_cortex_a7=y
BR2_ARM_EABI=y
BR2_ARM_FPU_NEON_VFPV4=y
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BOARDNAME="orangepi_pc"
BR2_TARGET_UBOOT_CUSTOM_GIT=y
BR2_TARGET_UBOOT_CUSTOM_REPO_URL="http://git.denx.de/u-boot.git"
BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="4832e17787acb29734d895751bc7a594908aecc6"
BR2_TARGET_UBOOT_SPL=y
It all goes wrong when linking u-boot. Here are some snippets from the
output:
LD u-boot
/home/echaudron/buildroot_opi/output/host/usr/bin/armeb-buildroot-linux-uclibcgnueabi-ld.bfd:
Warning: size of symbol `invalidate_dcache_range' changed from 168 in
arch/arm/cpu/armv7/built-in.o to 4 in arch/arm/lib/built-in.o
/home/echaudron/buildroot_opi/output/host/usr/bin/armeb-buildroot-linux-uclibcgnueabi-ld.bfd:
Warning: size of symbol `enable_caches' changed from 4 in
arch/arm/cpu/armv7/built-in.o to 12 in arch/arm/lib/built-in.o
/home/echaudron/buildroot_opi/output/host/usr/bin/armeb-buildroot-linux-uclibcgnueabi-ld.bfd:
Warning: size of symbol `arm_init_before_mmu' changed from 40 in
arch/arm/cpu/armv7/built-in.o to 4 in arch/arm/lib/built-in.o
...
...
/home/echaudron/buildroot_opi/output/host/usr/bin/armeb-buildroot-linux-uclibcgnueabi-ld.bfd:
/home/echaudron/buildroot_opi/output/host/usr/lib/gcc/armeb-buildroot-linux-uclibcgnueabi/4.9.3/libgcc.a(_dvmd_lnx.o):
compiled for a big endian system and target is little endian
/home/echaudron/buildroot_opi/output/host/usr/bin/armeb-buildroot-linux-uclibcgnueabi-ld.bfd:
failed to merge target specific data of file
/home/echaudron/buildroot_opi/output/host/usr/lib/gcc/armeb-buildroot-linux-uclibcgnueabi/4.9.3/libgcc.a(_dvmd_lnx.o)
/home/echaudron/buildroot_opi/output/host/usr/bin/armeb-buildroot-linux-uclibcgnueabi-ld.bfd:
BFD (GNU Binutils) 2.24 assertion fail elf32-arm.c:12387
...
...
/home/echaudron/buildroot_opi/output/host/usr/bin/armeb-buildroot-linux-uclibcgnueabi-ld.bfd:
BFD (GNU Binutils) 2.24 assertion fail elf32-arm.c:12387
/home/echaudron/buildroot_opi/output/host/usr/bin/armeb-buildroot-linux-uclibcgnueabi-ld.bfd:
BFD (GNU Binutils) 2.24 assertion fail elf32-arm.c:12387
Segmentation fault (core dumped)
Makefile:1193: recipe for target 'u-boot' failed
make[2]: *** [u-boot] Error 139
When I build the same u-boot version using the ubuntu provided
"arm-linux-gnueabihf-" toolchain it works fine.
I'm using the following to build it;
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- orangepi_pc_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
Any ideas?
//Eelco
> Arnout Vandecappelle <mailto:arnout@mind.be>
> December 18, 2015 at 23:23
>
> Not that I know of. But it should be quite similar to the cubieboard I
> think.
>
> If you make a defconfig for it, consider using genimage rather than a
> custom
> script like mkcubiecard.
>
> Regards,
> Arnout
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151220/af382638/attachment.html>
next prev parent reply other threads:[~2015-12-20 12:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 13:22 [Buildroot] buildroot support for OrangePI PC Eelco Chaudron
2015-12-18 22:23 ` Arnout Vandecappelle
2015-12-20 12:32 ` Eelco Chaudron [this message]
2015-12-20 12:45 ` Thomas Petazzoni
2015-12-20 18:17 ` Eelco Chaudron
2015-12-20 18:25 ` Eelco Chaudron
2015-12-24 9:15 ` Eelco Chaudron
2015-12-24 10:28 ` Thomas Petazzoni
2015-12-24 10:52 ` Eelco Chaudron
2015-12-24 11:18 ` Thomas Petazzoni
2015-12-27 0:04 ` Cam Hutchison
2015-12-19 23:51 ` Cam Hutchison
2015-12-20 12:37 ` Thomas Petazzoni
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=56769FEB.60400@xiot.nl \
--to=echaudron@xiot.nl \
--cc=buildroot@busybox.net \
/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.