Need help with Raspberry Pi 3 Bootup

[Jorge Corona]

I am trying to setup Yocto with mender to run on Raspberry PI 3. I am building the image on Ubuntu 16.04 VM and it looks to have compiled for Pyro Yocto. It's pretty huge, at 625 MB. I flashed the image and I see all 4 partitions but the raspberry PI doesn't boot up to a prompt. 

Here are my configurations:

https://stackoverflow.com/questions/47641947/creating-yocto-mender-for-raspberrypi-3

I tried both rpi-basic-image and rpi-hwup-image and neither seem to work. Anyone help would be appreciated.

Thanks,

-- Jorge

[Gregorio Di Stefano]

Hi Jorge,

It's hard to troubleshoot without having any logs of the booting up process. Can you please share those with us?

Thanks,

Greg

[Naveen Narayanasamy]

Hello Jorge,

 

I think using this configuration setup will help you.

local.conf

MENDER_ARTIFACT_NAME = "release-1"

INHERIT += "mender-full"

DISTRO_FEATURES_append = " systemd"

VIRTUAL-RUNTIME_init_manager = "systemd"

DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"

VIRTUAL-RUNTIME_initscripts = ""

IMAGE_FSTYPES = "ext4"

MACHINE = "raspberrypi3"

KERNEL_IMAGETYPE = "uImage"

MENDER_PARTITION_ALIGNMENT_KB = "4096"

MENDER_BOOT_PART_SIZE_MB = "40"

# raspberrypi files aligned with mender layout requirements

IMAGE_BOOT_FILES_append = " boot.scr u-boot.bin;${SDIMG_KERNELIMAGE}"

IMAGE_INSTALL_append = " kernel-image kernel-devicetree openssh packagegroup-core-ssh-openssh openssh-sftp-server"

IMAGE_FSTYPES_remove += " rpi-sdimg"

#MENDER_SERVER_URL = "https://mender.mydomain.com"

MENDER_STORAGE_TOTAL_SIZE_MB = "3000"

MENDER_DATA_PART_SIZE_MB = "1000"

IMAGE_ROOTFS_MAXSIZE ?= "20000000"

CORE_IMAGE_EXTRA_INSTALL = " strace sudo sqlite3 gettext"

#FILESEXTRAPATHS_prepend_pn-mender := "/var/sslcert:"

#SRC_URI_append_pn-mender = " file://server.crt"

#

# This file is your local configuration file and is where all local user settings

# are placed. The comments in this file give some guide to the options a new user

# to the system might want to change but pretty much any configuration option can

# be set in this file. More adventurous users can look at local.conf.extended

# which contains other examples of configuration which can be placed in this file

# but new users likely won't need any of them initially.

#

# Lines starting with the '#' character are commented out and in some cases the

# default values are provided as comments to show people example syntax. Enabling

# the option is a question of removing the # character and making any change to the

# variable as required.

#

# Machine Selection

#

# You need to select a specific machine to target the build with. There are a selection

# of emulated machines available which can boot and run in the QEMU emulator:

#

#MACHINE ?= "qemuarm"

#MACHINE ?= "qemuarm64"

#MACHINE ?= "qemumips"

#MACHINE ?= "qemumips64"

#MACHINE ?= "qemuppc"

#MACHINE ?= "qemux86"

#MACHINE ?= "qemux86-64"

#

# There are also the following hardware board target machines included for 

# demonstration purposes:

#

#MACHINE ?= "beaglebone"

#MACHINE ?= "genericx86"

#MACHINE ?= "genericx86-64"

#MACHINE ?= "mpc8315e-rdb"

#MACHINE ?= "edgerouter"

#

# This sets the default machine to be qemux86 if no other machine is selected:

#MACHINE ??= "qemux86"

#

# Where to place downloads

#

# During a first build the system will download many different source code tarballs

# from various upstream projects. This can take a while, particularly if your network

# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you

# can preserve this directory to speed up this part of subsequent builds. This directory

# is safe to share between multiple builds on the same machine too.

#

# The default is a downloads directory under TOPDIR which is the build directory.

#

#DL_DIR ?= "${TOPDIR}/downloads"

#

# Where to place shared-state files

#

# BitBake has the capability to accelerate builds based on previously built output.

# This is done using "shared state" files which can be thought of as cache objects

# and this option determines where those files are placed.

#

# You can wipe out TMPDIR leaving this directory intact and the build would regenerate

# from these files if no changes were made to the configuration. If changes were made

# to the configuration, only shared state files where the state was still valid would

# be used (done using checksums).

#

# The default is a sstate-cache directory under TOPDIR.

#

#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"

#

# Where to place the build output

#

# This option specifies where the bulk of the building work should be done and

# where BitBake should place its temporary files and output. Keep in mind that

# this includes the extraction and compilation of many applications and the toolchain

# which can use Gigabytes of hard disk space.

#

# The default is a tmp directory under TOPDIR.

#

#TMPDIR = "${TOPDIR}/tmp"

#

# Default policy config

#

# The distribution setting controls which policy settings are used as defaults.

# The default value is fine for general Yocto project use, at least initially.

# Ultimately when creating custom policy, people will likely end up subclassing 

# these defaults.

#

DISTRO ?= "poky"

# As an example of a subclass there is a "bleeding" edge policy configuration

# where many versions are set to the absolute latest code from the upstream 

# source control systems. This is just mentioned here as an example, its not

# useful to most new users.

# DISTRO ?= "poky-bleeding"

#

# Package Management configuration

#

# This variable lists which packaging formats to enable. Multiple package backends

# can be enabled at once and the first item listed in the variable will be used

# to generate the root filesystems.

# Options are:

#  - 'package_deb' for debian style deb files

#  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)

#  - 'package_rpm' for rpm style packages

# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"

# We default to rpm:

PACKAGE_CLASSES ?= "package_rpm"

#

# SDK target architecture

#

# This variable specifies the architecture to build SDK items for and means

# you can build the SDK packages for architectures other than the machine you are

# running the build on (i.e. building i686 packages on an x86_64 host).

# Supported values are i686 and x86_64

#SDKMACHINE ?= "i686"

#

# Extra image configuration defaults

#

# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated

# images. Some of these options are added to certain image types automatically. The

# variable can contain the following options:

#  "dbg-pkgs"       - add -dbg packages for all installed packages

#                     (adds symbol information for debugging/profiling)

#  "dev-pkgs"       - add -dev packages for all installed packages

#                     (useful if you want to develop against libs in the image)

#  "ptest-pkgs"     - add -ptest packages for all ptest-enabled packages

#                     (useful if you want to run the package test suites)

#  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)

#  "tools-debug"    - add debugging tools (gdb, strace)

#  "eclipse-debug"  - add Eclipse remote debugging support

#  "tools-profile"  - add profiling tools (oprofile, lttng, valgrind)

#  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)

#  "debug-tweaks"   - make an image suitable for development

#                     e.g. ssh root access has a blank password

# There are other application targets that can be used here too, see

# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.

# We default to enabling the debugging tweaks.

EXTRA_IMAGE_FEATURES ?= "debug-tweaks"

#

# Additional image features

#

# The following is a list of additional classes to use when building images which

# enable extra features. Some available options which can be included in this variable

# are:

#   - 'buildstats' collect build statistics

#   - 'image-mklibs' to reduce shared library files size for an image

#   - 'image-prelink' in order to prelink the filesystem image

#   - 'image-swab' to perform host system intrusion detection

# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink

# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended

USER_CLASSES ?= "buildstats image-mklibs image-prelink"

#

# Runtime testing of images

#

# The build system can test booting virtual machine images under qemu (an emulator)

# after any root filesystems are created and run tests against those images. To

# enable this uncomment this line. See classes/testimage(-auto).bbclass for

# further details.

#TEST_IMAGE = "1"

#

# Interactive shell configuration

#

# Under certain circumstances the system may need input from you and to do this it

# can launch an interactive shell. It needs to do this since the build is

# multithreaded and needs to be able to handle the case where more than one parallel

# process may require the user's attention. The default is iterate over the available

# terminal types to find one that works.

#

# Examples of the occasions this may happen are when resolving patches which cannot

# be applied, to use the devshell or the kernel menuconfig

#

# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none

# Note: currently, Konsole support only works for KDE 3.x due to the way

# newer Konsole versions behave

#OE_TERMINAL = "auto"

# By default disable interactive patch resolution (tasks will just fail instead):

PATCHRESOLVE = "noop"

#

# Disk Space Monitoring during the build

#

# Monitor the disk space during the build. If there is less that 1GB of space or less

# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully

# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort

# of the build. The reason for this is that running completely out of space can corrupt

# files and damages the build in ways which may not be easily recoverable.

# It's necesary to monitor /tmp, if there is no space left the build will fail

# with very exotic errors.

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"

#

# Shared-state files from other locations

#

# As mentioned above, shared state files are prebuilt cache data objects which can

# used to accelerate build time. This variable can be used to configure the system

# to search other mirror locations for these objects before it builds the data itself.

#

# This can be a filesystem directory, or a remote url such as http or ftp. These

# would contain the sstate-cache results from previous builds (possibly from other

# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the

# cache locations to check for the shared objects.

# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH

# at the end as shown in the examples below. This will be substituted with the

# correct path within the directory structure.

#SSTATE_MIRRORS ?= "\

#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \

#file://.* file:///some/local/dir/sstate/PATH"

#

# Qemu configuration

#

# By default qemu will build with a builtin VNC server where graphical output can be

# seen. The two lines below enable the SDL backend too. By default libsdl-native will

# be built, if you want to use your host's libSDL instead of the minimal libsdl built

# by libsdl-native then uncomment the ASSUME_PROVIDED line below.

PACKAGECONFIG_append_pn-qemu-native = " sdl"

PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"

#ASSUME_PROVIDED += "libsdl-native"

# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to

# track the version of this file when it was generated. This can safely be ignored if

# this doesn't mean anything to you.

CONF_VERSION = "1"

bblayers.conf

# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf

# changes incompatibly

# rapsbian /root/poky/mkraspbian-chroot 

POKY_BBLAYERS_CONF_VERSION = "2"

BBPATH = "${TOPDIR}"

BBFILES ?= ""

BBLAYERS ?= " \

  /root/poky/meta \

  /root/poky/meta-poky \

  /root/poky/meta-yocto-bsp \

  /root/poky/meta-mender/meta-mender-core \

  /root/poky/meta-mender/meta-mender-demo \

  /root/poky/meta-raspberrypi \

  /root/poky/meta-mender/meta-mender-raspberrypi \

  /root/poky/meta-openembedded/meta-oe \

  /root/poky/meta-openembedded/meta-multimedia \

  /root/poky/meta-openembedded/meta-python \

  /root/poky/meta-openembedded/meta-networking \

  /root/poky/meta-openembedded/meta-gnome \

  /root/poky/meta-openembedded/meta-xfce \

  /root/poky/openembedded-core \

"

Best

Naveen

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mender+unsubscribe@lists.mender.io.
To post to this group, send email to men...@lists.mender.io.
Visit this group at https://groups.google.com/a/lists.mender.io/group/mender/.

[Drew Moseley]

Hi Jorge,

I don't believe RPI_USE_U_BOOT is fully supported in the pyro branch.  I think for that branch you need to use the old style:

    KERNEL_IMAGETYPE = "uImage"

Drew

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mender+un...@lists.mender.io.

[Jorge Corona]

Didn't work. I got errors:

ERROR: rpi-basic-image-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/ubuntu/pyro/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-basic-image/1.0-r0/recipe-sysroot-native/usr/bin/dnf -y -c /home/ubuntu/pyro/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-basic-image/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/ubuntu/pyro/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-basic-image/1.0-r0/rootfs/etc/yum.repos.d --repofrompath=oe-repo,/home/ubuntu/pyro/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-basic-image/1.0-r0/oe-rootfs-repo --installroot=/home/ubuntu/pyro/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-basic-image/1.0-r0/rootfs --setopt=logdir=/home/ubuntu/pyro/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-basic-image/1.0-r0/temp --nogpgcheck install kernel-modules kernel-image-4.9.50 packagegroup-core-boot psplash-raspberrypi kernel-devicetree openssh-sftp-server mender sqlite3 strace sudo gettext packagegroup-core-ssh-openssh packagegroup-core-ssh-dropbear openssh run-postinsts' returned 1:

Added oe-repo repo from file:///home/ubuntu/pyro/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-basic-image/1.0-r0/oe-rootfs-repo

Last metadata expiration check: 0:00:00 ago on Tue Dec 05 17:56:48 2017 UTC.

Error: package openssh-7.4p1-r0.cortexa7hf_neon_vfpv4 conflicts with dropbear provided by dropbear-2016.74-r0.cortexa7hf_neon_vfpv4

  - package packagegroup-core-ssh-dropbear-1.0-r1.noarch requires dropbear, but none of the providers can be installed

  - conflicting requests

  - conflicting requests

(try to add '--allowerasing' to command line to replace conflicting packages)

ERROR: rpi-basic-image-1.0-r0 do_rootfs: Function failed: do_rootfs

ERROR: Logfile of failure stored in: /home/ubuntu/pyro/build/tmp/work/raspberrypi3-poky-linux-gnueabi/rpi-basic-image/1.0-r0/tem

To unsubscribe from this group and stop receiving emails from it, send an email to mender+un...@lists.mender.io.

[Jorge Corona]

How do I get logs? Are they on the SD Card?

[Naveen Narayanasamy]

Your recipe should look like this(remove dropbear)

# Base this image on rpi-hwup-image

include rpi-hwup-image.bb

SPLASH = "psplash-raspberrypi"

IMAGE_FEATURES += "splash"

It can be found in ../meta-raspberrypi/recipes-core/images/rpi-basic-image.bb

Naveen

To unsubscribe from this group and stop receiving emails from it, send an email to mender+unsubscribe@lists.mender.io.

[Jorge Corona]

Thanks,

I went back and removed RPI_USE_U_BOOT and added the KERNEAL_IMAGTYPE and it boots now.

[Raghav]

Good evening,
I am also trying to build a modifies yocto image with mender for raspberry pi 3.
I seemed to have use the same steps, but I am geting the error :
"" kernel panic: not syncing: VFS : unable to mount on unknown blocks ""

My local.conf is :

""
#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.

MENDER_ARTIFACT_NAME = "release-1"

INHERIT += "mender-full"

#RPI_USE_U_BOOT = "1"

MENDER_PARTITION_ALIGNMENT_KB = "4096"
MENDER_BOOT_PART_SIZE_MB = "40"

IMAGE_INSTALL_append = " kernel-image kernel-devicetree openssh packagegroup-core-ssh-openssh openssh-sftp-server"

#IMAGE_INSTALL_append = " kernel-image kernel-devicetree"
#IMAGE_INSTALL_append = " kernel-modules"
IMAGE_FSTYPES_remove += " rpi-sdimg"

IMAGE_BOOT_FILES_append = " boot.scr u-boot.bin;${SDIMG_KERNELIMAGE}"

KERNEL_IMAGETYPE = "uImage"

DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""

IMAGE_FSTYPES = "ext4"



MACHINE = "raspberrypi3"

BB_DISKMON_DIRS ??= "\

and bb.layer.conf is

""
# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly

POKY_BBLAYERS_CONF_VERSION = "2"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \

  ${HOME}/pokynode/poky/meta \
  ${HOME}/pokynode/poky/meta-poky \
  ${HOME}/pokynode/poky/meta-yocto-bsp \
  ${HOME}/pokynode/poky/meta-mender/meta-mender-core \
  ${HOME}/pokynode/poky/meta-openembedded/meta-oe \
  ${HOME}/pokynode/poky/meta-openembedded/meta-multimedia \
  ${HOME}/pokynode/poky/meta-openembedded/meta-networking \
  ${HOME}/pokynode/poky/meta-openembedded/meta-perl \
  ${HOME}/pokynode/poky/meta-openembedded/meta-python \
  ${HOME}/pokynode/poky/meta-qt5 \
  ${HOME}/pokynode/poky/meta-raspberrypi \
  ${HOME}/pokynode/poky/meta-security \
  ${HOME}/pokynode/poky/meta-nodejs \
  "

""


Could you please help me.

Thanks
Regards

[Raghav]

Also I have used the rocko branch