meta-raspberrypi: Just got a Pi3 Model B in, image doesn't boot.

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"

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 40 (15 by maintainers)

Most upvoted comments

If I copy over the bcm* files and bootcode.bin from NOOBS into the image created by yocto, it works.