Your external issue tracker seems to be offline.

Description

rpi-test-image is un-buildable

The problem above is that I was following the instructions of the README of morty branch, and it does not mention dependencies on "meta-oe/meta-networking" and "meta-oe/meta-python". The rpi-test-image requires previously mentioned layers.

Creating this issue so that I wont forget to update the documentation.

Question:

Shall we first convert README to markdown as we was done in master branch? And then update dependencies? Or the other way around?

Steps to reproduce the issue:

mirza@b58ada3e9601:~/project/raspberrypi/build$ bitbake rpi-test-image
WARNING: Host distribution "DebianGNULinux-8" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Parsing recipes: 100% |#############################################################################################################################################################################| Time: 0:00:23
Parsing of 1568 .bb files complete (0 cached, 1568 parsed). 2131 targets, 145 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'crda' (but /home/mirza/project/raspberrypi/layers/meta-raspberrypi/recipes-core/packagegroups/packagegroup-rpi-test.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'crda' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['crda']
NOTE: Runtime target 'packagegroup-rpi-test' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-rpi-test', 'crda']
ERROR: Required build target 'rpi-test-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['rpi-test-image', 'packagegroup-rpi-test', 'crda']

Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

A quick question about sdimg file after building meta-raspberrypi. I have got rpi-hwup-image-raspberrypi-20170405083420.rootfs.tar.bz2 and bcm2835-bootfiles folder. I cannot see any file which says sdimg.

Build Configuration:
BB_VERSION = "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi"
DISTRO = "poky"
DISTRO_VERSION = "2.2"
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "master:e016eb10b075e280b4e78a04e47b59a173386421"
meta-raspberrypi = "master:da32aac453da278e254d37b816602410af85d162"

local.conf:
MACHINE ??= "raspberrypi"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS = "
STOPTASKS,${TMPDIR},1G,100K
STOPTASKS,${DL_DIR},1G,100K
STOPTASKS,${SSTATE_DIR},1G,100K
STOPTASKS,/tmp,100M,100K
ABORT,${TMPDIR},100M,1K
ABORT,${DL_DIR},100M,1K
ABORT,${SSTATE_DIR},100M,1K
ABORT,/tmp,10M,1K"
CONF_VERSION = "1"
IMAGE_FSTYPES = "tar.bz2 ext3.xz"

The image files in tmp/deploy/images/raspberrypi, after building successfully are as follows:
modules-1-4.9.13+git0+28ea32b9af-r0-raspberrypi-20170405083420.tgz
rpi-hwup-image-raspberrypi-20170405083420.rootfs.ext3.xz
rpi-hwup-image-raspberrypi-20170405083420.rootfs.tar.bz2
bcm2835-bootfiles (folder).

I am not sure which mailing-list I can post this question/issue, therefore please let me know if it is a known issue or if this may not be a suitable place to post this issue. Thanks.

There is currently one Waveshare display supported (here).
It is being done by setting variable WAVESHARE_1024X600_C_2_1

if [ "${WAVESHARE_1024X600_C_2_1}" = "1" ]; then
# set some configuraton.
fi

I am going to add support for different displays (which have different parameters). I am thinking about doing it in way like this:

if [ "${HDMI_DISPLAY_TYPE}" = "WAVESHARE_7_INCH_LCD_C" ] || [ "${WAVESHARE_1024X600_C_2_1}" = "1" ]; then 
# config
elif [ "${HDMI_DISPLAY_TYPE}" = "WAVESHARE_10_1_INCH_LCD_B" ]; then 
# config
elif [ "${HDMI_DISPLAY_TYPE}" = "WAVESHARE_10_1_INCH_LCD_B_ALTERNATE" ]; then
# config
fi

First line is for backward compatibility. Is that needed?
According to naming convention I would stick with naming from their wiki which contains configuration parameters.
On the other hand, those configs differ mostly with hdmi_cvt parameter which corresponds to resolution, and sometimes with hdmi_mode. I am playing around with this one and i had to use alternate configuration.
Maybe we should stick with resolution based naming, and some other variable for alternate hdmi_mode, or one value per configuration with _ALTERNATE suffix? or _MODE_27, '_MODE_87`

This was tested on current master. Only poky/master and meta-raspberrypi/master in bblayers.conf.

After starting a devtool modify linux-raspberrypi session, building the kernel fails with the following log. Any suggestion where to look for troubleshooting this?

MACHINE="raspberrypi3" devtool build linux-raspberrypi

Build Configuration:
BB_VERSION        = "1.33.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "raspberrypi3"
DISTRO            = "poky"
DISTRO_VERSION    = "2.2+snapshot-20170228"
TUNE_FEATURES     = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7"
TARGET_FPU        = "hard"
meta              
meta-poky         
meta-yocto-bsp    = "master:3c83b56309ab419f8cda72c0711479f60f61439a"
meta-raspberrypi  = "master:c768a3d1aed8d16d08afe12fddb359914e0a203a"
workspace         = "<unknown>:<unknown>"

Initialising tasks: 100% |###########################################################################################################################################################################| Time: 0:00:00
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: linux-raspberrypi-1_4.4.48+git999-r0 do_configure: oe_runmake failed
ERROR: linux-raspberrypi-1_4.4.48+git999-r0 do_configure: Function failed: do_configure (log file is located at /scratch/gizero/poky-master-build/tmp/work/raspberrypi3-poky-linux-gnueabi/linux-raspberrypi/1_4.4.4
8+git999-r0/temp/log.do_configure.4531)
ERROR: Logfile of failure stored in: /scratch/gizero/poky-master-build/tmp/work/raspberrypi3-poky-linux-gnueabi/linux-raspberrypi/1_4.4.48+git999-r0/temp/log.do_configure.4531
Log data follows:
| DEBUG: Executing python function externalsrc_configure_prefunc
| DEBUG: Python function externalsrc_configure_prefunc finished
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing python function check_oldest_kernel
| DEBUG: Python function check_oldest_kernel finished
| DEBUG: Executing shell function do_configure
| NOTE: make HOSTCC=gcc  HOSTCPP=gcc  -E oldconfig
| ERROR: oe_runmake failed
| make: *** No rule to make target 'oldconfig'.  Stop.
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at /scratch/gizero/poky-master-build/tmp/work/raspberrypi3-poky-linux-gnueabi/linux-raspberrypi/1_4.4.48+git999-r0/temp/log.do_configure.4531)
ERROR: Task (/home/gizero/work/upstreaming/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 452 tasks of which 128 didn't need to be rerun and 1 failed.

Hi,
I don't know if this is an issue, I have compiled a console-image recipe for raspberry pi3 successfully.
I have setted up the wifi to have internet connection and now I would like to set apt properly to use Raspbian repository for upgrade and mainteinance.
I have added the official repository URL into sources.list but when I have tried to install something or just upgrade with apt-get upgrade I have a "Broken pipe" error from dpkg.
I think it is not so easy like just I have done.
Is it really possible to use apt-get for maintenance of a Yocto based distro?

Did anybody manage to make this display work with raspberry pi3?
In kernel config display drivers are being built as modules, but still no luck. LCD shows just white screen the moment I put power on. Tried to do some "echo 0 > /dev/fb0" and "tail -f /dev/input/touchscreen0", no reactions on touch too.

When I add bcm2835 to my IMAGE_INSTALL variable, the do_rootfs step of my image fails, i think because no bcm2835 package is generated (as it would be empty). In my log.do_rootfs:

...
Unknown package 'bcm2835'.
...
Collected errors:
 * opkg_install: Cannot install package bcm2835.
...

And indeed, no bcm2835 package is generated:

$ ls -1 tmp/deploy/ipk/cortexa7hf-neon-vfpv4/*bcm2835*
tmp/deploy/ipk/cortexa7hf-neon-vfpv4/bcm2835-dbg_1.46-r0_cortexa7hf-neon-vfpv4.ipk
tmp/deploy/ipk/cortexa7hf-neon-vfpv4/bcm2835-dev_1.46-r0_cortexa7hf-neon-vfpv4.ipk
tmp/deploy/ipk/cortexa7hf-neon-vfpv4/bcm2835-staticdev_1.46-r0_cortexa7hf-neon-vfpv4.ipk
tmp/deploy/ipk/cortexa7hf-neon-vfpv4/bcm2835-tests_1.46-r0_cortexa7hf-neon-vfpv4.ipk

By allowing an empty package to be created, the do_rootfs step finishes cleanly.

diff --git a/recipes-devtools/bcm2835/bcm2835_1.46.bb b/recipes-devtools/bcm2835/bcm2835_1.46.bb
index dd37b8f..09fcab8 100644
--- a/recipes-devtools/bcm2835/bcm2835_1.46.bb
+++ b/recipes-devtools/bcm2835/bcm2835_1.46.bb
@@ -35,6 +35,8 @@ do_install_append() {

 PACKAGES += "${PN}-tests"

+ALLOW_EMPTY_${PN} = "1"
+
 FILES_${PN} = ""
 FILES_${PN}-tests = "${libdir}/${BPN}"
 FILES_${PN}-dbg += "${libdir}/${BPN}/.debug"

Am I doing something wrong? Am I supposed to put bcm2835 somewhere else than IMAGE_INSTALL, or am I supposed to used something else than bcm2835?

There are currently multiple issues regarding the device tree binary handling. Currently all dtb's are specified in the rpi-base.inc. But this causes multiple isses by different kernel recipes. For example the Kernel 3.18 doesn't provide the bcm2710-rpi-3-b.dtb

| make[3]: *** No rule to make target 'arch/arm/boot/dts/bcm2710-rpi-3-b.dtb'. Stop. | make[2]: *** [bcm2710-rpi-3-b.dtb] Error 2 | make[1]: *** [sub-make] Error 2 | make: *** [__sub-make] Error 2 | ERROR: oe_runmake failed | ERROR: Function failed: do_compile (log file is located at /builds/raspberrypi3/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-raspberrypi/1_3.18.16+gitAUTOINC+1bb18c8f72-r0/temp/log.do_compile.24045)

Same issue applies to the pitft22-overlay.dtb. This dtb is currently handled for each kernel version explicitly. New kernel version (such as linux-raspberrypi_4.4.bb) needs to add the patch-file again.
| NOTE: make -j 8 overlays/pitft22-overlay.dtb | make[3]: *** No rule to make target 'arch/arm/boot/dts/overlays/pitft22-overlay.dtb'. Stop. | make[2]: *** [overlays/pitft22-overlay.dtb] Error 2 | make[1]: *** [sub-make] Error 2 | make: *** [__sub-make] Error 2 | ERROR: oe_runmake failed | ERROR: Function failed: do_compile (log file is located at /storage/builds/raspberrypi3/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-raspberrypi/1_4.4.3+gitAUTOINC+a2c8f5b320-r0/temp/log.do_compile.27266)

So in this case I would suggest a machine specific devite-tree handling

I'm running an Adafruit GPS Hat on a Raspberry Pi 2. The pins on that product are mapped to the TXD0/RXD0 pins and should be available through /dev/ttyAMA0. Is there a way I can use a dtoverlay option to override "console=serial0,115200", skip the firmware's search-and-replace, and just shove "console=tty1" in there to free up /dev/ttyAMA0? I believe this should be a configuration parameter I could change in a bbappend in my own OpenEmbedded layer. This is related to the discussion here: RPi-Distro/repo#22

When I try to build all the packages in morty branch, I have couple errors:

ERROR: Nothing PROVIDES 'virtual/libgles1' (but /home/gumstix/Buildbot/yocto-raspberrypi3-morty/build/poky/meta/recipes-graphics/mesa/mesa-demos_8.3.0.bb DEPENDS on or otherwise requires it)
ERROR: mesa PROVIDES virtual/libgles1 but was skipped: PREFERRED_PROVIDER_virtual/libgl set to mesa-gl, not mesa
ERROR: mesa PROVIDES virtual/libgles1 but was skipped: PREFERRED_PROVIDER_virtual/libgl set to mesa-gl, not mesa
ERROR: ti-sgx-ddk-um PROVIDES virtual/libgles1 but was skipped: PREFERRED_PROVIDER_virtual/egl set to userland, not ti-sgx-ddk-um

I fixed this by changing the rpi-default-providers.inc of virtual/egl, virtual/libgles2, virtual/libgl, virtual/mesa to mesa, then I have other errors:

ERROR: Nothing PROVIDES 'userland' (but /home/gumstix/Buildbot/yocto-raspberrypi_cm3-morty/build/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.8.3.bb DEPENDS on or otherwise requires it)
ERROR: userland was skipped: PREFERRED_PROVIDER_virtual/libgles2 set to mesa, not userland

I fixed this by changing the gstreamer1.0-plugins-bad_%.bbappend

-PACKAGECONFIG[dispmanx] = "--enable-dispmanx,--disable-dispmanx,userland"
+PACKAGECONFIG[dispmanx] = "--enable-dispmanx,--disable-dispmanx,virtual/egl virtual/libgles2"

and there seems no error.

Could you reproduce those problems and fix them upstream?

Steps to reproduce the issue:

1. Clone meta-openembedded, meta-raspberrypi, poky, meta-qt5 in morty branch
2. $ bitbake mesa-demos
3. $ bitbake gstreamer1.0-plugins-bad

Hi, please remove the "patch" file in the root of the master branch

(I guess something bad happened to my patch forwarding)

Hello,

I am trying to enable bluetooth in my Pi3 image so now i have

local.conf

MACHINE ??= "raspberrypi3"
IMAGE_FSTYPES = "rpi-sdimg"
IMAGE_INSTALL_append = "bluez5 wireless-tools linux-firmware-brcm43430 wpa-supplicant rpm"
DISTRO_FEATURES_append += " bluez5 bluetooth wifi systemd"
ENABLE_UART = "1"
MACHINE_FEATURES += " pi3-miniuart-bt"

bblayers.conf

BBLAYERS ?= "
/home/yocto/poky/meta
/home/yocto/poky/meta-poky
/home/yocto/poky/meta-yocto-bsp
/home/yocto/poky/meta-raspberrypi
/home/yocto/poky/meta-openembedded/meta-oe
"

hcitools does not show any bluetooth interface

and if i try set

KERNEL_DEVICETREE = "overlays/pi3-miniuart-bt-overlay.dtb"
in
meta-raspberrypi/recipes-core/images/rpi-basic-image.bb
or
local.conf

in both case i get rainbow screen in my HDMI screen and freeze after that

and if i try
Set KERNEL_DEVICETREE (in conf/machine/raspberrypi.conf) it's ignored the value whatever it is

i try following
raspberrypi/firmware#553
and
RPi-Distro/repo#22

and no luck

i don't want or use any of GPIO pin or serial so i don't mind disable it all if this will fix the bluetooth issue

Thanks

Hi, I'm getting this error when trying to run the build. Tried systems Lubuntu 16.10 and Lubuntu 16.04.
16.04 doesn't complain about being an unsupported distribution.

Here are the steps to reproduce the issue:

sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
     build-essential chrpath socat libsdl1.2-dev xterm
git clone http://git.yoctoproject.org/git/poky
cd poky
git checkout morty
export POKY_DIR=$PWD
git clone http://git.yoctoproject.org/git/meta-raspberrypi
source oe-init-build-env rpi-build
sed -i "11 a\  $POKY_DIR/meta-raspberrypi \\\\" conf/bblayers.conf
sed -i 's/MACHINE ??= "qemux86"/MACHINE ??= "raspberrypi2"/' conf/local.conf
bitbake rpi-hwup-image

It results in the following error:

ERROR: /home/user/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb: Error executing a python function in <code>:                                                                                          | ETA:  --:--:--

The stack trace of python calls that resulted in this exception/failure was:
File: '<code>', lineno: 18, function: <module>
     0014:__anon_18__home_user_poky_meta_recipes_kernel_linux_linux_yocto_inc(d)
     0015:__anon_364__home_user_poky_meta_classes_kernel_yocto_bbclass(d)
     0016:__anon_6__home_user_poky_meta_recipes_kernel_linux_linux_dtb_inc(d)
     0017:__anon_148__home_user_poky_meta_raspberrypi_recipes_kernel_linux_linux_rpi_inc(d)
 *** 0018:__anon_38__home_user_poky_meta_raspberrypi_recipes_kernel_linux_linux_raspberrypi_inc(d)
File: '/home/user/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi.inc', lineno: 36, function: __anon_38__home_user_poky_meta_raspberrypi_recipes_kernel_linux_linux_raspberrypi_inc
     0032:# Set programmatically some variables during recipe parsing
     0033:# See http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#anonymous-python-functions
     0034:python __anonymous () {
     0035:    kerneltype = d.getVar('KERNEL_IMAGETYPE')
 *** 0036:    kerneldt = get_dts(d, d.getVar('LINUX_VERSION'))
     0037:    d.setVar("KERNEL_DEVICETREE", kerneldt)
     0038:}
     0039:
     0040:do_kernel_configme_prepend() {
Exception: TypeError: getVar() missing 1 required positional argument: 'expand'

ERROR: Failed to parse recipe: /home/user/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb
ERROR: /home/user/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb: Error executing a python function in <code>:

The stack trace of python calls that resulted in this exception/failure was:
File: '<code>', lineno: 18, function: <module>
     0014:__anon_18__home_user_poky_meta_recipes_kernel_linux_linux_yocto_inc(d)
     0015:__anon_364__home_user_poky_meta_classes_kernel_yocto_bbclass(d)
     0016:__anon_6__home_user_poky_meta_recipes_kernel_linux_linux_dtb_inc(d)
     0017:__anon_148__home_user_poky_meta_raspberrypi_recipes_kernel_linux_linux_rpi_inc(d)
 *** 0018:__anon_38__home_user_poky_meta_raspberrypi_recipes_kernel_linux_linux_raspberrypi_inc(d)
File: '/home/user/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi.inc', lineno: 36, function: __anon_38__home_user_poky_meta_raspberrypi_recipes_kernel_linux_linux_raspberrypi_inc
     0032:# Set programmatically some variables during recipe parsing
     0033:# See http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#anonymous-python-functions
     0034:python __anonymous () {
     0035:    kerneltype = d.getVar('KERNEL_IMAGETYPE')
 *** 0036:    kerneldt = get_dts(d, d.getVar('LINUX_VERSION'))
     0037:    d.setVar("KERNEL_DEVICETREE", kerneldt)
     0038:}
     0039:
     0040:do_kernel_configme_prepend() {
Exception: TypeError: getVar() missing 1 required positional argument: 'expand'

Hi,

I've got strange problem about 'taskhash mismatch' when I try to rebuild core-image-minimal after a 'cleansstate'.

ERROR: core-image-minimal-1.0-r0 do_image_rpi_sdimg: Taskhash mismatch 1b48d92377c7cedb58231830828f590b verses 92b3b86f0e026e3159ba0f71477c092a for /media/pierre/SAMSUNG_EXT4/Yocto/krogoth/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg
ERROR: Taskhash mismatch 1b48d92377c7cedb58231830828f590b verses 92b3b86f0e026e3159ba0f71477c092a for /media/pierre/SAMSUNG_EXT4/Yocto/krogoth/meta/recipes-core/images/core-image-minimal.bb.do_image_rpi_sdimg

Looks like the commit cd338c2 added the following line to classes/sdcard_image-rpi.bbclass :

IMAGE_CMD_rpi-sdimg[vardepsexclude] = "IMAGEDATESTAMP"

If I comment the line, everything works fine... Actually i should admit I don't really understand the use of that line (and the Yocto documentation):

vardepsexclude: Specifies a space-separated list of variables that should be excluded from a variable's dependencies for the purposes of calculating its signature.

regards

I verified that NOOBS 1.9 boots correctly.

My Pi3 image (MACHINE = "raspberrypi3") just shows 4 raspberries on boot.

I have also verified that my image for my Pi2 works (MACHINE = "raspberrypi2").

Here is my setup.

MACHINE ??= "raspberrypi3"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES = "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS = "\
    STOPTASKS,${TMPDIR},1G,100K \
    STOPTASKS,${DL_DIR},1G,100K \
    STOPTASKS,${SSTATE_DIR},1G,100K \
    STOPTASKS,/tmp,100M,100K \
    ABORT,${TMPDIR},100M,1K \
    ABORT,${DL_DIR},100M,1K \
    ABORT,${SSTATE_DIR},100M,1K \
    ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
CONF_VERSION = "1"
LICENSE_FLAGS_WHITELIST = "commercial license"

BB_VERSION        = "1.28.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "raspberrypi3"
DISTRO            = "poky"
DISTRO_VERSION    = "2.0.1"
TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard vfpv4 cortexa7"
TARGET_FPU        = "vfp-vfpv4-neon"
meta              
meta-yocto        
meta-yocto-bsp    = "HEAD:3b223f75eec1738fbc913858e8e11c8305e3edcb"
meta-raspberrypi  = "master:dedd75f08ffe3360722ab761da18987aa681edd1"
meta              = "jethro:4d879cb8d7384ac4a96f22c1664b8875f2d8f615"
meta-oe           
meta-python       
meta-networking   = "jethro:c305ac5d2f5285d5eec8952a4ca7f3b4f89aed96"
meta-camera-source = "master:62521e29499baf0be515e0b73ead80e34645fe33"

I have got the latest branch and its build is OK. But if webkitgtk is enabled, the build is failed because
some interfaces are not defined in gl2ext.h. For example, PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC, likely its version is too old. Can I upgrade opengl es by myself?

Hi

Is there any conf for Pi Zero? Or could I reuse Pi/Pi2 for Zero?

Thanks,
Dave

Hi:
How to solve this compile problem?
Log as follows：

fuyongjie@Lenovo:~/work/raspberrypi/yocto$ source poky/oe-init-build-env rpi-build

Shell environment set up for builds.

You can now run 'bitbake '

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
fuyongjie@Lenovo:~/work/raspberrypi/yocto/rpi-build$ bitbake rpi-test-image
Loading cache: 100% |################################################| Time: 0:00:01
Loaded 2687 entries from dependency cache.
Parsing recipes: 100% |##############################################| Time: 0:00:05
Parsing of 1944 .bb files complete (1943 cached, 1 parsed). 2688 targets, 176 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.33.3"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi"
DISTRO = "poky"
DISTRO_VERSION = "2.2+snapshot-20170423"
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "master:633ad6c9f436f5d2b6ee1a005b697661a054a394"
meta-raspberrypi = "master:4b0bc450e08e6836744c97d21e72600f8320fc05"
meta-oe
meta-multimedia
meta-networking
meta-python = "master:444e1fb198076f34a0fa66e83f3eec76efba2e6c"

Initialising tasks: 100% |###########################################| Time: 0:00:07
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: x264-r2731+gitAUTOINC+2b741f81e5-r0 do_compile: oe_runmake failed
ERROR: x264-r2731+gitAUTOINC+2b741f81e5-r0 do_compile: Function failed: do_compile (log file is located at /home/fuyongjie/work/raspberrypi/yocto/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/x264/r2731+gitAUTOINC+2b741f81e5-r0/temp/log.do_compile.2800)
ERROR: Logfile of failure stored in: /home/fuyongjie/work/raspberrypi/yocto/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/x264/r2731+gitAUTOINC+2b741f81e5-r0/temp/log.do_compile.2800
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4
| ERROR: oe_runmake failed
| arm-poky-linux-gnueabi-gcc -march=armv6 -mfpu=vfp -mfloat-abi=hard -mtune=arm1176jzf-s -mfpu=vfp --sysroot=/home/fuyongjie/work/raspberrypi/yocto/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/x264/r2731+gitAUTOINC+2b741f81e5-r0/recipe-sysroot -I. -I. -c -DSTACK_ALIGNMENT=4 -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/quant-a.o common/arm/quant-a.S
| common/arm/quant-a.S: Assembler messages:
| common/arm/quant-a.S:362: Error: selected processor does not support rbit r1,r1' in ARM mode | common/arm/quant-a.S:363: Error: selected processor does not support rbit r1,r1' in ARM mode
| Makefile:217: recipe for target 'common/arm/quant-a.o' failed
| make: *** [common/arm/quant-a.o] Error 1
| ERROR: Function failed: do_compile (log file is located at /home/fuyongjie/work/raspberrypi/yocto/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/x264/r2731+gitAUTOINC+2b741f81e5-r0/temp/log.do_compile.2800)
ERROR: Task (/home/fuyongjie/work/raspberrypi/yocto/poky/meta/recipes-multimedia/x264/x264_git.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2296 tasks of which 2290 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/fuyongjie/work/raspberrypi/yocto/poky/meta/recipes-multimedia/x264/x264_git.bb:do_compile
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Hi,
I'm having an issue with external wifi LAN card after updating firmware.
It works fine before updating firmware but not now.
Giving me dmesg like below,

usb 1-1.3: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[ 4.877941] usb 1-1.3: Direct firmware load for ath9k_htc/htc_9271-1.4.0.fw failed with error -2
[ 4.877966] usb 1-1.3: ath9k_htc: Firmware htc_9271.fw requested
[ 4.878020] usb 1-1.3: Direct firmware load for htc_9271.fw failed with error -2
[ 4.878029] usb 1-1.3: no suitable firmware found!
[ 4.878036] usb 1-1.3: ath9k_htc: Failed to get firmware htc_9271.fw
[ 4.880936] usb 1-1.3: ath9k_htc: USB layer deinitialized

Any solutions or ideas?

Thank you and hope have a great day!

Best,
Paul

Seems that the file 0001-dts-add-overlay-for-pitft22.patch is duplicated multiple times, though the content is the same. Should this patch be merged in the raspberrypi kernel branch?

https://github.com/raspberrypi/linux

Hi

Any ideas for getting bluetooth to work on rpi3? I have tried patching bluez5 according to this issue:
raspberrypi/linux#1314

and putting the image in /lib/firmware/brcm and all but I can't get it to work. I just get get timeouts when running hciattach, sometimes it says flashing firmware but then it times out again.

Anyone who got it working or is working on it that could help?

Thank you,
Daniel

Summary

We found out that most of the initscripts in /etc/rcS.d are not executed. In fact only S00psplash is executed as far as we could find out. We discovered this because S04udev seemed not to be running.
We could not find the cause though, if we work around this by starting the scripts manually it works like a charm (but this doesn't feel right).

Steps to reproduce

We wanted to build our Yocto-based firmware that already existed for another machine now for the raspberrypi2, so we added this layer and baked an image. We were on dizzy back then. Then we found this bug which did not exist on our Freescale iMX.6 based machine we used before.
We baked a few different images for debugging (rpi-hwup-image, rpi-test-image, core-image-x11) and experienced the bug on every one of them.
We updated the whole project to jethro afterwards, hoping that it would fix the bug. It did not.

Expected result

The initscripts should all have been executed after boot.

Actual result

We put some echo-logs in the different S0X-files and it showed that only S00psplash got executed.

Logs / files etc.

Build configuration

Build Configuration:
BB_VERSION        = "1.28.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Debian-8.0"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "raspberrypi2"
DISTRO            = "poky"
DISTRO_VERSION    = "2.0.1"
TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard vfpv4 cortexa7"
TARGET_FPU        = "vfp-vfpv4-neon"
meta              
meta-yocto        = "jethro:5b12268f6e17574999f91628a60e21711cf62ee4"
meta-browser      = "jethro:e114d625d4bd23a52cc1108a45d96ffd8dc0ab7f"
meta-oe           
meta-gnome        
meta-networking   
meta-multimedia   
meta-python       
meta-webserver    = "jethro:dc5634968b270dde250690609f0015f881db81f2"
meta-angstrom     = "angstrom-v2015.12-yocto2.0:6a31b67fbbe9e0ca9f597ab8b248d9fa980b156a"
meta-raspberrypi  = "jethro:f2cff839f52a6e6211337fc45c7c3eabf0fac113"
meta-fsl-arm      = "jethro:35b8b9bd9863de208ab60e33b55f10ee43e2619b"
meta-yocto-bsp    = "jethro:5b12268f6e17574999f91628a60e21711cf62ee4"
meta-qt5          = "jethro:d5536e34ec985c82b621448ab4325e5cbba38560"

I would be happy to provide further information as needed.

Hi Andrei,
I'm using latest yocto (morty) synced with git, your layer and I'm using "raspberrypi" as MACHINE in order to keep compatibility with RPi1,2,3,0. I'm having issues with cmdline.txt because it seems to be rewritten by something else (maybe kernel?) and I want to set my own file. I've tried to create a .bbappend file with the do_deploy_append() function as reported here but I don't know if my file is executed or if its output has been rewritten by something else. Do you have any hints or is there a reliable sample to look at ?

Thanks in advance

I could not reopened follows issue, then I created new issue.
#45

I said "I know already workaround. So I think that you do not have to fix meta-raspberypi by force." in comment.

BUT I would like to hear your opinion on the questions below.

but other platform is not happend such a problem.
for exapmle meta-ti, xf86-input-evdev is included XSERVER varibale in omap4.inc.
Such as follows.

PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
XSERVER = "xserver-xorg \
           xserver-xorg-module-exa \
           xf86-input-evdev \
           xf86-video-omap"
It really oe-core's issue?
Whether xf86-input-evdev should be used or not depends on the board?

You do not necessarily need to fix this problem in meta-raspberrypi.
But I think you should answer this question.

Hi Andrei,
I am creating and building an embedded Linux distribution for the raspberry pi3.
I use the version of Yocto Project 2.2.1 - Morty and the layer meta-raspberrypi.
I am integrating the vc-graphics/vc-graphics-hardfp (meta-raspberrypi recipes) into the image rpi-basic-image.
I am not able to solve the problems of dependencies between the recipe vc-graphics/vc-graphics-hardfp of this recipe rpi-basic-image (see the Error message below):

"1 error: Required build target 'rpi-basic-image' has no buildable providers.Missing or unbuildable dependency chain was: ['rpi-basic-image', 'vc-graphics']"

Could you help me to resolve the vc-graphics/vc-graphics-hardfp dependencies.

See also the copy of the IMAGE_INSTALL_append (Toaster Morty 2.2.1) below:
"apt dpkg dbus sudo tzdata glibc-utils localedef networkmanager pointercal xinit libmatchbox matchbox-terminal matchbox-desktop matchbox-keyboard xkeyboard-config matchbox-session matchbox-wm libx11 consolekit base-passwd liberation-fonts pkgconfig xserver-xorg xf86-input-libinput vc-graphics".

I also need xf86-video-fbturbo in the meta-raspberrypi.

Could you please help me to integrate the recipe for the driver xf86-video-fbturbo from https://github.com/ssvb/xf86-video-fbturbo into the meta-raspberrypi either yourself when it is easy for or tell me how to do it myself or if it is even possible.

Because the same driver applies in the Raspbian during the installation stage of the package xserver-xorg-video-fbturbo and I would like the same driver on my embedded Linux distribution. You would be my hero if you created the new recipe for raspberry pi3 for me.

See the links below : https://github.com/ssvb/xf86-video-fbturbo, https://github.com/ssvb/xf86-video-fbturbo/wiki/Installation.

https://www.reddit.com/r/raspberry_pi/comments/1ubcwu/fbturbo_accelerated_x_driver_in_raspbian/

I thank you in advance for your reply.

Denis

Hello, I am encountering difficulties with the Rpi3 build. Since I was not sure the problem was not my fault, I cloned a fresh copy of poky and meta-raspberrypi (both checked out on morty, and meta dependencies on morty too), but the problem is still appearing, trying to build the DISTRO poky for MACHINE raspberrypi3 :

➜ build git:(morty) bitbake rpi-hwup-image
Loading cache: 100% |#########################################################################################################################################################################################################| Time: 0:00:00
Loaded 2 entries from dependency cache.
WARNING: /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb: Exception during build_dependencies for PKG_kernel-image | ETA: --:--:--
WARNING: /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb: Error during finalise of /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb
WARNING: /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb: Exception during build_dependencies for PKG_kernel-image
WARNING: /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb: Error during finalise of /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb
ERROR: ExpansionError during parsing /home/alexis/Projets/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb
Traceback (most recent call last):
bb.data_smart.ExpansionError: Failure expanding variable PKG_kernel-image, expression was kernel-image-${@legitimize_package_name('${@get_kernelversion_headers('/home/alexis/Projets/poky/build/tmp/work/raspberrypi3-poky-linux-gnueabi/linux-raspberrypi/1_4.9.21+git${SRCPV}-r0/linux-raspberrypi3-standard-build')}')} which triggered exception SyntaxError: invalid syntax (PKG_kernel-image, line 1)
Summary: There were 4 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Unfortunately, since the problem seems to appear right at parsing, I cannot get the exact variable expansion with bitbake -e. Apparently my Yocto setup does not encounter the issue if I try the build for another RPI target, like raspberrypi0. Any advice on how to troubleshoot this issue ?

What is a way to get wifi ready image for RPi3?
There is no wlan0 interface for build-in wifi

Hello! I tried to build for raspberrypi2 and everything seemed to work properly. I then tried to build for raspberrypi3-64 but I got this error:

Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 3 HOSTCC=gcc  HOSTCPP=gcc  -E Image CC=aarch64-poky-linux-gcc   -fuse-ld=bfd  --sysroot=/home/luca/yocto_mount/build_64/tmp/sysroots/raspberrypi3-64 LD=aarch64-poky-linux-ld.bfd    --sysroot=/home/luca/yocto_mount/build_64/tmp/sysroots/raspberrypi3-64 LOADADDR=0x00008000
| NOTE: make -j 3 HOSTCC=gcc  HOSTCPP=gcc  -E bcm2708-rpi-0-w.dtb
| ERROR: oe_runmake failed
|   CHK     include/config/kernel.release
|   GEN     ./Makefile
|   CHK     include/generated/uapi/linux/version.h
|   CHK     include/generated/utsrelease.h
|   Using /home/luca/yocto_mount/build_64/tmp/work-shared/raspberrypi3-64/kernel-source as source for kernel
|   CC      scripts/mod/empty.o
|   CC      scripts/mod/devicetable-offsets.s
|   GEN     scripts/mod/devicetable-offsets.h
|   MKELF   scripts/mod/elfconfig.h
|   HOSTCC  scripts/mod/modpost.o
|   HOSTCC  scripts/mod/file2alias.o
|   HOSTCC  scripts/mod/sumversion.o
|   HOSTLD  scripts/mod/modpost
|   CHK     include/generated/timeconst.h
|   CHK     include/generated/bounds.h
|   CHK     include/generated/asm-offsets.h
|   CALL    /home/luca/yocto_mount/build_64/tmp/work-shared/raspberrypi3-64/kernel-source/scripts/checksyscalls.sh
|   CHK     include/generated/compile.h
|   CC      scripts/mod/devicetable-offsets.s
|   CC      scripts/mod/empty.o
|   GEN     scripts/mod/devicetable-offsets.h
|   MKELF   scripts/mod/elfconfig.h
|   HOSTCC  scripts/mod/modpost.o
|   HOSTCC  scripts/mod/file2alias.o
|   HOSTCC  scripts/mod/sumversion.o
|   HOSTLD  scripts/mod/modpost
| make[3]: *** No rule to make target 'arch/arm64/boot/dts/bcm2708-rpi-0-w.dtb'.  Stop.
| arch/arm64/Makefile:114: recipe for target 'bcm2708-rpi-0-w.dtb' failed
| make[2]: *** [bcm2708-rpi-0-w.dtb] Error 2
| Makefile:150: recipe for target 'sub-make' failed
| make[1]: *** [sub-make] Error 2
| Makefile:24: recipe for target '__sub-make' failed
| make: *** [__sub-make] Error 2
| ERROR: Function failed: do_compile (log file is located at /home/luca/yocto_mount/build_64/tmp/work/raspberrypi3_64-poky-linux/linux-raspberrypi/1_4.9.23+gitAUTOINC+53460a0a50-r17/temp/log.do_compile.76508)

Any idea why this is happening?

I'm struggling with one wire temperature sensor and an Ir receiver using a recent yocto build, here is what I'm seeing on a Jessie build:

[    4.704991] i2c /dev entries driver
[    5.484709] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    5.821942] systemd-udevd[96]: starting version 215
[    6.350574] lirc_dev: IR Remote Control driver registered, major 245
[    6.399151] lirc_rpi: module is from the staging directory, the quality is unknown, you have been warned.
[    6.407353] Driver for 1-wire Dallas network protocol.
[    6.420098] w1-gpio onewire@0: gpio pin 4, external pullup pin -1, parasitic power 0
[    6.420157] w1_add_master_device: set_pullup requires write_byte or touch_bit, disabling
[    6.521092] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000
[    7.373714] bcm2835-rng 20104000.rng: hwrng registered
[    7.840786] lirc_rpi: auto-detected active low receiver on GPIO pin 24
[    7.841199] lirc_rpi lirc_rpi: lirc_dev: driver lirc_rpi registered at minor = 0
[    7.841222] lirc_rpi: driver registered!

not working yocto:

[    6.412996] i2c /dev entries driver
[    6.479388] Driver for 1-wire Dallas network protocol.
[    6.564720] lirc_dev: IR Remote Control driver registered, major 244
[    6.617053] lirc_rpi: module is from the staging directory, the quality is unknown, you have been warned.
[    6.624019] lirc_rpi: gpio chip not found!

I have device tree entries in /boot/config.txt

dtoverlay=w1-gpio
dtparam=i2c_arm=on
dtoverlay=i2c-rtc,ds1307
dtoverlay=lirc-rpi,gpio_out_pin=17,gpio_in_pin=24

I can load the modules by using modprobe, or adding to /etc/modules, however the modules don't seem to populate /sys/bus/w1 with the actual devices, and the lirc-rpi fails to load with gpio chip not found.

Any clues? Thanks

bitbake wiringpi
displays following error.

| NOTE: make -j 1 INCLUDE_DIR=/donnees/programmation/yocto/poky/build_rpi/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/wiringpi/git-r0/image/usr/include LIB_DIR=/donnees/programmation/yocto/poky/build_rpi/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/wiringpi/git-r0/image/usr/lib DESTDIR=/donnees/programmation/yocto/poky/build_rpi/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/wiringpi/git-r0/image/usr PREFIX="" -C gpio LDFLAGS=-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -L/donnees/programmation/yocto/poky/build_rpi/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/wiringpi/git-r0/git/wiringPi -L/donnees/programmation/yocto/poky/build_rpi/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/wiringpi/git-r0/git/devLib
| make: Entering directory '/donnees/programmation/yocto/poky/build_rpi/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/wiringpi/git-r0/git/gpio'
| [Compile] gpio.c
| gpio.c:40:23: fatal error: gertboard.h: No such file or directory

with verbose Makefile, such build command can be seen
| arm-poky-linux-gnueabi-gcc -march=armv7ve -marm -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=/donnees/programmation/yocto/poky/build_rpi/tmp/sysroots/raspberrypi2 -c -I/donnees/programmation/yocto/poky/build_rpi/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/wiringpi/git-r0/git/wiringPi -I/donnees/programmation/yocto/poky/build_rpi/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/wiringpi/git-r0/git/devLib-O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/donnees/programmation/yocto/poky/build_rpi/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/wiringpi/git-r0=/usr/src/debug/wiringpi/git-r0 -fdebug-prefix-map=/donnees/programmation/yocto/poky/build_rpi/tmp/sysroots/i686-linux= -fdebug-prefix-map=/donnees/programmation/yocto/poky/build_rpi/tmp/sysroots/raspberrypi2= gpio.c -o gpio.o
| gpio.c:40:23: fatal error: gertboard.h: No such file or directory
We can see one -I is not correct.

Issue seems to be in the wiringpi_git.bb file. With following patch, no more issue

diff --git a/recipes-devtools/wiringPi/wiringpi_git.bb b/recipes-devtools/wiringPi/wiringpi_git.bb
index 9d2206b..a55b007 100644
--- a/recipes-devtools/wiringPi/wiringpi_git.bb
+++ b/recipes-devtools/wiringPi/wiringpi_git.bb
@@ -16,7 +16,7 @@ SRC_URI = "git://git.drogon.net/wiringPi \

 COMPATIBLE_MACHINE = "raspberrypi"

-CFLAGS_prepend = "-I${S}/wiringPi -I${S}/devLib"
+CFLAGS_prepend = "-I${S}/wiringPi -I${S}/devLib "

 EXTRA_OEMAKE += "'INCLUDE_DIR=${D}${includedir}' 'LIB_DIR=${D}${libdir}'"
 EXTRA_OEMAKE += "'DESTDIR=${D}/usr' 'PREFIX=""'"

I have built an image using this layer, the ram size should be 1G on raspi, but the freecommand output is 128M.

Hi Andrei,
I'm able to compile a basic image (rpi-hwup-image.bb) for RaspberryPi (1/2/3) boards just by changing the MACHINE var, but when I set it for example to "raspberrypi" my image boots just only on v1 boards (B and B+), the same happens for "raspberrypi3" boards (3 only) and so on. Boot partition for each image is basically the same and has its kernel.img (or kernel7.img) only.
Is there a way to create an universal image (P1, P2, P3 support) that goes on each board just like what raspbian does ? I mean, I can compile with MACHINE set to "raspberrypi" and generate various kernels (1,2,3,0) to match the destination board, It's not heavily optimized but at least it runs on each single machine
On a cleaned up installation I have left busybox and kernel configs untouched because I'm doing just bare tests on them, each single image works but I wish to combine them. I might be able to compile each single kernel and with a dirty batch hack I can merge them, but, is there a Yocto way to do it ?

Thanks in advance for your reply
Ben

Hello.

I tried to use core-image-sato with vc4graphics.
Sato is booted however mouse pointer does not moved in spite of mouse is moved.

I added the following line to my local.conf.
It seems to work fine.

IMAGE_INSTALL_append = " xf86-input-evdev"

I think xf86-input-evdev should be included IMAGE_INSTALL or dependencies to core-image-sato or else...

Would you let me know your opinion.
Thanks.

The bitbake build process configures the kernel using .cfg files. However, the meta-raspberrypi linux-rpi.inc creates a config file and calls make oldconfig. Is there a reason why the configuration is done this way? What would be the prefered way to extends the kernel configuration with additional parameters?

Thanks!

WiFi driver init fail

I'm using the pyro version of this Yocto layer and when I boot up the image I receive the following error:
[ 3.392744] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.bin failed with error -2

This is my bblayers variable:
BBLAYERS ?= "
/opt/yocto/poky/meta
/opt/yocto/poky/meta-poky
/opt/yocto/poky/meta-yocto-bsp
/opt/yocto/poky/meta-openembedded/meta-oe
/opt/yocto/poky/meta-openembedded/meta-multimedia
/opt/yocto/poky/meta-openembedded/meta-networking
/opt/yocto/poky/meta-openembedded/meta-python
/opt/yocto/poky/meta-raspberrypi
"

This is my local.conf
MACHINE ?= "raspberrypi3"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_ipk"
SDKMACHINE ?= "x86_64"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS = "
STOPTASKS,${TMPDIR},1G,100K
STOPTASKS,${DL_DIR},1G,100K
STOPTASKS,${SSTATE_DIR},1G,100K
STOPTASKS,/tmp,100M,100K
ABORT,${TMPDIR},100M,1K
ABORT,${DL_DIR},100M,1K
ABORT,${SSTATE_DIR},100M,1K
ABORT,/tmp,10M,1K"
CONF_VERSION = "1"
PREFERRED_PROVIDER_udev = "eudev"
VIRTUAL-RUNTIME_init_manager = "sysvinit"
DISTRO_FEATURES_remove = "x11 wayland"
MACHINE_FEATURES_remove = "apm"
ENABLE_UART = "1"
ENABLE_RPI3_SERIAL_CONSOLE = "1"
RM_OLD_IMAGE = "1"
INHERIT += "rm_work"
LICENSE_FLAGS_WHITELIST = "commercial"
INHERIT += "extrausers"
EXTRA_USERS_PARAMS = "usermod -P changeme root; "
WIFI_SUPPORT = "
crda
iw
linux-firmware-bcm43430
wireless-tools
wpa-supplicant
"
IMAGE_INSTALL += "${WIFI_SUPPORT}"

I've used the command:
bitbake rpi-basic-image

Thanks for your support

I tried to bitbaking core-image-sato.
However bitbake showed error message as follows.

bitbake core-image-sato
WARNING: Host distribution "Ubuntu-16.10" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% |############################################| Time: 0:00:00
Loaded 1338 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'linux-firmware-brcm43430' (but /home/mickey/work/yocto/rpi-morty/poky/meta/recipes-core/packagegroups/packagegroup-base.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'linux-firmware-brcm43430' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['linux-firmware-brcm43430']
NOTE: Runtime target 'packagegroup-base-extended' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-base-extended', 'linux-firmware-brcm43430']
ERROR: Required build target 'core-image-sato' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-sato', 'packagegroup-base-extended', 'linux-firmware-brcm43430']

Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

I suspected commit 380740d.
I tried bitbake after reverting this commit.
Then bitbake is succeeded.

Have you seen problems like this?

Still nailing this down by bisecting poky repo (annoyingly lengthy task...), but looks like some recent commit on oe-core broke the capability of booting with u-boot in the chain... Anyone seeing this as well?

The boot hangs at 'Starting kernel ...' and at first glance the most evident difference w.r.t. a working sdcard image is that there is no mention of the dtb blob being used to boot.

A core-image-minimal built with both poky and meta-raspberrypi from their respective current master branches does show the issue.

To me the u-boot upgrade to 2017.07 (commit d2990a2da61b6a6078728cfa3715b3f4144398f7 in poky, b322e1b1cb4cd4d4cc53f868b53ca9b069772755 in oe-core) is a candidate to blame... I'll report back as soon as I finish bisecting this thing...

Creating this so we don't forget...

Should we split the Readme into files in a doc directory in the git repository itself or should we use the wiki on GitHub? My preference is a doc directory as we're then not tied to GitHub too closely.

Currently meta-raspberrypi/conf/machine/raspberrypi3-64.conf sets:
MACHINEOVERRIDES = "raspberrypi3:raspberrypi:${MACHINE}"
Is there a need for it to include "raspberrypi"? The non-64bit version doesn't seem to do that.

I checked out morty branch both poky and meta-raspberrypi.
Then I added [KERNEL_IMAGETYPE = "uImage"] to my local.conf and ran bitbake.
but I got an error such as follows.

| board/raspberrypi/rpi_2/built-in.o: In function `board_get_usable_ram_top':
| /home/mickey/work/yocto/rpi-morty/build_u-boot/tmp/work/raspberrypi3-poky-linux-gnueabi/u-boot/v2016.03+gitAUTOINC+df61a74e68-r0/git/board/raspberrypi/rpi_2/../rpi/rpi.c:272: undefined reference to `fw_dtb_pointer'
| board/raspberrypi/rpi_2/built-in.o: In function `set_serial_number':
| /home/mickey/work/yocto/rpi-morty/build_u-boot/tmp/work/raspberrypi3-poky-linux-gnueabi/u-boot/v2016.03+gitAUTOINC+df61a74e68-r0/git/board/raspberrypi/rpi_2/../rpi/rpi.c:340: undefined reference to `fw_dtb_pointer'
| /home/mickey/work/yocto/rpi-morty/build_u-boot/tmp/work/raspberrypi3-poky-linux-gnueabi/u-boot/v2016.03+gitAUTOINC+df61a74e68-r0/git/Makefile:1171: recipe for target 'u-boot' failed
| make[1]: *** [u-boot] Error 1
| make[1]: Leaving directory '/home/mickey/work/yocto/rpi-morty/build_u-boot/tmp/work/raspberrypi3-poky-linux-gnueabi/u-boot/v2016.03+gitAUTOINC+df61a74e68-r0/build'

It seems to missing symbol that fw_dtb_pointer.
I think fw_dtb_pointer is declared in lowlevel_init.S.
However lowlevel_init.S is not included in Makefiles.

I checked git log then I think suspicious a commit that 031e269.
This commit to avoid a failing build to u-boot_2016.11.
However morty's u-boot is 2016.03.

I reverted this commit and bitbake,then build is succeeded.
Have you seen problems like this?

ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    Error, the PACKAGE_ARCHS variable (all any noarch armv5hf-vfp armv5thf-vfp armv5ehf-vfp armv5tehf-vfp armv6hf-vfp armv6thf-vfp armv7ahf-vfp armv7at2hf-vfp armv7vehf-vfp armv7vet2hf-vfp armv7vehf-neon armv7vet2hf-neon armv7vehf-neon-vfpv4 armv7vet2hf-neon-vfpv4 cortexa7hf-vfp cortexa7hf-neon cortexa7hf-neon-vfpv4 cortexa7t2hf-vfp cortexa7t2hf-neon cortexa7t2hf-neon-vfpv4 raspberrypi2) for DEFAULTTUNE (cortexa7thf-neon-vfpv4) does not contain TUNE_PKGARCH (cortexa7hf-neonvfpv4).

the culprit is change: 31351ce146bf9c61d779456cd68ff7c2c9d4c8a8

Description

The rpio tool requires Python's logging and Threading library code. These libraries are not present on a minimal install and must be required by the tool's recipe to ensure they are included in the build.

Steps to reproduce the issue:

1. Checkout a work area for Raspberry Pi work
2. Add rpio to the list of things to IMAGE_INSTALL_append
3. Perform a rpi-basic-image generation
4. Attempt to run rpio and it will fail. Use a call to python /use/bing/rpio to see the failure line indicating a missing library.

Describe the results you received:

Script fails to execute as it cannot fine the missing libraries on the system.

Describe the results you expected:

Adding rpio to the list of things to add to an image should give you a working copy of rpio by ensuring all of it's dependencies are met.

Additional information you deem important (e.g. issue happens only occasionally):

Additional details (revisions used, host distro, etc.):
I am testing on Krogoth with a Raspberry Pi 3. I think this is still present in the latest branch. I think this will fail on any Raspberry Pi platform. (There is a seperate problem with Pi 3 not being supported by rpio yet that I am working on with the maintainer of the script.)

Hi guys.

Anyone else experiencing problems booting on current HEAD?

I am currently testing on a raspberrypi2 and it builds just fine but does not boot. Tested both Linux and u-boot. I tried using the "bootfiles" from krogoth branch (just copied them to boot section on SD) and that worked! Though I did not use the device tree from krogoth but from HEAD, the krogoth one did not work for me. So there seem to some conflicts here, or is it just me?

I have also tested building krogoth branch and that works just fine.

I noticed that you in a recent commit changed to use tarballs for firmware [1] and that you changed the firmware date there, was this intentional? I shall admit that I do not quite understand the dependencies of the firmware files, would love if you could explain that a bit or point me to some documentation.

[1]. http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/commit/?id=716b6a9cd7f24a8bacd539bb40519d185e3f963a

logs:

ERROR: /media/mika/new/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb: Error executing a python function in <code>:

The stack trace of python calls that resulted in this exception/failure was:
File: '<code>', lineno: 19, function: <module>
     0015:__anon_18__media_mika_new_poky_meta_recipes_kernel_linux_linux_yocto_inc(d)
     0016:__anon_364__media_mika_new_poky_meta_classes_kernel_yocto_bbclass(d)
     0017:__anon_6__media_mika_new_poky_meta_recipes_kernel_linux_linux_dtb_inc(d)
     0018:__anon_148__media_mika_new_poky_meta_raspberrypi_recipes_kernel_linux_linux_rpi_inc(d)
 *** 0019:__anon_38__media_mika_new_poky_meta_raspberrypi_recipes_kernel_linux_linux_raspberrypi_inc(d)
File: '/media/mika/new/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi.inc', lineno: 36, function: __anon_38__media_mika_new_po$
     0032:# Set programmatically some variables during recipe parsing
     0033:# See http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#anonymous-python-functions
     0034:python __anonymous () {
     0035:    kerneltype = d.getVar('KERNEL_IMAGETYPE')
 *** 0036:    kerneldt = get_dts(d, d.getVar('LINUX_VERSION'))
     0037:    d.setVar("KERNEL_DEVICETREE", kerneldt)
     0038:}
     0039:
     0040:do_kernel_configme_prepend() {
Exception: TypeError: getVar() missing 1 required positional argument: 'expand'

ERROR: /media/mika/new/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.4.bb: Error executing a python function in <code>:

The stack trace of python calls that resulted in this exception/failure was:
File: '<code>', lineno: 19, function: <module>
     0015:__anon_18__media_mika_new_poky_meta_recipes_kernel_linux_linux_yocto_inc(d)
     0016:__anon_364__media_mika_new_poky_meta_classes_kernel_yocto_bbclass(d)
     0017:__anon_6__media_mika_new_poky_meta_recipes_kernel_linux_linux_dtb_inc(d)
     0018:__anon_148__media_mika_new_poky_meta_raspberrypi_recipes_kernel_linux_linux_rpi_inc(d)
 *** 0019:__anon_38__media_mika_new_poky_meta_raspberrypi_recipes_kernel_linux_linux_raspberrypi_inc(d)
File: '/media/mika/new/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi.inc', lineno: 36, function: __anon_38__media_mika_new_po$
     0032:# Set programmatically some variables during recipe parsing
     0033:# See http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#anonymous-python-functions
     0034:python __anonymous () {
     0035:    kerneltype = d.getVar('KERNEL_IMAGETYPE')
 *** 0036:    kerneldt = get_dts(d, d.getVar('LINUX_VERSION'))
     0037:    d.setVar("KERNEL_DEVICETREE", kerneldt)
     0038:}
     0039:
     0040:do_kernel_configme_prepend() {
Exception: TypeError: getVar() missing 1 required positional argument: 'expand'

ERROR: Failed to parse recipe: /media/mika/new/poky/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb

host OS:
Debian 8 (Jessie)

meta-raspberrypi
commit ec28a0d (Update to 4.9.4)

poky
commit a3fa5ce87619e81d7acfa43340dd18d8f2b2d7dc (version 2.2.1)

Let me know if there is anything else you need.

Thanks,

I read about a hardware watchdog kernel module here.
I would like to have a hardware watchdog in my firmware on the Pi 2 B, too.
Is this supported at all? If yes, how can I enable it?

Description

Incorrect order of compiler flags causing the libwiringpi.so library to not have the required linking dependencies.

Steps to reproduce the issue:
Build an executable that links to libwiringpi.so. The compilation of this executable will break with the following error:
recipe-sysroot/usr/lib/libwiringPi.so: undefined reference to `crypt'
| collect2: error: ld returned 1 exit status

Describe the results you received:
readelf -d libwiringPi.so

Dynamic section at offset 0xbf18 contains 25 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [libc.so.6]
0x0000000e (SONAME) Library soname: [libwiringPi.so.]

Describe the results you expected:
readelf -d libwiringPi.so

Dynamic section at offset 0xbef8 contains 29 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [libm.so.6]
0x00000001 (NEEDED) Shared library: [libpthread.so.0]
0x00000001 (NEEDED) Shared library: [librt.so.1]
0x00000001 (NEEDED) Shared library: [libcrypt.so.1]
0x00000001 (NEEDED) Shared library: [libc.so.6]
0x0000000e (SONAME) Library soname: [libwiringPi.so.]

Additional information:
I reproduced the problem on pyro branch, but I'm quite sure that can be reproduced on master too. It's 100% reproducible. I already have the fix and I'll submit it as soon as possible.

Description
I am trying to write a configuration file for the cm3 64 bits, but I keep getting errors regarding KERNEL_DEVICETREE. I am trying to make the machine similar to the raspberrypi3-64 and add the KERNEL_DEVICETREE for the CM, but from what I understand, they are not shipped.
During compilation, it fails, not finding some dtb.It seem KERNEL_DEVICETREE points to some, but those are not generated. If not linked to KERNEL_DEVICETREE paramater, how can I ship the right dtb?
Here is my conf file:

#@TYPE: Machine
#@NAME: RaspberryPi Compute Module 3 (CM3-64)
#@DESCRIPTION: Machine configuration for the RaspberryPi Compute Module 3 (CM3) in 64 bits mode

MACHINEOVERRIDES = "raspberrypi3:${MACHINE}"

require conf/machine/include/arm/arch-armv8.inc
include conf/machine/include/rpi-base.inc

KERNEL_DEVICETREE = " \
    broadcom/bcm2710-rpi-3-b.dtb \
    broadcom/bcm2837-rpi-3-b.dtb \
    broadcom/bcm2708-rpi-cm.dtb \
    broadcom/bcm2710-rpi-cm3.dtb \
    \
    overlays/hifiberry-amp.dtbo \
    overlays/hifiberry-dac.dtbo \
    overlays/hifiberry-dacplus.dtbo \
    overlays/hifiberry-digi.dtbo \
    overlays/i2c-rtc.dtbo \
    overlays/iqaudio-dac.dtbo \
    overlays/iqaudio-dacplus.dtbo \
    overlays/lirc-rpi.dtbo \
    overlays/pitft22.dtbo \
    overlays/pitft28-resistive.dtbo \
    overlays/pitft35-resistive.dtbo \
    overlays/pps-gpio.dtbo \
    overlays/rpi-ft5406.dtbo \
    overlays/w1-gpio.dtbo \
    overlays/w1-gpio-pullup.dtbo \
    overlays/pi3-disable-bt.dtbo \
    overlays/pi3-miniuart-bt.dtbo \
    overlays/vc4-kms-v3d.dtbo \
    "

SERIAL_CONSOLE ?= "115200 ttyS0"
VC4_CMA_SIZE ?= "cma-256"

UBOOT_MACHINE = "rpi_3_config"
MACHINE_FEATURES_append = " vc4graphics"

I am conscious this is not an issue itself, but once I understand how it works, I can make a PR here.

Steps to reproduce the issue:

1. Add the upper configuration file in meta-raspberrypi/conf/machine
2. Add KERNEL_DEFCONFIG_raspberrypi-cm3-64 ?= "bcmrpi3_defconfig" in recipes-kernel/linux/linux-raspberrypi.inc
3. bitbake linux-raspberrypi

Describe the results you received:

|   DTC     arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dtb
| make[3]: *** No rule to make target `arch/arm64/boot/dts/broadcom/bcm2708-rpi-cm.dtb'.  Stop.
| make[2]: *** [broadcom/bcm2708-rpi-cm.dtb] Error 2
| make[1]: *** [sub-make] Error 2
| make: *** [__sub-make] Error 2

Describe the results you expected:
Compilation done with dtb from CM.

Additional information you deem important (e.g. issue happens only occasionally):

Additional details (revisions used, host distro, etc.):

| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_rpi_sdimg
| Creating filesystem with Boot partition 40960 KiB and RootFS 90112 KiB
| dd: failed to open '/rpi-basic-image-raspberrypi3-20160927134756.rootfs.rpi-sdimg': Permission denied
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_rpi_sdimg (log file is located at /home/mickey/work/yocto/rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-basic-image/1.0-r0/temp/log.do_image_rpi_sdimg.7703)
ERROR: Task 16 (/home/mickey/work/yocto/rpi/build/../poky/meta-raspberrypi/recipes-core/images/rpi-basic-image.bb, do_image_rpi_sdimg) failed with exit code '1'

do_image_rpi_sdimg is failed after 4817e2c commit.
I reverted 4817e2c for test, then do_image_rpi_sdimg is succeeded.

This commit is correspond on oe-core in master branch. but it is unnecessary for the krogoth branch.

By the way, why meta-raspberrypi does not have krogoth branch?