Custom Yocto for WP8548 - Stuck in Fastboot


#1

Hello,

I tried to build my own Yocto Linux.

  1. Downloaded the Legato Linux Distribution - https://source.sierrawireless.com/resources/legato/legatolinuxdist/

  2. unziped the Legato Linux Distribution (tar xvjf …)

  3. Started make:

kilian@kilian-VirtualBox:~/yocto$ make
Makefile:18: “Legato: build disabled since ‘/home/kilian/yocto/legato/’ does not exist”
“meta-swi-extras/build.sh” -p poky/ -o meta-openembedded/ -l meta-swi -x “kernel/.git” -j 9 -t 9 -a “SDKPATH_PREFIX=” -M -a “MANGOH_WIFI_REPO=”/home/kilian/yocto/mangOH/WiFi"" -m swi-mdm9x15 -a KBRANCH_DEFAULT_MDM9X15=standard/swi-mdm9x15-yocto-1.7-swi-le55 -a KMETA_DEFAULT_MDM9X15=meta-yocto-1.7-swi-le55 -q -b build_bin
Poky dir: /home/kilian/yocto/poky
OE meta: /home/kilian/yocto/meta-openembedded
SWI meta dir: /home/kilian/yocto/meta-swi
Linux repo dir: /home/kilian/yocto/kernel/.git
Number of make threads 9
Number of bitbake tasks 9
Extra options added - SDKPATH_PREFIX=
With mangOH
Extra options added - MANGOH_WIFI_REPO=/home/kilian/yocto/mangOH/WiFi
SWI machine: swi-mdm9x15
Extra options added - KBRANCH_DEFAULT_MDM9X15=standard/swi-mdm9x15-yocto-1.7-swi-le55
Extra options added - KMETA_DEFAULT_MDM9X15=meta-yocto-1.7-swi-le55
Enable Qualcomm Proprietary bin
Build dir: /home/kilian/yocto/build_bin

Shell environment set up for builds.

You can now run 'bitbake ’

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

You can also run generated qemu images with a command like ‘runqemu qemux86’

  • layer: meta-swi-mdm9xxx
  • layer: meta-swi-mdm9x15
  • layer: meta-swi
  • layer: meta-oe
  • layer: meta-networking
  • layer: meta-python
  • layer: meta-swi-bin
  • layer: meta-swi-extras
  • layer: meta-mangoh
    Updating LEGATO_BUILD to false
    Updating ROOTFS_VERSION to
    Updating SDKPATH_PREFIX to
    Updating MANGOH_WIFI_REPO to /home/kilian/yocto/mangOH/WiFi
    Updating KBRANCH_DEFAULT_MDM9X15 to standard/swi-mdm9x15-yocto-1.7-swi-le55
    Updating KMETA_DEFAULT_MDM9X15 to meta-yocto-1.7-swi-le55
    Build image of minimal rootfs (for swi-mdm9x15).
    Loading cache: 100% |#############################################################| ETA: 00:00:00
    Loaded 2073 entries from dependency cache.
    Parsing recipes: 100% |###########################################################| Time: 00:00:02
    Parsing of 1602 .bb files complete (1600 cached, 2 parsed). 2074 targets, 200 skipped, 0 masked, 0 errors.
    NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.24.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-14.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "swi-mdm9x15"
DISTRO = "poky-swi-ext"
DISTRO_VERSION = "1.7.3"
TUNE_FEATURES = "arm armv7a vfp neon"
TARGET_FPU = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp = "(nobranch):c282df8993828bd7b1d50cfcf637a477eaf481a1"
meta-mangoh = "(nobranch):b58ad3c6a4e4d0f2d563e8af86c46f96f8ba3bb6"
meta-python
meta-networking
meta-oe = "(nobranch):70beecb2716bca1b9dfbc7d6a264233e1f05e82b"
meta-swi
meta-swi-mdm9xxx
meta-swi-mdm9x15 = "master:70317fa501d3af2a5fa04e92a9bf25feb716efa8"
meta-swi-extras
meta-swi-bin = “master:dc7691c2766b5ac7d8be82930de19066355628fe”

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 2470 tasks of which 2466 didn’t need to be rerun and all succeeded

  1. Changed to the directory with the generated images and flashed them through fastboot (changed the device into fastboot by running sys_reboot bootloader):

kilian@kilian-VirtualBox:~/yocto/build_bin/tmp/deploy/images/swi-mdm9x15$ sudo fastboot devices
MDM9615 fastboot
kilian@kilian-VirtualBox:~/yocto/build_bin/tmp/deploy/images/swi-mdm9x15$ sudo fastboot erase kernel
erasing ‘kernel’…
OKAY [ 0.099s]
finished. total time: 0.099s
kilian@kilian-VirtualBox:~/yocto/build_bin/tmp/deploy/images/swi-mdm9x15$ sudo fastboot erase rootfs
erasing ‘rootfs’…
OKAY [ 0.272s]
finished. total time: 0.272s
kilian@kilian-VirtualBox:~/yocto/build_bin/tmp/deploy/images/swi-mdm9x15$ sudo fastboot flash kernel kernel
sending ‘kernel’ (3916 KB)…
OKAY [ 1.052s]
writing ‘kernel’…
OKAY [ 0.722s]
finished. total time: 1.773s
kilian@kilian-VirtualBox:~/yocto/build_bin/tmp/deploy/images/swi-mdm9x15$ sudo fastboot flash rootfs rootfs
sending ‘rootfs’ (26624 KB)…
OKAY [ 7.219s]
writing ‘rootfs’…
OKAY [ 4.539s]
finished. total time: 11.757s
kilian@kilian-VirtualBox:~/yocto/build_bin/tmp/deploy/images/swi-mdm9x15$ sudo fastboot reboot
rebooting…

finished. total time: 0.006s

After that, the board restarts again into fastboot mode.
So, I don’t know, who I could solve the problem that the device would boot normal again and how I could flash my yocto Linux (until now, it is completely unchanged, only compiled it).

Thanks!

BTW: Using Ubuntu 14.04 in a VM to compile and flash on a Ubuntu 16.10 host.
The manual I used is this one: http://legato.io/legato-docs/latest/yoctoLegatoOverview.html#getstartedYoctoLinux_rebuildYoctoImages


Maybe helpful informations:

Created files in ~/yocto/build_bin/tmp/deploy/images/swi-mdm9x15:

appsboot.mbn
appsboot.raw
boot_wp85.cwe
boot-yocto-mdm9x15-20170407121219.2k.img
boot-yocto-mdm9x15-20170407121219.2k.initramfs.img
boot-yocto-mdm9x15-20170407121219.4k.img
boot-yocto-mdm9x15-20170407121219.4k.initramfs.img
boot-yocto-mdm9x15-20170410060412.2k.img
boot-yocto-mdm9x15-20170410060412.2k.initramfs.img
boot-yocto-mdm9x15-20170410060412.4k.img
boot-yocto-mdm9x15-20170410060412.4k.initramfs.img
boot-yocto-mdm9x15-20170410060907.2k.img
boot-yocto-mdm9x15-20170410060907.2k.initramfs.img
boot-yocto-mdm9x15-20170410060907.4k.img
boot-yocto-mdm9x15-20170410060907.4k.initramfs.img
boot-yocto-mdm9x15.2k.img
boot-yocto-mdm9x15.2k.initramfs.img
boot-yocto-mdm9x15.4k.img
boot-yocto-mdm9x15.4k.initramfs.img
boot-yocto-mdm9x15.img
boot-yocto_wp85.cwe
kernel
mdm9x15-image-initramfs-swi-mdm9x15-20170407121219.rootfs.cpio.gz
mdm9x15-image-initramfs-swi-mdm9x15-20170407121219.rootfs.manifest
mdm9x15-image-initramfs-swi-mdm9x15-20170407121219.rootfs.tar.bz2
mdm9x15-image-initramfs-swi-mdm9x15.cpio.gz
mdm9x15-image-initramfs-swi-mdm9x15.manifest
mdm9x15-image-initramfs-swi-mdm9x15.tar.bz2
mdm9x15-image-minimal-swi-mdm9x15-20170407121219.2k.ubi
mdm9x15-image-minimal-swi-mdm9x15-20170407121219.4k.ubi
mdm9x15-image-minimal-swi-mdm9x15-20170407121219.rootfs.4k.yaffs2
mdm9x15-image-minimal-swi-mdm9x15-20170407121219.rootfs.manifest
mdm9x15-image-minimal-swi-mdm9x15-20170407121219.rootfs.squashfs
mdm9x15-image-minimal-swi-mdm9x15-20170407121219.rootfs.tar.bz2
mdm9x15-image-minimal-swi-mdm9x15-20170407121219.rootfs.version
mdm9x15-image-minimal-swi-mdm9x15-20170407121219.rootfs.yaffs2
mdm9x15-image-minimal-swi-mdm9x15-20170407121219-user1.2k.ubi
mdm9x15-image-minimal-swi-mdm9x15-20170407121219-user1.4k.ubi
mdm9x15-image-minimal-swi-mdm9x15.2k.default
mdm9x15-image-minimal-swi-mdm9x15.2k.ubi
mdm9x15-image-minimal-swi-mdm9x15.4k.default
mdm9x15-image-minimal-swi-mdm9x15.4k.ubi
mdm9x15-image-minimal-swi-mdm9x15.4k.yaffs2
mdm9x15-image-minimal-swi-mdm9x15.manifest
mdm9x15-image-minimal-swi-mdm9x15.squashfs
mdm9x15-image-minimal-swi-mdm9x15.tar.bz2
mdm9x15-image-minimal-swi-mdm9x15.ubi
mdm9x15-image-minimal-swi-mdm9x15-user1.2k.ubi
mdm9x15-image-minimal-swi-mdm9x15-user1.4k.ubi
mdm9x15-image-minimal-swi-mdm9x15.version
modules–3.14.29+git0+a00e464379_b0ce579abb-r0.1-swi-mdm9x15-20170407121219.tgz
modules-swi-mdm9x15.tgz
README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt
rootfs
user1-single-part-ubifs-empty_wp85.cwe
yocto_wp85.cwe
zImage
zImage–3.14.29+git0+a00e464379_b0ce579abb-r0.1-qcom-msm9615-20170407121219.dtb
zImage–3.14.29+git0+a00e464379_b0ce579abb-r0.1-swi-mdm9x15-20170407121219.bin
zImage-initramfs-3.14.29+gitAUTOINC+a00e464379_b0ce579abb-r0.1-swi-mdm9x15-20170407121219.bin
zImage-initramfs-swi-mdm9x15.bin
zImage-qcom-msm9615.dtb
zImage-swi-mdm9x15.bin

The device is shown as a Google Device:

kilian@kilian-VirtualBox:~/yocto/build_bin/tmp/deploy/images/swi-mdm9x15$ lsusb
Bus 001 Device 005: ID 18d1:d00d Google Inc.


#2

Fixed it :slight_smile:

The link from the kernel file in the /build_bin/tmp/deploy/images/swi-mdm9x15 was set to a wrong file:

lrwxrwxrwx 1 kilian kilian 22 Apr 10 08:09 kernel -> boot-yocto-mdm9x15.img

The solution is to flash the boot-yocto-mdm9x15.2k.img file with

sudo fastboot flash kernel boot-yocto-mdm9x15.2k.img

Now my device is booting normal again :slight_smile: