From: Dennis Eberstein <ebi@indalika.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-BOOT] [ERROR] Trouble Building uboot for A10s Allwinner red-brick
Date: Fri, 29 Jul 2016 16:49:11 +0200 [thread overview]
Message-ID: <e052e75ac0cbab72d3ef8424de07cfdb@indalika.de> (raw)
Hey U-Boot list,
I have some trouble with building U-BOOT for my Tinkerforge RED-Brick.
Its an Allwinner A10s powered little development SoC.
http://www.tinkerforge.com/de/doc/Hardware/Bricks/RED_Brick.html thats
all german.
I just made myself a Configuration, you will find it in the attachments.
Than I typed make all and got:
cmd/bootm.c: In function 'do_imls_nor':
cmd/bootm.c:332:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first
use in this function)
i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {
^
cmd/bootm.c:332:7: note: each undeclared identifier is reported only
once for each function it appears in
scripts/Makefile.build:280: recipe for target 'cmd/bootm.o' failed
make[1]: *** [cmd/bootm.o] Error 1
Makefile:1211: recipe for target 'cmd' failed
make: *** [cmd] Error 2
I fixed by putting a CONFIG_SYS_MAX_FLASH_BANKS into
include/configs/sunxi-common.h
Than I ran into this one:
CC common/menu.o
CC common/usb_kbd.o
CC common/env_common.o
In file included from include/configs/sunxi-common.h:495:0,
from include/configs/sun5i.h:25,
from include/config.h:5,
from include/common.h:18,
from common/env_common.c:11:
include/config_distro_bootcmd.h:309:2: error: expected '}' before
'BOOT_TARGET_DEVICES_references_PXE_without_CONFIG_CMD_DHCP_or_PXE'
BOOT_TARGET_DEVICES_references_PXE_without_CONFIG_CMD_DHCP_or_PXE
^
include/config_distro_bootcmd.h:313:2: note: in expansion of macro
'BOOTENV_DEV_NAME_PXE'
BOOTENV_DEV_NAME_##devtypeu(devtypeu, devtypel, instance)
^
include/configs/sunxi-common.h:476:2: note: in expansion of macro
'BOOTENV_DEV_NAME'
func(PXE, pxe, na) \
^
include/config_distro_bootcmd.h:315:18: note: in expansion of macro
'BOOT_TARGET_DEVICES'
"boot_targets=" BOOT_TARGET_DEVICES(BOOTENV_DEV_NAME) "\0"
^
include/config_distro_bootcmd.h:332:2: note: in expansion of macro
'BOOTENV_BOOT_TARGETS'
BOOTENV_BOOT_TARGETS \
^
include/configs/sunxi-common.h:527:2: note: in expansion of macro
'BOOTENV'
BOOTENV
^
include/env_default.h:108:2: note: in expansion of macro
'CONFIG_EXTRA_ENV_SETTINGS'
CONFIG_EXTRA_ENV_SETTINGS
^
scripts/Makefile.build:280: recipe for target 'common/env_common.o'
failed
make[1]: *** [common/env_common.o] Error 1
Makefile:1210: recipe for target 'common' failed
make: *** [common] Error 2
I cannot see why there should be a } out of nothing...
I tried this all with multiple versions: The Git master, the sunxi
overlay, the 2016.09 version from FTP and the 2016.07 relase. Everywhere
the same results.
What do I do wrong?
Would appreciate any help on this.
Thanks in advance
Tinkerforge has just not gone to Mainline uboot. They run it with the
sunxi-uboot right now. They didn't have the time to do the update yet.
So now I am on it, because I want to run my favourite distro on it. And
that would need a halfway actual Kernel. More something like 4.x not 3.x
what the have.
Best regards
Dennis
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: u-boot_config.txt
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160729/d78fa79b/attachment.txt>
reply other threads:[~2016-07-29 14:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e052e75ac0cbab72d3ef8424de07cfdb@indalika.de \
--to=ebi@indalika.de \
--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