On 14-05-09 10:58 AM, Brian Karcz wrote:
Hi Bruce,
I'm not entirely familiar with the mechanism that gets the defconfig from the
BSP to the .config in work area, but here is how things currently look. The two
files aren't a direct match as there appear to be some formatting differences,
but the variables in the SOC/ARCH section seem to correlate partially (ie. it
knows its trying to build for an at91sam9x5 SOC).
defconfig:
CONFIG_ARCH_AT91=y
CONFIG_SOC_AT91SAM9260=y
CONFIG_SOC_AT91SAM9263=y
CONFIG_SOC_AT91SAM9G45=y
CONFIG_SOC_AT91SAM9X5=y
CONFIG_MACH_AT91SAM_DT=y
.config:
#
# Atmel AT91 Processor
#
# CONFIG_SOC_AT91RM9200 is not set
CONFIG_SOC_AT91SAM9260=y
# CONFIG_SOC_AT91SAM9261 is not set
CONFIG_SOC_AT91SAM9263=y
# CONFIG_SOC_AT91SAM9RL is not set
CONFIG_SOC_AT91SAM9G45=y
CONFIG_SOC_AT91SAM9X5=y
# CONFIG_SOC_AT91SAM9N12 is not set
#
# Atmel Non-DT world
#
CONFIG_ARCH_AT91_NONE=y
# CONFIG_ARCH_AT91RM9200 is not set
# CONFIG_ARCH_AT91SAM9260 is not set
# CONFIG_ARCH_AT91SAM9261 is not set
# CONFIG_ARCH_AT91SAM9263 is not set
# CONFIG_ARCH_AT91SAM9RL is not set
# CONFIG_ARCH_AT91SAM9G45 is not set
#
# AT91 Board Options
#
#
# Generic Board Type
#
# CONFIG_MACH_AT91SAM9_DT is not set
Given the fact that the ARCH and DT variables don't appear to match, it looks
like this might be device tree related.
The reason I asked is that in the past, the error you are seeing
was related to the machine not being properly defined in the
kernel's .config.
FWIW, assuming you have a full "defconfig", and not a "save_defconfig"
variant, the path from it to the final .config is pretty much a copy
into the kernel and a "make oldconfig", so nothing is thrown away
unless there is a missing dependency, or the Kconfig doesn't exist in
the given kernel.
It's worth checking via menuconfig to see if anything obvious is
missing, and trying some quick builds to rule out a bad configuration.
Bruce
I was hoping the code out of the box was going to be able to provide a demo
image that I could build and poke around in for some guidance. My ultimate goal
is to port the at91sam9x5ek machine definition to one for the at91sam9g20ek
demo board and then port THAT over to a custom machine based roughly off that
reference design.
-----Original Message-----
From: Bruce Ashfield [mailto:[email protected]]
Sent: Friday, May 09, 2014 9:55 AM
To: Brian Karcz; [email protected]
Subject: Re: [yocto] [meta-atmel] at91sam9x5ek: "no machine record defined"
failure for core-image-minimal
On 14-05-09 09:44 AM, Brian Karcz wrote:
Hi,
Not sure if this is the correct place to email this, but I've seen a
few other meta-atmel references so I figured I'd give it a shot.
I'm attempting to setup a core-image-minimal build using the
guidelines in the meta-atmel README for the at91sam9x5ek machine type.
When the kernel build goes to link, I get a "no machine record
defined" error. Is this something others are seeing in the meta-atmel demo
builds?
It's a pretty benign build setup according to the README:
git clone git://git.yoctoproject.org/poky
cd poky
git checkout dora-10.0.1 -b dora-10.0.1
git clone git://git.openembedded.org/meta-openembedded
cd meta-openembedded
git checkout 6572316557e742c2dc93848e4d560242bf0c3995 -b my_branch
cd ..
git clone http://github.com/linux4sam/meta-atmel
source oe-init-build-env /workspace/build-atmel
modify local.conf:
MACHINE ??= "at91sam9x5ek"
PACKAGE_CLASSES ?= "package_ipk"
modify bblayers.conf:
BBLAYERS ?= " \
/opt/poky/meta-atmel \
/opt/poky/meta \
/opt/poky/meta-yocto \
/opt/poky/meta-yocto-bsp \
/opt/poky/meta-openembedded/meta-oe \
/opt/poky/meta-openembedded/meta-networking \
"
bitbake core-image-minimal
Setting this up, I get the following build configuration and error:
/workspace/build-atmel$ bitbake core-image-minimal
Loading cache: 100%
|#####################################################################
|#################|
ETA: 00:00:00
Loaded 1782 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.20.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-12.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "at91sam9x5ek"
DISTRO = "poky"
DISTRO_VERSION = "1.5.1"
TUNE_FEATURES = "armv5 thumb dsp"
TARGET_FPU = "soft"
meta-atmel = "master:269066a8128d1e767deee64854a142e67451a5f2"
meta
meta-yocto
meta-yocto-bsp = "dora-10.0.1:8e410e9e46e3335458a7747cdd32e05f5c19ccbb"
meta-oe
meta-networking = "my_branch:6572316557e742c2dc93848e4d560242bf0c3995"
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_compile (log file is located at
/workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-
yocto-custom/3.10+AUTOINC+68f2c28207-r5/temp/log.do_compile.2291)
ERROR: Logfile of failure stored in:
/workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-
yocto-custom/3.10+AUTOINC+68f2c28207-r5/temp/log.do_compile.2291
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 2 zImage CC=arm-poky-linux-gnueabi-gcc
-mno-thumb-interwork -marm LD=arm-poky-linux-gnueabi-ld.bfd
| GEN
/workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-
yocto-custom/3.10+AUTOINC+68f2c28207-r5/linux-at91sam9x5ek-standard-bu
ild/Makefile
| CHK include/generated/uapi/linux/version.h
| CHK include/generated/utsrelease.h
| Using
/workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-
yocto-custom/3.10+AUTOINC+68f2c28207-r5/linux
as source for kernel
| make[3]: `include/generated/mach-types.h' is up to date.
| CC scripts/mod/devicetable-offsets.s
| GEN scripts/mod/devicetable-offsets.h
| HOSTCC scripts/mod/file2alias.o
| CALL
/workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-
yocto-custom/3.10+AUTOINC+68f2c28207-r5/linux/scripts/checksyscalls.sh
| HOSTLD scripts/mod/modpost
| CHK include/generated/compile.h
| LINK vmlinux
| LD vmlinux.o
| MODPOST vmlinux.o
| GEN .version
| CHK include/generated/compile.h
| UPD include/generated/compile.h
| CC init/version.o
| LD init/built-in.o
| arm-poky-linux-gnueabi-ld.bfd: no machine record defined
| make[2]: *** [vmlinux] Error 1
| make[1]: *** [sub-make] Error 2
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at
/workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-
yocto-custom/3.10+AUTOINC+68f2c28207-r5/temp/log.do_compile.2291)
ERROR: Task 208
(/opt/poky/meta-atmel/recipes-kernel/linux/linux-yocto-custom_3.10.bb,
do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 793 tasks of which 785 didn't need to
be rerun and 1 failed.
Waiting for 0 running tasks to finish:
Summary: 1 task failed:
/opt/poky/meta-atmel/recipes-kernel/linux/linux-yocto-custom_3.10.bb,
do_compile
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Any thoughts on what might be missing from the README or my
implementation of it to get this demo build working?
Can you confirm that the final .config for the board has the machine
definitions that you'd expect for the board ?
Bruce
Thanks,
Brian
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
