superna9999 / meta-meson Goto Github PK

View Code? Open in Web Editor NEW

98.0 16.0 66.0 2.93 MB

Upstream Linux Amlogic Meson Yocto/OpenEmbedded Layer

Home Page: https://github.com/superna9999/meta-meson/wiki

License: MIT License

BitBake 64.85% Batchfile 4.28% Shell 13.93% Dockerfile 2.24% Python 13.01% Jinja 1.70%

amlogic yocto open-embedded upstream linux bsp

meta-meson's Introduction

Upstream Linux Amlogic Meson Yocto/Openembedded Layer

Now Amlogic SoCs of the Meson family are supported upstream :

Meson8b : s805
Meson-GX : s905 (GXBB) s905x/S905d (GXL) s912 (GXM)
Meson AXG : a113d
Meson G12A : S905X2, S905D2, S905Y2
Meson G12B : S922X, A311D
Meson SM1 : S905X3, S905D3

This Yocto/Openembedded will help building images for these SoCs using the lastest uptream linux branch.

Build Setup

Create a home repository for the build :

$ mkdir amlogic-bsp

Checkout Yocto/Poky :

$ cd amlogic-bsp
amlogic-bsp$ git clone --depth 1 git://git.yoctoproject.org/poky -b nanbield poky

Checkout meta-meson :

amlogic-bsp$ git clone https://github.com/superna9999/meta-meson.git meta-meson -b nanbield

Initialize environment :

amlogic-bsp$ TEMPLATECONF=../meta-meson/conf/templates/default
amlogic-bsp$ source poky/oe-init-build-env
amlogic-bsp/build$ cp ../poky/meta-poky/conf/local.conf.sample conf/local.conf

or :

amlogic-bsp$ source poky/oe-init-build-env
amlogic-bsp/build$ bitbake-layers add-layer $PWD/../meta-meson/

Selecting Machine to build for

This layer aims to support all mainline supported boards, but some of them have a vendor U-Boot loaded on the eMMC and can only be booted by pressing the "update" button.

The libretech-cc, hardkernel-odroidc2, amlogic-p212 and khadas-vim are fully mainline sdcard images, with mainline U-Boot and mainline Linux with a single ext4 partition. To boot this image the eMMC u-boot must be disabled by erasing the first sectors of the eMMC or removing it for libretech-cc and hardkernel-odroidc2 boards.

Available S805 machines are :

hardkernel-odroidc1 : .wic image to be booted using vendor u-boot
amlogic-s805 (all S805 machines) : generic non-bootable .wic image to be customized

Available S905 machines are :

amlogic-p200 : complete .wic sdcard image with mainline U-boot
amlogic-p200-sdboot : .wic image to be booted using vendor u-boot
amlogic-p201 : complete .wic sdcard image with mainline U-boot
amlogic-p201-sdboot : .wic image to be booted using vendor u-boot
hardkernel-odroidc2 : complete .wic sdcard image with mainline U-boot
hardkernel-odroidc2-sdboot : .wic image to be booted using vendor u-boot
tronsmart-vega-s95-pro : .wic image to be booted using vendor u-boot
tronsmart-vega-s95-meta : .wic image to be booted using vendor u-boot
tronsmart-vega-s95-telos : .wic image to be booted using vendor u-boot
nexbox-a95x-s905 : .wic image to be booted using vendor u-boot
wetek-hub : .wic image to be booted using vendor u-boot
wetek-play2 : .wic image to be booted using vendor u-boot
amlogic-s905 (all S905 machines) : generic non-bootable .wic image to be customized

Available S905D machines are :

amlogic-p230 : .wic image to be booted using vendor u-boot
amlogic-p231 : .wic image to be booted using vendor u-boot
mecool-kii-pro : .wic image to be booted using vendor u-boot
amlogic-s905d (all S905D machines) : generic non-bootable .wic image to be customized

Available S905X machines are :

libretech-ac : complete bootable .wic sdcard image using already flashed u-boot on SPI
libretech-cc : complete bootable .wic sdcard image with mainline U-boot
libretech-cc-sdboot : .wic image to be booted using vendor u-boot
amlogic-p212 : complete bootable .wic sdcard image with mainline U-boot
amlogic-p212-sdboot : .wic image to be booted using vendor u-boot
nexbox-a95x-s905x : .wic image to be booted using vendor u-boot
khadas-vim : complete bootable .wic sdcard image with mainline U-boot
khadas-vim-sdboot : .wic image to be booted using vendor u-boot
hwacom-amazetv : .wic image to be booted using vendor u-boot
amlogic-p241: .wic image to be booted using vendor u-boot
amlogic-p281: .wic image to be booted using vendor u-boot
oranth-tx3-mini: .wic image to be booted using vendor u-boot
osmc-vero4k-plus .wic image to be booted using vendor u-boot
amlogic-s905x (all S905X machines) : generic non-bootable .wic image to be customized

Available S912 machines are :

amlogic-q200 : .wic image to be booted using vendor u-boot
amlogic-q201 : .wic image to be booted using vendor u-boot
nexbox-a1 : .wic image to be booted using vendor u-boot
khadas-vim2 : .wic image to be booted using vendor u-boot
mecool-kiii-pro : .wic image to be booted using vendor u-boot
minix-neo-u9h : .wic image to be booted using vendor u-boot
beelink-gt1-ultimate: complete bootable .wic sdcard image with mainline U-boot
amlogic-s912 (all S912 machines) : generic non-bootable .wic image to be customized

Available A113d machine :

amlogic-s400 : complete bootable .wic eMMC image with mainline U-boot

Available S905X2 machines are :

amlogic-u200: .wic image to be booted using vendor u-boot
amediatech-x96-max: .wic image to be booted using vendor u-boot
seirobotics-sei510: complete bootable .wic sdcard image with mainline U-boot

Available S905Y2 machines are :

radxa-zero: complete bootable .wic sdcard image with mainline U-boot

Available S922X machines are :

hardkernel-odroidn2: complete bootable .wic sdcard image with mainline U-boot
hardkernel-odroidn2-sdboot: .wic image to be booted using vendor u-boot
hardkernel-odroidn2plus: complete bootable .wic sdcard image with mainline U-boot
hardkernel-odroidn2plus-sdboot: .wic image to be booted using vendor u-boot
hardkernel-odroid-n2l: complete bootable .wic sdcard image with mainline U-boot

Available A311D machines are :

khadas-vim3 : complete bootable .wic sdcard image with mainline U-boot
khadas-vim3-sdboot : .wic image to be booted using vendor u-boot
hardkernel-odroid-go-ultra: complete bootable .wic sdcard image with mainline U-boot
bananapi-bpi-m2s: complete bootable .wic sdcard image with mainline U-boot
bananapi-bpi-cm4io: complete bootable .wic sdcard image with mainline U-boot

Available S905X3/D3 machines are :

khadas-vim3l : complete bootable .wic sdcard image with mainline U-boot
khadas-vim3l-sdboot : .wic image to be booted using vendor u-boot
seirobotics-sei610: complete bootable .wic sdcard image with mainline U-boot
hardkernel-odroidc4: complete bootable .wic sdcard image with mainline U-boot
hardkernel-odroidc4-sdboot: .wic image to be booted using vendor u-boot
hardkernel-odroidhc4: complete bootable .wic sdcard image with mainline U-boot
hardkernel-odroidhc4-sdboot: .wic image to be booted using vendor u-boot
haochuangy-h96-max: .wic image to be booted using vendor u-boot
cyx-a95xf3-air: .wic image to be booted using vendor u-boot
cyx-a95xf3-air-gbit: .wic image to be booted using vendor u-boot
bananapi-bpi-m5: complete bootable .wic sdcard image with mainline U-boot
bananapi-bpi-m2-pro: complete bootable .wic sdcard image with mainline U-boot

Available S9xxx machines are :

amlogic-s9xxx (all S905 and S905X and S912 machines) : generic non-bootable .wic image to be customized

Selecting Image type

Images types available (in addition of standard Poky/OE images) :

amlogic-image-headless-sd : to flash on an eMMC or SD-Card
amlogic-image-headless-initrd : to be loaded as a ramdisk
amlogic-image-sato : Graphical images with X11 and Sato environment to flash on an eMMC or SD-Card

Standard types are :

core-image-base : Basic console image with boot logo

Building example

Building SD image for all S905 and S905X and S912 machines :

amlogic-bsp/build$ export MACHINE=amlogic-s9xxx
amlogic-bsp/build$ bitbake amlogic-image-sato

A .wic image will be generated in the tmp/deploy/images/$MACHINE/ directory.

This Image contains a FAT32 BOOT partition will the kernel uImage and .dtb, compatible with Amlogic U-Boot already flashed on your device.

For the amlogic-p212, khadas-vim and libretech-cc, Mainline U-Boot is automatically installed in a single ext4 partition .wic image in the tmp/deploy/images/$MACHINE/ directory.

Flash the .wic file with the Etcher tool from https://etcher.io/

Or for the connoisseurs :

You will be able to dd the image onto the raw SDcard like :

sudo dd if=tmp/deploy/images/libretech-cc/core-image-sato-libretech-cc.wic of=/dev/mmcblk0

Build with kas

The kas tool is installed via Python pip. The recommended way is to use an virtual environment for this.

$ python3 -m venv venv
$ source venv/bin/activate
$ pip3 install wheel kas

To start a build we just need to run the command kas build <configuration>.yml

$ source venv/bin/activate
$ DL_DIR=/data/downloads SSTATE_DIR=/data/sstate-cache kas build kas/kas-poky-meson.yml

The environment variable DL_DIR will allow to use a common place for the downloads across different projects. The same applies to the SSTATE_DIR variable.

To build for a specific machine use the environment variable KAS_MACHINE.

Please check the kas manual for more details.

meta-meson's People

Contributors

Stargazers

Watchers

meta-meson's Issues

Failure to build u-boot for GXM

I tried building amlogic-image-sato for amlogic_q200 and failed for u-boot:

`| gcc -isystem/home/diego1/Downloads/amlogic-bsp/build/tmp/work/amlogic_q200-poky-linux/u-boot-amlogic/1_v2015.01+gitAUTOINC+ffd40ecd0e-r0/recipe-sysroot-native/usr/include -O2 -pipe -L/home/diego1/Downloads/amlogic-bsp/build/tmp/work/amlogic_q200-poky-linux/u-boot-amlogic/1_v2015.01+gitAUTOINC+ffd40ecd0e-r0/recipe-sysroot-native/usr/lib -L/home/diego1/Downloads/amlogic-bsp/build/tmp/work/amlogic_q200-poky-linux/u-boot-amlogic/1_v2015.01+gitAUTOINC+ffd40ecd0e-r0/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/home/diego1/Downloads/amlogic-bsp/build/tmp/work/amlogic_q200-poky-linux/u-boot-amlogic/1_v2015.01+gitAUTOINC+ffd40ecd0e-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/home/diego1/Downloads/amlogic-bsp/build/tmp/work/amlogic_q200-poky-linux/u-boot-amlogic/1_v2015.01+gitAUTOINC+ffd40ecd0e-r0/recipe-sysroot-native/lib -Wl,-rpath,/home/diego1/Downloads/amlogic-bsp/build/tmp/work/amlogic_q200-poky-linux/u-boot-amlogic/1_v2015.01+gitAUTOINC+ffd40ecd0e-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,/home/diego1/Downloads/amlogic-bsp/build/tmp/work/amlogic_q200-poky-linux/u-boot-amlogic/1_v2015.01+gitAUTOINC+ffd40ecd0e-r0/recipe-sysroot-native/lib -Wl,-O1 -Wl,--allow-shlib-undefined -Wl,--dynamic-linker=/home/diego1/Downloads/amlogic-bsp/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 -o scripts/kconfig/conf scripts/kconfig/conf.o scripts/kconfig/zconf.tab.o
| mkdir -p include/config include/generated
| scripts/kconfig/conf --silentoldconfig Kconfig
| ***
| *** Configuration file ".config" not found!
| ***
| *** Please run some configurator (e.g. "make oldconfig" or
| *** "make menuconfig" or "make xconfig").
| ***
| make[3]: *** [/home/diego1/Downloads/amlogic-bsp/build/tmp/work/amlogic_q200-poky-linux/u-boot-amlogic/1_v2015.01+gitAUTOINC+ffd40ecd0e-r0/git/scripts/kconfig/Makefile:37: silentoldconfig] Error 1
| make[2]: *** [/home/diego1/Downloads/amlogic-bsp/build/tmp/work/amlogic_q200-poky-linux/u-boot-amlogic/1_v2015.01+gitAUTOINC+ffd40ecd0e-r0/git/Makefile:477: silentoldconfig] Error 2
| make[1]: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/uboot.release'. Stop.
| make: *** [Makefile:147: sub-make] Error 2
| make: Leaving directory '/home/diego1/Downloads/amlogic-bsp/build/tmp/work/amlogic_q200-poky-linux/u-boot-amlogic/1_v2015.01+gitAUTOINC+ffd40ecd0e-r0/git'
| WARNING: exit code 1 from a shell command.
|
ERROR: Task (/home/diego1/Downloads/amlogic-bsp/poky/../meta-meson/recipes-bsp/u-boot/u-boot-amlogic_v2015.01.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4771 tasks of which 4762 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/diego1/Downloads/amlogic-bsp/poky/../meta-meson/recipes-bsp/u-boot/u-boot-amlogic_v2015.01.bb:do_compile
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
`
Build environment is Debian bullseye/sid I tried first all exactly as described in the readme, then tried master, with similar results.

Is there any obvious mistake I did?

Add recipe for s905w

Hello,

Are you planning to add recipe for s905w based devices.

If you need dtb here it is. https://github.com/AlexELEC/S905-trees/blob/master/S905W/gxl_p281_1g.dtb

Let me know if you need anything else.

u-boot build fail rocko - odroidc2

Hello,

I just tried to build hardkernel-odroidc2 as your guide line. But the u-boot-odroidc2 compilation is failed.
Do you have any idea to fix this? Thank you.

Build Configuration:
BB_VERSION           = "1.36.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "aarch64-poky-linux"
MACHINE              = "hardkernel-odroidc2"
DISTRO               = "poky"
DISTRO_VERSION       = "2.4.1"
TUNE_FEATURES        = "aarch64"
TARGET_FPU           = ""
meta
meta-poky
meta-yocto-bsp       = "rocko:16e22f3e37788afb83044f5089d24187d70094bd"
meta-meson           = "rocko:d05496d517922d9438727cba6742ab706c7af059"

Fail log:

| In file included from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/linux/compiler.h:54:0,
|                  from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/linux/byteorder/little_endian.h:12,
|                  from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/arch/arm/include/asm/byteorder.h:29,
|                  from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/compiler.h:125,
|                  from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/image.h:19,
|                  from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/common.h:82:
| /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/linux/compiler-gcc.h:114:1: fatal error: linux/compiler-gcc7.h: No such file or directory
|  #include gcc_header(__GNUC__)
|  ^~~~
| compilation terminated.
| In file included from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/linux/compiler.h:54:0,
|                  from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/linux/byteorder/little_endian.h:12,
|                  from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/arch/arm/include/asm/byteorder.h:29,
|                  from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/compiler.h:125,
|                  from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/image.h:19,
|                  from /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/common.h:82:
| /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/include/linux/compiler-gcc.h:114:1: fatal error: linux/compiler-gcc7.h: No such file or directory
|  #include gcc_header(__GNUC__)
|  ^~~~
| compilation terminated.
| /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/scripts/Makefile.autoconf:64: recipe for target 'include/autoconf.mk' failed
| make[3]: *** [include/autoconf.mk] Error 1
| make[3]: *** Waiting for unfinished jobs....
| /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/scripts/Makefile.autoconf:40: recipe for target 'include/autoconf.mk.dep' failed
| make[3]: *** [include/autoconf.mk.dep] Error 1
| /opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git/Makefile:475: recipe for target 'silentoldconfig' failed
| make[2]: *** [silentoldconfig] Error 1
| make[1]: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/uboot.release'.  Stop.
| Makefile:147: recipe for target 'sub-make' failed
| make: *** [sub-make] Error 2
| make: Leaving directory '/opt/newwork/p/yocto/build/tmp/work/hardkernel_odroidc2-poky-linux/u-boot-odroidc2/1_v2015.01+gitAUTOINC+205c7b3259-r0/git'

ERROR: mesa-2_21.0.3-r0 do_configure: meson failed

Hi superna9999,
I‘m adding meta-kodi(https://github.com/koenkooi/meta-kodi) to meta-meson..the branch is hardknott.
but I encountered the fellow errors:

ERROR: Logfile of failure stored in: /home/yocto-crops/build/tmp/work/aarch64-poky-linux/mesa/2_21.0.3-r0/temp/log.do_configure.9831
ERROR: Task (/home/yocto-crops/poky/meta/recipes-graphics/mesa/mesa_21.0.3.bb:do_configure) failed with exit code '1'

In log.do_configure.9831

DEBUG: Executing python function extend_recipe_sysroot
NOTE: ......
NOTE:......
DEBUG: Python function extend_recipe_sysroot finished
DEBUG: Executing shell function do_configure
NOTE: Executing meson -Dshared-glapi=enabled -Dgallium-opencl=disabled -Dglx-read-only-text=true -Dplatforms=wayland,x11 -Ddri-drivers= -Ddri3=enabled -Degl=enabled -Delf-tls=true -Dgallium-drivers=swrast,kmsro,virgl,lima,panfrost -Dllvm=false -Dgbm=enabled -Dgles1=enabled -Dgles2=enabled -Dopengl=true -Dosmesa=false -Dlibunwind=disabled -Dgallium-va=enabled -Dgallium-vdpau=enabled -Dvulkan-drivers= -Dgallium-xa=disabled -Dgallium-xvmc=disabled...
The Meson build system
Version: 0.57.1
Source dir: /home/yocto-crops/build/tmp/work/aarch64-poky-linux/mesa/2_21.0.3-r0/mesa-21.0.3
Build dir: /home/yocto-crops/build/tmp/work/aarch64-poky-linux/mesa/2_21.0.3-r0/build
Build type: cross build
Program python3 found: YES (/home/yocto-crops/build/tmp/work/aarch64-poky-linux/mesa/2_21.0.3-r0/recipe-sysroot-native/usr/bin/python3-native/python3)
Project name: mesa
Project version: 21.0.3
C compiler for the host machine: aarch64-poky-linux-gcc -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/yocto-crops/build/tmp/work/aarch64-poky-linux/mesa/2_21.0.3-r0/recipe-sysroot (gcc 10.2.0 "aarch64-poky-linux-gcc (GCC) 10.2.0")
C linker for the host machine: aarch64-poky-linux-gcc -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/yocto-crops/build/tmp/work/aarch64-poky-linux/mesa/2_21.0.3-r0/recipe-sysroot ld.bfd 2.36.1.20210209
C++ compiler for the host machine: aarch64-poky-linux-g++ -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/yocto-crops/build/tmp/work/aarch64-poky-linux/mesa/2_21.0.3-r0/recipe-sysroot (gcc 10.2.0 "aarch64-poky-linux-g++ (GCC) 10.2.0")
C++ linker for the host machine: aarch64-poky-linux-g++ -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/yocto-crops/build/tmp/work/aarch64-poky-linux/mesa/2_21.0.3-r0/recipe-sysroot ld.bfd 2.36.1.20210209
C compiler for the build machine: gcc (gcc 7.5.0 "gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0")
C linker for the build machine: gcc ld.bfd 2.30
C++ compiler for the build machine: g++ (gcc 7.5.0 "g++ (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0")
C++ linker for the build machine: g++ ld.bfd 2.30
Build machine cpu family: x86_64
Build machine cpu: x86_64
Host machine cpu family: aarch64
Host machine cpu: aarch64
Target machine cpu family: aarch64
Target machine cpu: aarch64
Found CMake: NO
Run-time dependency clang found: NO (tried cmake)

../mesa-21.0.3/meson.build:546:4: ERROR: Problem encountered: VDPAU state tracker requires at least one of the following gallium drivers: r300, r600, radeonsi, nouveau.

Use common recipe for meson32 & meson64

The meson32 and meson64 linux recipes are outdated and don't support fitImage and other features, cleanup all this with a single recipe to enable fitImage for U-Boot mainline supported boards.

Option to select 32bit

Is it possible to add option for selecting 32bit image?

Need support for my customized board (processor: amlogic s905w)

Dear Sir/Madam,

Myself Vasu Joshi. I have a customized board which has Amlogic s905w processor.

I want to build a sd card image for the same board. Can you please suggest me the steps how to start or is it enough if i follow the steps which is mentioned in the README section?

Thanks in advance.
Vasu Joshi

Trouble booting yocto image from uboot

Hi Neil,
I've completed a custom yocto build using your meta-meson but im having some issues getting it to boot via u-boot.

I see the following output in uboot and then it appears to hang...

`odroidc2#setenv bootcmd setenv bootargs console=ttyAML0,115200 consoleblank=0 root=/dev/mmcblk0p2 rootwait rw;mmc info;fatload mmc 1 0x1000000 meson-gxbb-odroidc2.dtb;fatload mmc 1 0x01080000 uImage;bootm 0x01080000 - 0x1000000

odroidc2#run bootcmd
Device: SDIO Port C
Manufacturer ID: 15
OEM: 100
Name: AGND3
Tran Speed: 52000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 14.6 GiB
Bus Width: 8-bit
ret = 1 .[mmc_init] mmc init success
reading meson-gxbb-odroidc2.dtb
14949 bytes read in 6 ms (2.4 MiB/s)
reading uImage
6856776 bytes read in 333 ms (19.6 MiB/s)
ee_gate_off ...
Booting kernel from Legacy Image at 01080000 ...
Image Name: Poky (Yocto Project Reference Di
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 6856712 Bytes = 6.5 MiB
Load Address: 01080000
Entry Point: 01080000
Verifying Checksum ... OK
load dtb from 0x1000000 ......
Flattened Device Tree blob at 01000000
Booting using the fdt blob at 0x1000000
Loading Kernel Image ... OK
kernel loaded at 0x01080000, end = 0x0170a008
Loading Device Tree to 000000001fff9000, end 000000001ffffa64 ... OK

Starting kernel ...

uboot time: 28678927 us
`
I dont see anything further on console (or hdmi) but heartbeat light is flashing.

I have triied both amlogic-s905 and hardkernel-odroidc2 version of the build and tried with hardkernel u-boot and also an upstream version, both with the same issue.

If you have the time, do you have any thoughts on what might be the problem?, maybe I have a build issue somewhere.

Many Thanks,

Brad.

Amlogic s905w processor is not booting

Hi,

I am trying to boot Amlogic s905w processor based board. For that i followed the same steps which is mentioned in the README document.

I did the set up of yocto and built the image successfully as you mentioned in the README. I have flashed the built image on sd card.

But, the board is not booting. Logs also not coming on HDMI monitor.

Can you please help me to resolve this problem.

Thanks in advance.
VJ

Get rid of vendor u-boot

Remove amlogic & khadas vendor U-Boot recipe

Rationale:
Mainline U-boot is now feature-rich and stable to permit removal of Amlogic u-boot version

u-boot ethernet phy regression on gxbb (nanopi-k2, odroid-c2)

Describe the bug
According to the feedback on this bug: home-assistant/operating-system#1202 ethernet/phy is working at least through 2020.04 u-boot release. Confirmed broken using poky/meta-meson on dunfell branches.

Build Context

meta-meson dunfell
meta-meson changes: none prior to reverting u-boot-meson-gx version requirement to 2020.01 (u-boot version on poky dunfell)
Yocto Project Poky/meta dunfell
meta-small-arm-extra dunfell
local.conf normal except for:

PREFERRED_PROVIDER_virtual/kernel ?= "linux-mainline"
PREFERRED_VERSION_linux-mainline ?= "5.10%"
# ethernet bug somewhere after this version
PREFERRED_VERSION_u-boot-meson-gx = "2020.01%"  <= broken without this

Expected behavior
Working ethernet.

System (please complete the following information):

Host OS: gentoo
Version: N/A
Architecture: x86_64

Additional context
Just building core-image-minimal with some packages, testing on nanopi-k2 and odroid-c2 (confirmed working with u-boot 2020.04 and kernel 5.10.14 with one small espressobin-ultra patch).

Ease integration with Mender (double partitions instead of single)

Make sure this layer can be easily used to build industrial images with features like Mender OTA or secure-boot.

Help is welcome to enable other features.

eMMC error on Khadas VIM2

Hello Neil,

I use the patches from https://github.com/superna9999/meta-meson/tree/master/recipes-kernel/linux/linux-yocto-meson64-4.20, and run linux 4.20.3 on Khadas VIM2, but I found the eMMC not work?

root@Khadas:~# dmesg | grep mmc1
[    4.550534] mmc1: error -110 whilst initialising MMC card

Do you have this issue?

Thanks.

S905W support

Hello, I'm just wondering when you can update for S905w?

More specifically for this little guy https://www.cnx-software.com/2017/08/24/x96-mini-amlogic-s905w-android-tv-box-sells-for-25-and-up/

Modify UBOOT_EXTLINUX_ROOT

On my Vim3, when booting I need to modify the UBOOT_EXTLINUX_ROOT to /dev/mmcblk1p1. With the current recipes, it is not possible to do this in my local.conf because it has a hard assignment in conf/machine/.conf.

Would you accept a PR that changes the line

UBOOT_EXTLINUX_ROOT = "root=/dev/mmcblk0p1"
to
UBOOT_EXTLINUX_ROOT ?= "root=/dev/mmcblk0p1"

as this would not change the default behaviour, but allow me to change the default to what I need?

If so, should I create a PR just for the vim3, or should I make the modification for all platforms that use UBOOT_EXTLINUX_ROOT?

incorrect sdimage root partition for khadas vim

if booting from sdcard, the root partition should be mmcblk0p1 and not mmcblk1p1 in /boot/extlinux/extlinux.conf

https://pastebin.com/vujKDz6Z

can't boot odroid-c2

Hi, I can't get an image based on this layer to boot on my odroid-c2 board following the instructions in the README file. Building an image with git://github.com/akuster/meta-odroid builds and boots fine on the exact same hardware (including SDcard).

I've tried rocko and master, OE/nodistro and poky. No combination was able to build successfully without #13, but even after successfully building, none booted. I've tried core-image-minimal, amlogic-image-sato, and amlogic-image-headless-sd.

The boot process doesn't seem to be leaving the firmware, it starts with:

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;

and then keeps repeating

LOOP:1;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;

over and over.

After writing the SDcard with the meta-odroid image, the partitioning looks like:

# fdisk -l /dev/sdi
Disk /dev/sdi: 14.4 GiB, 15489564672 bytes, 30253056 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x71ec0000

Device     Boot  Start    End Sectors  Size Id Type
/dev/sdi1         2048 264191  262144  128M  e W95 FAT16 (LBA)
/dev/sdi2       264192 481279  217088  106M 83 Linux

after meta-meson:

# fdisk -l /dev/sdi
Disk /dev/sdi: 14.4 GiB, 15489564672 bytes, 30253056 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe16276b6

Device     Boot Start     End Sectors   Size Id Type
/dev/sdi1  *        8   54763   54756  26.8M  c W95 FAT32 (LBA)
/dev/sdi2       54768 1141911 1087144 530.9M 83 Linux

The meta-odroid image also places a boot.scr file in the first (DOS) partition, which the meta-meson one doesn't (not sure if this is relevant).

trusted-firmware for vim3

I would like to get trusted-firmware-a running on the Khadas Vim3, so am working on a recipe to make this happen. meta-arm has vanilla recipes to do this, and upstream has support for g12a, which I believe is compatible with the g12b on the Vim3.

The problem I have is that won't be able to boot with the vendor u-boot as is the current supported mode with these recipes.

I would therefor need to create a u-boot recipe for the vim3 as well. But I am struggling to see the best way to achieve this with the current setup? Any pointers/suggestions would be appreciated - I don't mind doing the implementation work.

My plan would be to create a u-boot_2020.%.bbappend and add the signing code required to create the bootable image. Has anybody done this before?

The code required seems to be available in this repo https://github.com/LibreELEC/amlogic-boot-fip, and the plan would be to use this as apart of the u-boot overlay.

Enable fitImage by default

Enable fitImage for U-Boot mainline supported boards, this would permit easily support advanced secure-boot and OTA features.

Getting .py errors during the build process

I am getting .py errors during the build process, i made a terminal screenshot, am i maybe missing some python package, or maybe i need to edit some file.

I am on Ubuntu 16.04., making image for Vim1.

QT5 image

Hello,

Can you write instruction to building QT5 image?

Thanks in advance.

Add eMMC board variants OR make medium independant images (sd, eMMC, USB, NVME, SATA, ...)

Today, images are for SDCard (except the S400 board without an SDCard port).

Either add a -emmc variant and make boot=UUID= work somehow, with or without an initramfs.

build failed for Khadas VIM

Build Context

meta-meson branch: sumo
meta-meson changes: NO
Yocto Project Poky / oe-core branch: sumo
local.conf changes: NO
bitbake command: bitbake amlogic-image-sato

System:

Host OS: Ubuntu
Version: 16.04
Architecture: x86_64

Describe the bug
When I try to build Yocto for Khadas VIM but failed with some warnings & errors.
Build command:

$ TEMPLATECONF=../meta-meson/conf
$ source poky/oe-init-build-env
$ export MACHINE=khadas-vim
$ bitbake amlogic-image-sato

But I got some warnings & errors:

WARNING: quilt-native-0.65-r0 do_fetch: Failed to fetch URL http://download.savannah.gnu.org/releases/quilt/quilt-0.65.tar.gz, attempting MIRRORS if available
WARNING: attr-native-2.4.47-r0 do_fetch: Failed to fetch URL http://download.savannah.gnu.org/releases/attr/attr-2.4.47.src.tar.gz, attempting MIRRORS if available
WARNING: popt-native-1.16-r3 do_fetch: Failed to fetch URL http://rpm5.org/files/popt/popt-1.16.tar.gz, attempting MIRRORS if available
WARNING: shadow-4.2.1-r0 do_fetch: Failed to fetch URL http://pkg-shadow.alioth.debian.org/releases/shadow-4.2.1.tar.xz, attempting MIRRORS if available
WARNING: libsndfile1-1.0.28-r0 do_fetch: Failed to fetch URL http://www.mega-nerd.com/libsndfile/files/libsndfile-1.0.28.tar.gz, attempting MIRRORS if available
WARNING: acl-2.2.52-r0 do_fetch: Failed to fetch URL http://download.savannah.gnu.org/releases/acl/acl-2.2.52.src.tar.gz, attempting MIRRORS if available
WARNING: iso-codes-3.77-r0 do_fetch: Failed to fetch URL https://pkg-isocodes.alioth.debian.org/downloads/iso-codes-3.77.tar.xz, attempting MIRRORS if available
WARNING: libsamplerate0-0.1.9-r1 do_fetch: Failed to fetch URL http://www.mega-nerd.com/SRC/libsamplerate-0.1.9.tar.gz, attempting MIRRORS if available
WARNING: lzip-native-1.19-r0 do_fetch: Failed to fetch URL http://download.savannah.gnu.org/releases/lzip/lzip-1.19.tar.gz, attempting MIRRORS if available
WARNING: sysvinit-2.88dsf-r14 do_fetch: Failed to fetch URL http://download.savannah.gnu.org/releases/sysvinit/sysvinit-2.88dsf.tar.bz2, attempting MIRRORS if available
WARNING: mktemp-1.7-r3 do_fetch: Failed to fetch URL ftp://ftp.mktemp.org/pub/mktemp/mktemp-1.7.tar.gz, attempting MIRRORS if available
WARNING: linux-yocto-meson64-4.17.0+gitAUTOINC+29dcea8877-r0 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
checking file arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
Hunk #1 succeeded at 265 with fuzz 1.
WARNING: linux-yocto-meson64-4.17.0+gitAUTOINC+29dcea8877-r0 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
patching file arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
Hunk #1 succeeded at 265 with fuzz 1.
ERROR: linux-yocto-meson64-4.17.0+gitAUTOINC+29dcea8877-r0 do_compile: oe_runmake failed
ERROR: linux-yocto-meson64-4.17.0+gitAUTOINC+29dcea8877-r0 do_compile: Function failed: do_compile (log file is located at /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work/khadas_vim-oe-linux/linux-yocto-meson64/4.17.0+gitAUTOINC+29dcea8877-r0/temp/log.do_compile.11487)
ERROR: Logfile of failure stored in: /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work/khadas_vim-oe-linux/linux-yocto-meson64/4.17.0+gitAUTOINC+29dcea8877-r0/temp/log.do_compile.11487

The warnings seem to be that some packages are failed to download, maybe network issue? (I have a VPN.)

And build linux failed too:

|   CC      lib/mpi/mpih-cmp.o
|   AR      sound/soc/jz4740/built-in.a
|   AR      sound/soc/kirkwood/built-in.a
|   AR      sound/soc/mediatek/built-in.a
|   CC      sound/soc/meson/audio-core.o
|   CC      net/ipv4/ip_input.o
|   CC      lib/mpi/mpih-div.o
|   CC      net/ipv6/protocol.o
|   CC      drivers/base/dma-contiguous.o
|   CC      sound/soc/meson/aiu-i2s-dma.o
|   CC      sound/soc/meson/i2s-dai.o
|   CC      fs/lockd/svclock.o
|   CC      lib/mpi/mpih-mul.o
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c: In function 'aiu_i2s_dma_priv':
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:111:9: error: implicit declaration of function 'snd_soc_platform_get_drvdata'; did you mean 'snd_soc_card_get_drvdata'? [-Werror=implicit-function-declaration]
|   return snd_soc_platform_get_drvdata(rtd->platform);
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
|          snd_soc_card_get_drvdata
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:111:41: error: 'struct snd_soc_pcm_runtime' has no member named 'platform'
|   return snd_soc_platform_get_drvdata(rtd->platform);
|                                          ^~
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c: At top level:
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:315:8: error: variable 'aiu_i2s_platform' has initializer but incomplete type
|  struct snd_soc_platform_driver aiu_i2s_platform = {
|         ^~~~~~~~~~~~~~~~~~~~~~~
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:316:3: error: 'struct snd_soc_platform_driver' has no member named 'ops'
|   .ops  = &aiu_i2s_dma_ops,
|    ^~~
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:316:10: warning: excess elements in struct initializer
|   .ops  = &aiu_i2s_dma_ops,
|           ^
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:316:10: note: (near initialization for 'aiu_i2s_platform')
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:317:3: error: 'struct snd_soc_platform_driver' has no member named 'pcm_new'
|   .pcm_new = aiu_i2s_dma_new,
|    ^~~~~~~
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:317:13: warning: excess elements in struct initializer
|   .pcm_new = aiu_i2s_dma_new,
|              ^~~~~~~~~~~~~~~
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:317:13: note: (near initialization for 'aiu_i2s_platform')
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c: In function 'aiu_i2s_dma_probe':
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:345:9: error: implicit declaration of function 'snd_soc_register_platform'; did you mean 'snd_soc_register_card'? [-Werror=implicit-function-declaration]
|   return snd_soc_register_platform(dev, &aiu_i2s_platform);
|          ^~~~~~~~~~~~~~~~~~~~~~~~~
|          snd_soc_register_card
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c: At top level:
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/sound/soc/meson/aiu-i2s-dma.c:315:32: error: storage size of 'aiu_i2s_platform' isn't known
|  struct snd_soc_platform_driver aiu_i2s_platform = {
|                                 ^~~~~~~~~~~~~~~~
| cc1: some warnings being treated as errors
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/scripts/Makefile.build:317: recipe for target 'sound/soc/meson/aiu-i2s-dma.o' failed
| make[5]: *** [sound/soc/meson/aiu-i2s-dma.o] Error 1
| make[5]: *** Waiting for unfinished jobs....
|   CC      lib/mpi/mpi-pow.o
|   CC      net/ipv4/ip_fragment.o
|   CC      drivers/base/dma-mapping.o
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/scripts/Makefile.build:558: recipe for target 'sound/soc/meson' failed
| make[4]: *** [sound/soc/meson] Error 2
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/scripts/Makefile.build:558: recipe for target 'sound/soc' failed
| make[3]: *** [sound/soc] Error 2
| /home/nick/code/git/amlogic/amlogic-bsp/build/tmp-glibc/work-shared/khadas-vim/kernel-source/Makefile:1034: recipe for target 'sound' failed
| make[2]: *** [sound] Error 2
| make[2]: *** Waiting for unfinished jobs....
|   CC      drivers/base/dma-coherent.o
|   CC      net/ipv6/ip6_offload.o
|   CC      lib/mpi/mpiutil.o
|   CC      net/core/datagram.o
|   CC      net/core/stream.o
|   CC      fs/lockd/svcshare.o
|   CC      drivers/base/module.o
|   CC      drivers/base/soc.o
|   AR      lib/mpi/built-in.a
|   CC      lib/xz/xz_dec_syms.o
|   CC      lib/xz/xz_dec_stream.o
|   CC      drivers/base/pinctrl.o
|   CC      net/ipv4/ip_forward.o
|   CC      lib/xz/xz_dec_lzma2.o
|   CC      net/ipv6/tcpv6_offload.o
|   CC      net/core/scm.o
|   CC      lib/xz/xz_dec_bcj.o
|   CC      drivers/base/platform-msi.o
|   CC      fs/lockd/svcproc.o
|   CC      net/core/gen_stats.o
|   CC      net/ipv4/ip_options.o
|   CC      drivers/base/arch_topology.o
|   AR      lib/xz/built-in.a
|   CC      lib/zlib_inflate/inffast.o
|   CC      lib/zlib_inflate/inflate.o
|   CC      net/ipv6/exthdrs_offload.o
|   CC      lib/zlib_inflate/infutil.o
|   AR      drivers/base/built-in.a
|   CC      lib/zlib_inflate/inftrees.o
|   CC      lib/zlib_inflate/inflate_syms.o
|   CC      net/core/gen_estimator.o
|   CC      drivers/block/loop.o
|   CC      fs/lockd/svcsubs.o
|   CC      fs/lockd/mon.o
|   CC      fs/lockd/xdr.o
|   AR      lib/zlib_inflate/built-in.a
|   GEN     lib/oid_registry_data.c
|   CC      lib/lockref.o
|   CC      net/ipv6/inet6_hashtables.o
|   CC      lib/bcd.o
|   CC      net/ipv4/ip_output.o
|   CC      lib/div64.o
|   CC      lib/sort.o
|   CC      net/core/net_namespace.o
|   CC      lib/parser.o
|   CC      fs/lockd/clnt4xdr.o
|   CC      fs/lockd/xdr4.o
|   CC      lib/debug_locks.o
|   CC      fs/lockd/svc4proc.o
|   CC      lib/random32.o
|   CC      net/ipv6/mcast_snoop.o
|   CC      drivers/block/virtio_blk.o
|   CC      lib/bust_spinlocks.o
|   CC      fs/lockd/procfs.o
|   CC      net/core/flow_dissector.o
|   CC      net/core/secure_seq.o
|   CC      lib/kasprintf.o
|   CC      drivers/block/xen-blkfront.o
|   AR      net/ipv6/built-in.a
|   CC      lib/bitmap.o
|   CC      lib/scatterlist.o
|   AR      fs/lockd/built-in.a
|   CC      net/ipv4/ip_sockglue.o
|   CC      fs/nfs/filelayout/filelayout.o
|   CC      net/netfilter/core.o
|   CC      net/core/sysctl_net_core.o
|   CC      lib/gcd.o
|   CC      lib/lcm.o
|   CC      lib/list_sort.o
|   CC      lib/uuid.o
|   CC      lib/flex_array.o
|   CC      lib/iov_iter.o
|   CC      net/core/dev.o
|   CC      net/netfilter/nf_log.o
|   CC      net/core/ethtool.o
|   CC      lib/clz_ctz.o
|   AR      drivers/block/built-in.a
|   CC      net/ipv4/inet_hashtables.o
|   CC      lib/bsearch.o
|   AR      drivers/bus/built-in.a
|   AR      drivers/cdrom/built-in.a
|   CC      lib/find_bit.o
|   AR      drivers/char/agp/built-in.a
|   CC      drivers/char/mem.o
|   CC      lib/llist.o
|   CC      fs/nfs/filelayout/filelayoutdev.o
|   CC      lib/memweight.o
|   CC      lib/kfifo.o
|   CC      net/netfilter/nf_queue.o
|   CC      drivers/char/random.o
|   AR      fs/nfs/filelayout/built-in.a
|   CC      fs/nfs/client.o
|   CC      lib/percpu-refcount.o
|   CC      net/ipv4/inet_timewait_sock.o
|   CC      fs/nfs_common/grace.o
|   CC      net/netfilter/nf_sockopt.o
|   CC      lib/percpu_ida.o
|   CC      net/core/dev_addr_lists.o
|   AR      fs/nfs_common/built-in.a
|   CC      fs/nls/nls_base.o
|   CC      drivers/char/misc.o
|   CC      net/ipv4/inet_connection_sock.o
|   CC      lib/rhashtable.o
|   CC      fs/nls/nls_cp437.o
|   CC      net/netfilter/utils.o
|   CC      drivers/char/virtio_console.o
|   CC      fs/nls/nls_iso8859-1.o
|   CC      fs/nfs/dir.o
|   CC      net/core/dst.o
|   AR      fs/nls/built-in.a
|   CC      fs/notify/dnotify/dnotify.o
|   CC      lib/reciprocal_div.o
|   AR      net/netfilter/built-in.a
|   CC      fs/notify/fanotify/fanotify.o
|   CC      lib/once.o
|   AR      fs/notify/dnotify/built-in.a
|   CC      fs/notify/fanotify/fanotify_user.o
|   CC      lib/refcount.o
|   CC      net/ipv4/tcp.o
|   CC      lib/usercopy.o
|   CC      net/core/netevent.o
|   CC      fs/notify/inotify/inotify_fsnotify.o
|   AR      drivers/char/built-in.a
|   CC      lib/errseq.o
|   AR      drivers/char/ipmi/built-in.a
|   AR      drivers/clk/actions/built-in.a
|   AR      drivers/clk/bcm/built-in.a
|   CC      lib/bucket_locks.o
|   AR      drivers/clk/imgtec/built-in.a
|   AR      drivers/clk/mediatek/built-in.a
|   CC      drivers/clk/meson/clk-pll.o
|   CC      fs/notify/inotify/inotify_user.o
|   AR      fs/notify/fanotify/built-in.a
|   AR      drivers/clk/mvebu/built-in.a
|   CC      drivers/clk/meson/clk-mpll.o
|   CC      drivers/clk/meson/clk-audio-divider.o
|   CC      net/core/neighbour.o
|   CC      lib/string_helpers.o
|   CC      fs/nfs/file.o
|   CC      drivers/clk/meson/meson-aoclk.o
|   CC      drivers/clk/meson/gxbb.o
|   CC      drivers/clk/meson/gxbb-aoclk.o
|   AR      fs/notify/inotify/built-in.a
|   CC      fs/notify/fsnotify.o
|   CC      drivers/clk/meson/gxbb-aoclk-32k.o
|   CC      lib/hexdump.o
|   CC      drivers/clk/meson/axg.o
|   CC      fs/notify/notification.o
|   CC      lib/kstrtox.o
|   CC      fs/notify/group.o
|   CC      drivers/clk/meson/axg-aoclk.o
|   CC      drivers/clk/meson/clk-regmap.o
|   CC      lib/pci_iomap.o
|   CC      fs/nfs/getroot.o
|   CC      lib/iomap_copy.o
|   CC      fs/nfs/inode.o
|   CC      fs/notify/mark.o
|   AR      drivers/clk/meson/built-in.a
|   AR      drivers/clk/renesas/built-in.a
|   AR      drivers/clk/ti/built-in.a
|   CC      net/ipv4/tcp_input.o
|   CC      drivers/clk/versatile/clk-sp810.o
|   CC      lib/devres.o
|   CC      lib/logic_pio.o
|   AR      drivers/clk/versatile/built-in.a
|   CC      drivers/clk/clk-devres.o
|   CC      lib/hweight.o
|   CC      lib/assoc_array.o
|   CC      fs/nfs/super.o
|   CC      fs/notify/fdinfo.o
|   CC      lib/bitrev.o
|   CC      lib/rational.o
|   CC      drivers/clk/clk-bulk.o
|   CC      lib/crc16.o
|   CC      net/core/rtnetlink.o
|   AR      fs/notify/built-in.a
|   CC      lib/crc-t10dif.o
|   CC      drivers/clk/clkdev.o
|   CC      fs/proc/task_mmu.o
|   CC      lib/crc-itu-t.o
|   CC      lib/crc7.o
|   CC      fs/nfs/io.o
|   CC      lib/genalloc.o
|   CC      drivers/clk/clk.o
|   CC      lib/percpu_counter.o
|   CC      lib/audit.o
|   CC      fs/nfs/direct.o
|   CC      lib/compat_audit.o
|   CC      fs/nfs/pagelist.o
|   CC      fs/proc/inode.o
|   CC      lib/swiotlb.o
|   CC      lib/syscall.o
|   CC      fs/proc/root.o
|   CC      lib/nlattr.o
|   CC      drivers/clk/clk-divider.o
|   CC      lib/checksum.o
|   CC      fs/nfs/read.o
|   CC      fs/proc/base.o
|   CC      lib/cpu_rmap.o

Flashing image to eMMC

Hello,

I've successfully compiled P281 image. Now how do I flash image to emmc?

Can we use Amlogic USB burning tool?

Patchset with redundant entries

Hi Neil,

The 4.14 patchset has some of the old patches still in it, they didn't get removed in the commit.

Finding correct image version

Please forgive my ignorance, I come from an OpenWRT background so OE/Yocto is new to me.

I am interested is using the Amlogic S905x box (Best bang for buck) but how do i determine which of the S905x images I should use?

I hope this isn't a stupid question, I don't want to brick the device first time out.

Thank you,

Patch order 4.18

Patch order for kernel recipe 4.18.

0001-ARM64-dts-meson-add-vdec-entries.patch needs to be applied after all of the other patches.

Get rid of -sdboot variant for U-Boot Upstream supported boards

Remove legacy boot on boards supported by mainline U-boot

Rationale:
Mainline U-boot is now stable and feature-rich enough to stop using vendor u-boot for these boards.

An exception could stay for boards shipped with a "rich" vendor u-boot like Hardkernel, for this help would be needed to correctly support these

missing nanopi-k2 MACHINE?

There appears to be support for the nanopi-k2 machine (recipes-bsp/u-boot/u-boot-nanopi-k2_v2015.01.bb) but does there need to be a nanopi.conf in conf/machine?

Conflict in appropriate files - need help

Hello,

I have been trying to compile my first image but I have come up against the below issue.

I have seen somewhere that I should pin a file, but how do I do this? I can't find a tutorial or any reference to what that means.

`
_================================================================================
Install 612 Packages

Total size: 110 M
Installed size: 403 M
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction check error:
file /etc/iproute2/rt_protos conflicts between attempted installs of base-files-3.0.14-r89.nexbox_a95x_s905x and iproute2-4.14.1-r0.aarch64
file /etc/iproute2/rt_tables conflicts between attempted installs of base-files-3.0.14-r89.nexbox_a95x_s905x and iproute2-4.14.1-r0.aarch64
file /etc/sysctl.conf conflicts between attempted installs of base-files-3.0.14-r89.nexbox_a95x_s905x and procps-3.3.12-r0.aarch64

Error Summary

ERROR: amlogic-image-headless-sd-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/user/amlogic-bsp/build/tmp/work/nexbox_a95x_s905x-poky-linux/amlogic-image-headless-sd/1.0-r0/temp/log.do_rootfs.29264
ERROR: Task (/home/user/amlogic-bsp/meta-meson/recipes-core/images/amlogic-image-headless-sd.bb:do_rootfs) failed with exit code 1
NOTE: Tasks Summary: Attempted 3131 tasks of which 3130 didn't need to be rerun and 1 failed._
'

I have also getting the below warning. Is this related? I don't think it is.

WARNING: Layer meson should set LAYERSERIES_COMPAT_meson in its conf/layer.conf file to list the core layer names it is compatible with.

Many thanks,

Kernel 4.13

I checked the last commit with kernel 4.13. The system gathered and normally runs on s905X. By the way, I created a theme for the project Yocto (meta-meson) on the forum Khadas.

http://forum.khadas.com/t/the-project-ycto-linux/1098

- nothing provides linux-firmware-bcm43430a0 needed by packagegroup-core-boot-1.0-r17.seirobotics_sei610

My git branch:

git clone --depth 1 git://git.yoctoproject.org/poky -b hardknott  poky
git clone https://github.com/superna9999/meta-meson.git -b hardknott 
git clone git://git.openembedded.org/meta-openembedded -b hardknott 
git clone git://git.yoctoproject.org/meta-virtualization -b hardknott 
git clone git://git.yoctoproject.org/meta-security -b hardknott 
git clone git://github.com/kraj/meta-clang -b hardknott

My local.conf:

MACHINE = "seirobotics-sei610" #or "khadas-vim3l"
DL_DIR ?= "/home/yocto-crops/downloads"
BB_GENERATE_MIRROR_TARBALLS = "1"
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
BB_NUMBER_THREADS = "8"
PARALLEL_MAKE = "-j 8"
LICENSE_FLAGS_WHITELIST += " commercial_mpg123 commercial commercial_libav commercial_x264 commercial"
DISTRO_FEATURES_append = " virtualization"
PACKAGE_CLASSES ?= "package_ipk"
IMAGE_INSTALL_append += " bash docker-ce docker-ce-contrib python3 python3-docker-compose"

My BBLAYERS :

BBLAYERS ?= " \
  /home/yocto-crops/poky/meta \
  /home/yocto-crops/poky/meta-poky \
  /home/yocto-crops/poky/meta-yocto-bsp \
  /home/yocto-crops/meta-openembedded/meta-oe \
  /home/yocto-crops/meta-openembedded/meta-python \
  /home/yocto-crops/meta-openembedded/meta-perl \
  /home/yocto-crops/meta-openembedded/meta-networking \
  /home/yocto-crops/meta-openembedded/meta-filesystems \
  /home/yocto-crops/meta-openembedded/meta-webserver \
  /home/yocto-crops/meta-virtualization \
  /home/yocto-crops/meta-security \
  /home/yocto-crops/meta-meson \
  "

The ERRO:

ERROR: amlogic-image-headless-initrd-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/yocto-crops/build/tmp/work/seirobotics_sei610-poky-linux/amlogic-image-headless-initrd/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=info -y -c /home/yocto-crops/build/tmp/work/seirobotics_sei610-poky-linux/amlogic-image-headless-initrd/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/yocto-crops/build/tmp/work/seirobotics_sei610-poky-linux/amlogic-image-headless-initrd/1.0-r0/rootfs/etc/yum.repos.d --installroot=/home/yocto-crops/build/tmp/work/seirobotics_sei610-poky-linux/amlogic-image-headless-initrd/1.0-r0/rootfs --setopt=logdir=/home/yocto-crops/build/tmp/work/seirobotics_sei610-poky-linux/amlogic-image-headless-initrd/1.0-r0/temp --repofrompath=oe-repo,/home/yocto-crops/build/tmp/work/seirobotics_sei610-poky-linux/amlogic-image-headless-initrd/1.0-r0/oe-rootfs-repo --nogpgcheck install bash docker-ce docker-ce-contrib kernel-devicetree kernel-modules linux-firmware packagegroup-core-boot packagegroup-core-ssh-openssh python3 python3-docker-compose run-postinsts locale-base-en-us locale-base-en-gb' returned 1:
DNF version: 4.6.0
cachedir: /home/yocto-crops/build/tmp/work/seirobotics_sei610-poky-linux/amlogic-image-headless-initrd/1.0-r0/rootfs/var/cache/dnf
Added oe-repo repo from /home/yocto-crops/build/tmp/work/seirobotics_sei610-poky-linux/amlogic-image-headless-initrd/1.0-r0/oe-rootfs-repo
User-Agent: falling back to 'libdnf': could not detect OS or basearch
repo: using cache for: oe-repo
oe-repo: using metadata from Tue 30 Nov 2021 08:29:14 AM UTC.
Last metadata expiration check: 0:00:01 ago on Tue 30 Nov 2021 08:29:15 AM UTC.
--> Starting dependency resolution
--> Finished dependency resolution
Error: 
 Problem: conflicting requests
  - nothing provides linux-firmware-bcm43430a0 needed by packagegroup-core-boot-1.0-r17.seirobotics_sei610
(try to add '--skip-broken' to skip uninstallable packages)

when MACHINE = "hardkernel-odroidc4" pass all.

libretech-cc-sdboot doesn't boot

Hello,

I have compiled amlogic-image-sato using libretech-cc-sdboot option.

It doesn't boot and gives following message on console screen.

GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:0;RCY:0;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:1;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:2;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:3;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:4;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:5;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:6;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:7;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:8;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:9;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:A;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:B;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:C;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:D;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:E;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:F;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:10;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:11;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:12;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:13;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:14;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:15;USB:0;SPI:0;CHK:AA;EMMC:400;NAND:81;SD:0;READ:0;CHK:AA;LOOP:16;USB:0;SPI:0;CHK:AA;

On other hand machine=libretech-cc works great.

What could be the issue?

linux-yocto-meson64 doesn't use linux-yocto

Describe the bug
Because of the naming convention 'linux-yocto-meson64_.bb, I would have expected the 64bit kernel build for meson to conform to the linux-yocto way of doing things.
It turns out the the 32bit version does, but the 64bit version breaks the convention.

Build Context

meta-meson zeus

Expected behaviour
I would have hoped to be able to use the yocto-linux methods for modifying kernel configuration etc

Additional context
I am assuming there is a reason for not inheriting from linux-yocto, but this does not appear to be documented anywhere.
Is there any way we can have a linux-meson64 for custom build and yocto-linux-meson64 for a Yocto compliant build process?

Make usage of amlogic-boot-fip Makefile feature

Simplify bootable binary generate by using the Makefile added in the amlogic-boot-fip repo: LibreELEC/amlogic-boot-fip#3

No ethernet with Mecool M8S PRO+ (Using P212 dts)

I have successfully build and booted an amlogic-image-headless-sd image with the "amlogic-p212" machine on the Mecool M8S PRO+. The guys that are booting libreelec on this device are using the "gxl_p212_2g.dtb" file, thus it stands to reason that the "amlogic-p212" machine type is compatible.

Mainline u-boot was used so I had to erase the first sectors of the mmc as described in the README.

A problem that I encounter with this image is the not functioning ethernet.

I see no kernel errors:

[ 0.810343] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[ 0.815860] meson8b-dwmac c9410000.ethernet: no reset control found
[ 0.827072] meson8b-dwmac c9410000.ethernet: Ring mode enabled
[ 0.832846] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported
[ 0.840260] meson8b-dwmac c9410000.ethernet: Normal descriptors
[ 0.846123] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported
[ 0.853541] meson8b-dwmac c9410000.ethernet: COE Type 2
[ 0.858716] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported
[ 0.865701] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported
[ 0.872116] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[ 123.285420] meson8b-dwmac c9410000.ethernet eth0: device MAC address 1e:84:7b:c8:84:92
[ 123.387653] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW

ethtool reports that there is no link detected even though I have a cable inserted:

    Supported ports: [ TP MII ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
    Supported pause frame use: Symmetric Receive-only
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
    Advertised pause frame use: No
    Advertised auto-negotiation: Yes
    Speed: Unknown!
    Duplex: Unknown! (255)
    Port: MII
    PHYAD: 8
    Transceiver: internal
    Auto-negotiation: on
    Supports Wake-on: ug
    Wake-on: d
    Current message level: 0x0000003f (63)
                           drv probe link timer ifdown ifup
    Link detected: no

I do see a couple of differences when I decompile the "gxl_p212_2g.dtb" file used by libreelec and the dtb file that is generated by my build using the "amlogic-p212" machine:

gxl_p212_2g.dtb:

ethernet@0xc9410000 {
compatible = "amlogic, gxbb-rmii-dwmac";
reg = <0x00000000 0xc9410000 0x00000000 0x00010000 0x00000000 0xc8834540 0x00000000 0x00000008 0x00000000 0xc8834558 0x00000000 0x0000000c>;
interrupts = <0x00000000 0x00000008 0x00000001 0x00000000 0x00000009 0x00000001>;
phy-mode = "rmii";
pinctrl-names = "internal_eth_pins";
pinctrl-0 = <0x0000001e>;
mc_val = <0x00001800>;
resets = <0x00000008 0x00000023>;
reset-names = "ethpower";
interrupt-names = "macirq", "phyirq";
clocks = <0x00000008 0x0000000a>;
clock-names = "ethclk81";
internal_phy = <0x00000001>;
wol = <0x00000000>;
};

amlogic-p212 (meson-glx-s905x-p212.dtb):

ethernet@c9410000 {
compatible = "amlogic,meson-gx-dwmac", "amlogic,meson-gxbb-dwmac", "snps,dwmac";
reg = <0x00000000 0xc9410000 0x00000000 0x00010000 0x00000000 0xc8834540 0x00000000 0x00000004>;
interrupts = <0x00000000 0x00000008 0x00000001>;
interrupt-names = "macirq";
status = "okay";
clocks = <0x0000000b 0x00000024 0x0000000b 0x00000004 0x0000000b 0x0000000f>;
clock-names = "stmmaceth", "clkin0", "clkin1";
phy-mode = "rmii";
phy-handle = <0x0000001b>;
mdio {
#address-cells = <0x00000001>;
#size-cells = <0x00000000>;
compatible = "snps,dwmac-mdio";
phandle = <0x0000001a>;
};
};

The mainline kernel is obviously different from the Amlogic kernel so the problem might not lay here.

If anyone could assist me in getting the ethernet working?

Adding zeus branch

It would be possible to add zeus branch + with compatible change to support zeus release? Thanks.

Add all missing WiFi and BT firmware for boards

Add all missing WiFi and BT firmware for boards and cleanup/update board config with needed firmwares

u-boot-meson-gx build fails for hardkernel-odroidc2

Build Context

meta-meson branch: master
meta-meson change: none
Poky branch: sumo
bitbake command: bitbake amlogic-image-sato
host: docker/stretch

The build
fails within do_deploy of u-boot-meson-gx:
cp: cannot stat '/home/reinhard/Develop/odroid-c2/sumo/build/tmp-glibc/deploy/images/hardkernel-odroidc2/fip//bl31.img': No such file or directory

Some debugging shows that do_deploy_append_hardkernel-odroidc2 does not get called. Instead do_deploy_append_meson-gxbb is used.

I get this fixed with:

diff --git a/conf/machine/hardkernel-odroidc2.conf b/conf/machine/hardkernel-odroidc2.conf
index 26172b9..17941c3 100644
--- a/conf/machine/hardkernel-odroidc2.conf
+++ b/conf/machine/hardkernel-odroidc2.conf
@@ -1,6 +1,11 @@
 # Hardkernel Odroid-C2 Configurations
 
-require conf/machine/include/amlogic-s905.inc
+# require conf/machine/include/amlogic-s905.inc
+
+require conf/machine/include/amlogic-meson64.inc
+
+MACHINE_FEATURES = "serial usbhost sdio screen wifi"
+
 require conf/machine/include/hardkernel-odroidc2-dtb.inc
 
 KERNEL_IMAGETYPE = "Image"

The resulting image boots successfully into GUI from sdcard.

Usb and Sound for S912

Hi.
I'm not much change the your patches (to support USB S912 and sound all S905X\S912) and added a new fee (s96 vega group s912). Added a script for wic, which collects the image to the external media with the specific launch with the use of universal multi-boot. If you're interested, it's all to be in my last commits on branches master and pyro. By the way, for some reason I can't create a request to merge in your GIT. You lock this or am I doing something wrong ?

topic/mesa-lima kernel hdmi issues

First off: I'm very excited to see the topic/mesa-lima effort!!

It builds fine, but I haven't been able to see anything. I tried two different HDMI devices and both failed. The first is a Vizio D32x-D1 TV, and the second is a Waveshare 1024x600 touchscreen USB Rev2.1.

With the Vizio: the 4 penguins show up on the monitor, but no text (i.e. there is no "Please wait, booting..."). As the kernel is booting, there is a long pause, then an error. It never gets to a prompt.

...snip...
[    2.066715] meson-drm d0100000.vpu: Queued 2 outputs on vpu
[    2.066888] meson-drm d0100000.vpu: Failed to create debugfs directory
[    2.073140] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.079673] [drm] No driver support for vblank timestamp query.
[    2.085590] meson-drm d0100000.vpu: CVBS Output connector not available
[    2.117812] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[    2.122212] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[    2.130023] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops)
[    2.454339] Console: switching to colour frame buffer device 240x67
[    2.487089] meson-drm d0100000.vpu: fb0:  frame buffer device
[   23.521770] INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 1-... } 5258 jiffies s: 9 root: 0x2/.
[   23.526101] blocking rcu_node structures:
[   23.530069] Task dump for CPU 1:
[   23.533256] irq/32-dw_hdmi_ R  running task        0   104      2 0x00000000
[   23.540247] Call trace:
[   23.542670]  __switch_to+0x94/0xd8
[   23.546031]  __dw_hdmi_setup_rx_sense+0x28/0x98
[   23.550512]  dw_hdmi_setup_rx_sense+0x10/0x18
[   23.554825]  dw_hdmi_top_thread_irq+0x2c/0x50
[   23.559137]  irq_thread_fn+0x28/0x68
[   23.562672]  irq_thread+0x10c/0x1a0
[   23.566126]  kthread+0x128/0x130
[   23.569309]  ret_from_fork+0x10/0x18

With the Waveshare, it's as though the device doesn't see it at all. It boots just fine all the way up to the prompt, but nothing ever comes up on the screen, and the X server fails to run, saying no screens can be found.

Build info:

Build Configuration:
BB_VERSION           = "1.37.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "opensuse-42.3"
TARGET_SYS           = "aarch64-oe-linux"
MACHINE              = "hardkernel-odroidc2"
DISTRO               = "nodistro"
DISTRO_VERSION       = "nodistro.0"
TUNE_FEATURES        = "aarch64"
TARGET_FPU           = ""
meta-meson           = "topic/mesa-lima:8175b9906adbce166e36d47cb01a542a741f9013"
meta                 = "master:1f53140528d79c38d4f3a82cd0a03bd0ddc87275"
meta-oe              = "master:f0a664f2b7ac42fa8832ecc016ddf8b6260ee50e"

QT5 toolchain fails to compile

Describe the bug
I'm trying to compile libretech-cc with QT5 SDK toolchain. At first, I thought it's meta-qt5 bug but exact same config works on Raspberrypi3-64 machine. Specifically selected Rpi3-64 because it is same A53 and 64bit.

Build Context
/home/dsh/amlogic/poky/meta
/home/dsh/amlogic/poky/meta-poky
/home/dsh/amlogic/poky/meta-yocto-bsp
/home/dsh/amlogic/meta-meson
/home/dsh/amlogic/meta-openembedded/meta-oe
/home/dsh/amlogic/meta-qt5 \

Expected behavior
bitbake meta-toolchain-qt5 should work.

System (please complete the following information):

Host OS: Ubuntu
Version 18.04
Architecture x86-64
Additional context

While compiling with libretech-cc bitbake show this:

TARGET_SYS           = "aarch64-poky-linux"
MACHINE              = "libretech-cc-custom"
DISTRO               = "poky"
DISTRO_VERSION       = "1.0"
TUNE_FEATURES        = "aarch64"
TARGET_FPU           = ""

while RaspberryPi3-64 show this

TARGET_SYS           = "aarch64-poky-linux"
MACHINE              = "raspberrypi3-64"
DISTRO               = "poky"
DISTRO_VERSION       = "1.0"
TUNE_FEATURES        = "aarch64 cortexa53 crc"
TARGET_FPU           = ""

Is it because some TUNE_FEATURES missing?
Full log Amlogic failing on QtScripts
Full log RaspberryPi3 compiling successfully on QtScripts

Output files to single file

Hello,

I have just compiled my first OE for nexbox_a95x_s905x which results in the below files.

There is no single flashable image.

I understand the dtb is a hardware file, the ext4 is a mapped filesystem but not sure if this includes boot info. There is a separate boot image.

The flashing script for my device requires a single image file. Is there a tool I can use to construct an img from the below files.

Thank you,

FILES:
aml_autoscript
amlogic-image-headless-sd-nexbox-a95x-s905x-20180608105022.rootfs.ext4
amlogic-image-headless-sd-nexbox-a95x-s905x-20180608105022.rootfs.manifest
amlogic-image-headless-sd-nexbox-a95x-s905x-20180608105022.rootfs.tar.bz2
amlogic-image-headless-sd-nexbox-a95x-s905x-20180608105022.testdata.json
amlogic-image-headless-sd-nexbox-a95x-s905x.ext4
amlogic-image-headless-sd-nexbox-a95x-s905x.manifest
amlogic-image-headless-sd-nexbox-a95x-s905x.tar.bz2
amlogic-image-headless-sd-nexbox-a95x-s905x.testdata.json
Image--4.16.5+git0+e5ce9f6879-r0-meson-gxl-s905x-nexbox-a95x-20180608105022.dtb
Image-meson-gxl-s905x-nexbox-a95x.dtb
meson-gxl-s905x-nexbox-a95x.dtb
modules--4.16.5+git0+e5ce9f6879-r0-nexbox-a95x-s905x-20180608105022.tgz
modules-nexbox-a95x-s905x.tgz
uImage
uImage--4.16.5+git0+e5ce9f6879-r0-nexbox-a95x-s905x-20180608105022.bin
uImage-nexbox-a95x-s905x.bin

Cant compile. Stuck on do.rootfs

Describe the bug

NOTE: Executing RunQueue Tasks
WARNING: amlogic-image-sato-1.0-r0 do_rootfs: busybox.postinst returned 1, marki ng as unpacked only, configuration required on target.
WARNING: amlogic-image-sato-1.0-r0 do_rootfs: Intentionally failing postinstall scriptlets of ['busybox'] to defer them to first boot is deprecated. Please plac e them into pkg_postinst_ontarget_${PN} ().
If deferring to first boot wasn't the intent, then scriptlet failure may mean an issue in the recipe, or a regression elsewhere.
Details of the failure are in /home/ffnull/amlogic-bsp/build/tmp-glibc/work/frie ndlyelec_nanopik2-oe-linux/amlogic-image-sato/1.0-r0/temp/log.do_rootfs.
WARNING: amlogic-image-sato-1.0-r0 do_rootfs: busybox.postinst returned 1, marki ng as unpacked only, configuration required on target.
WARNING: amlogic-image-sato-1.0-r0 do_rootfs: Intentionally failing postinstall scriptlets of ['busybox'] to defer them to first boot is deprecated. Please plac e them into pkg_postinst_ontarget_${PN} ().
If deferring to first boot wasn't the intent, then scriptlet failure may mean an issue in the recipe, or a regression elsewhere.
Details of the failure are in /home/ffnull/amlogic-bsp/build/tmp-glibc/work/frie ndlyelec_nanopik2-oe-linux/amlogic-image-sato/1.0-r0/temp/log.do_rootfs.
WARNING: amlogic-image-sato-1.0-r0 do_rootfs: [log_check] amlogic-image-sato: fo und 2 warning messages in the logfile:
[log_check] WARNING: Intentionally failing postinstall scriptlets of ['busybox'] to defer them to first boot is deprecated. Please place them into pkg_postinst_ ontarget_${PN} ().
[log_check] WARNING: Intentionally failing postinstall scriptlets of ['busybox'] to defer them to first boot is deprecated. Please place them into pkg_postinst_ ontarget_${PN} ().

update-alternatives: Error: not linking /home/ffnull/amlogic-bsp/build/tmp-glibc/work/friendlyelec_nanopik2-oe-linux/amlogic-image-sato/1.0-r0/rootfs/sbin/klogd to /bin/busybox.nosuid since /home/ffnull/amlogic-bsp/build/tmp-glibc/work/friendlyelec_nanopik2-oe-linux/amlogic-image-sato/1.0-r0/rootfs/sbin/klogd exists and is not a link

Build Context

meta-meson branch
amlogic-image-sato
meta-meson changes
no
Yocto Project Poky / oe-core branch
sumo
other layers enabled in bblayers and their priorities
no
local.conf changes
no
bitbake command
bitbake amlogic-image-sato

Expected behavior
A clear and concise description of what you expected to happen.

System (please complete the following information):

Host OS: VBOX Ubuntu 16.04 X64

wifi-fw-2016-08-18-5f5fae7239 fetch failure

Describe the bug
wifi-fw-2016-08-18-5f5fae7239 build fails when fetching the tarball file:

ERROR: wifi-fw-2016-08-18-5f5fae7239-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export SSH_AUTH_SOCK="/ssh-agent"; export PATH="/workdir/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/workdir/poky/scripts:/workdir/build/tmp/work/aarch64-poky-linux/wifi-fw/2016-08-18-5f5fae7239-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/workdir/build/tmp/work/aarch64-poky-linux/wifi-fw/2016-08-18-5f5fae7239-r0/recipe-sysroot/usr/bin/crossscripts:/workdir/build/tmp/work/aarch64-poky-linux/wifi-fw/2016-08-18-5f5fae7239-r0/recipe-sysroot-native/usr/sbin:/workdir/build/tmp/work/aarch64-poky-linux/wifi-fw/2016-08-18-5f5fae7239-r0/recipe-sysroot-native/usr/bin:/workdir/build/tmp/work/aarch64-poky-linux/wifi-fw/2016-08-18-5f5fae7239-r0/recipe-sysroot-native/sbin:/workdir/build/tmp/work/aarch64-poky-linux/wifi-fw/2016-08-18-5f5fae7239-r0/recipe-sysroot-native/bin:/workdir/poky/bitbake/bin:/workdir/build/tmp/hosttools"; export HOME="/home/pokyuser"; /usr/bin/env wget -t 2 -T 30 --passive-ftp --no-check-certificate -P /workdir/build/downloads 'http://openlinux.amlogic.com:8000/download/ARM/wifi/wifi-fw-2016-08-18-5f5fae7239.tar.gz' --progress=dot -v failed with exit code 8, output:
--2020-05-29 16:31:43--  http://openlinux.amlogic.com:8000/download/ARM/wifi/wifi-fw-2016-08-18-5f5fae7239.tar.gz
Resolving openlinux.amlogic.com (openlinux.amlogic.com)... 120.25.202.108
Connecting to openlinux.amlogic.com (openlinux.amlogic.com)|120.25.202.108|:8000... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-05-29 16:31:46 ERROR 404: Not Found.

So, repo http://openlinux.amlogic.com:8000/download/ARM no longer exits.

I was trying to find wifi-fw-2016-08-18-5f5fae7239.tar.gz file but I couldn't find it so, I was looking for the files the recipe was trying to install and I end up looking in this 3 repos:

https://github.com/armbian/firmware
https://github.com/hardkernel/buildroot_platform_hardware_amlogic_wifi.git
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

And here the files matching the names on the recipe:

file: fw_bcm4356a2_ag.bin
- efc2555f3792101082a51714be4b4ba4 ./armbian-firmware/rkwifi/fw_bcm4356a2_ag.bin
- 1e7dcba997e5dc1d9970f9586eb85dfe ./buildroot_platform_hardware_amlogic_wifi/bcm_ampak/config/4356/fw_bcm4356a2_ag.bin
file: fw_bcm4356a2_ag.bin renamed to: brcmfmac4356-sdio.bin:
- ca63a118d10e69d0f84d8e06bbbe9d4f ./armbian-firmware/brcm/brcmfmac4356-sdio.bin
- 57853b6ac141f6d8d5774206436d9c55 ./linux-firmware/brcm/brcmfmac4356-sdio.bin
file: nvram_ap6356.txt:
- bd37ec8da4d46816aba85d018dbbbec8 ./armbian-firmware/rkwifi/nvram_ap6356.txt
- b7a7e2d284c5284d8f7e266cbdff5480 ./buildroot_platform_hardware_amlogic_wifi/bcm_ampak/config/4356/nvram_ap6356.txt
file: nvram_ap6356.txt renamed to: brcmfmac4356-sdio.txt:
- 046a0d584bab0d2f774ba9f722a175f9 ./armbian-firmware/brcm/brcmfmac4356-sdio.txt
file: nvram_ap6354.txt:
- 53c14427b50297acd443bb59a9b1769b ./armbian-firmware/rkwifi/nvram_ap6354.txt
- 714f7a3796eca86f41cdf8b5216a475a ./buildroot_platform_hardware_amlogic_wifi/bcm_ampak/config/4354/nvram_ap6354.txt
file: nvram_ap6354.txt renamed to: brcmfmac4354-sdio.txt
- not found

Build Context

meta-meson zeus, master
Recipe is the same in both branches.

Expected behavior
Fetch with no failure.

Additional context
Do you have the tarball so we can upload it to the recipe ./recipes-firmware/wifi-fw/wifi-fw/<files> or somewhere else?
If not, is any of the files listed above the right ones?

Thanks!

python2 support on OE master

python2 support has been removed from upstream OE/YP master and moved to a separate layer (https://git.openembedded.org/meta-python2). The fip things required to put u-boot-meson-gx together (I'm using libretech-cc) are python2 .pyc bytecode. It would appear that someone has un-compiled the bytecode to a regular python script here: https://github.com/repk/gxlimg If that could run under python3, or if the fip things could be recompiled to be python3 bytecode, then meta-meson would not need to depend on meta-python2.

Now, in order to successfully build libretech-cc on master, one needs:

meta-meson (master5b1df5111a27bec3a09bfcf5e2948d5320d6e133, plus the two fixes here: #77)
openembedded-core (master:44a4ac2294da0f53cbbfabc7ece836fe97f4d3f7)
meta-python2 (master:ac385337b357ace532bbdf24fc4ff09e7b29f4b6)
meta-openembedded/meta-oe (master:611b0c707aa889b1b3880687334b6dd0fd69479b) (this is a dependency of meta-python2)

MESA-LOADER: failed to open meson
Failed to load driver: meson

Get rid of u-boot-meson-gx and extend the u-boot recipe

Get rid of u-boot-meson-gx and extend the u-boot recipe since upstream u-boot is stable now and needs no changes

superna9999 / meta-meson Goto Github PK

meta-meson's Introduction

Upstream Linux Amlogic Meson Yocto/Openembedded Layer

Build Setup

Selecting Machine to build for

Selecting Image type

Building example

Build with kas

meta-meson's People

Contributors

Stargazers

Watchers

Forkers

meta-meson's Issues

Error Summary

Recommend Projects

Recommend Topics

Recommend Org