Giter Site home page Giter Site logo

edm-yocto-bsp's Introduction

TechNexion Yocto 2.4 rocko 4.9.y GA BSP

This BSP is a TechNexion release providing support NXP i.mx series processors

$: mkdir ~/bin
$: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$: chmod a+x ~/bin/repo

Download the BSP source:

For NXP i.mx8mq SOC, e.g.,PICO-IMX8M:

$: PATH=${PATH}:~/bin
$: mkdir edm_yocto
$: cd edm_yocto
$: repo init -u https://github.com/TechNexion/edm-yocto-bsp.git -b rocko_4.9.y_GA -m imx-4.9.88-2.0.0_ga.xml
$: repo sync -j8

Create build environment

Method 1:

Set up build environment on host PC:

Our build environment is under ubuntu 16.04.

Install required packages:

$: sudo apt-get install gawk wget git git-core diffstat unzip texinfo gcc-multilib build-essential \
chrpath socat cpio python python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm \
language-pack-en coreutils texi2html file docbook-utils \
python-pysqlite2 help2man desktop-file-utils \
libgl1-mesa-dev libglu1-mesa-dev mercurial autoconf automake \
groff curl lzop asciidoc u-boot-tools libreoffice-writer \
sshpass ssh-askpass zip xz-utils kpartx vim screen

Method 2:

Download virtual machine with pre-installed Ubuntu 16.04 and packages.

ftp://ftp.technexion.net/development_resources/development_tools/vm

This virtual machine is validated to build Yocto 2.4.

Method 3:

Use the dockerfile to setup the build environment:

After fetch yocto source code, create a docker image from a dockerfile.

$: cd sources/meta-edm-bsp-release/tools/container
$: docker build -t tn_ubuntu1604 .
$: docker run -it -u jenkins -v ${directory_in_host_machine}:${directory_in_docker} tn_ubuntu1604 /bin/bash
(-v: use to bind volume to the directory in host machine)
(password: jenkins)

Prepare WIFI/BT firmware

There are two kinds of WLAN module on TechNexion boards. One is Broadcom(BRCM) WLAN(includes BCM4330/BCM4339(AP6335)/BCM43438(AP6212)), the other is Qualcomm(QCA) WLAN(includes QCA9377-5/QCA6174). Because of the license restriction, please contact TechNexion FAE or Sales to get licensed firmware files.

For QCA WLAN and BT: qca9377-3_qca6174-3_firmware_20191128.zip

After getting the firmware binary: .. Decompress the tarball and put all the firmware files into sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/files.

The directory sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/files is the place to put WIFI/BT firmware files.

  1. Add firmware package in Yocto build: Add argument "WIFI_FIRMWARE=y" in build instruction. Please refer to following explanation.

Configurations for setup script

“MACHINE” is the target of build. It usually corresponds to the name of SOM or SBC.

For more information, please check the file under “sources/meta-edm-bsp-release/conf/machine”.

“-b” specify the build directory.

“DISPLAY” is the disply type. This option only works on i.mx6 (i.mx6 Solo/Dual Lite/Dual/Quad) SOMs and doesn’t work for i.mx6ul, i.mx6sx and i.mx7.

“BASEBOARD” is the baseboard type.

“WIFI_MODULE” is to choose what kind of WLAN is on board. (qca/brcm/ath-pci)

“WIFI_FIRMWARE” is to choose to add WLAN firmware files in target rootfs or not. (y/all)

Table 1. Build configurations for supported hardware
Parameter Available options Description

MACHINE

pico-imx8m

Compatible with TechNexion PICO-IMX8M (i.MX8M Quad)

pico-imx6

Compatible with TechNexion PICO-IMX6 (i.MX6 Solo/DL/Dual/Quad)

pico-imx7

Compatible with TechNexion PICO-IMX7

pico-imx6ul

Compatible with TechNexion PICO-IMX6UL/ULL

edm-imx6

Compatible with TechNexion EDM-IMX6 (i.MX6 Solo/DL/Dual/Quad/Quad Plus)

edm-imx7

Compatible with TechNexion EDM-IMX7

tep1-imx7

Compatible with TechNexion TEP-0500-IMX7/TEP-0700-IMX7

tep1-imx6ul

Compatible with TechNexion TEP-0500-IMX6UL/TEP-0700-IMX6UL

tek-imx6

Compatible with TechNexion TEK3-IMX6/TEP-1010-IMX6/TEP-1560-IMX6/TWP-1010-IMX6/TWP-1560-IMX6 (i.MX6 Solo/DL/Dual/Quad/Quad Plus)

tek3-imx6ul

Compatible with TechNexion TEK3-IMX6UL

DISTRO

fsl-imx-x11

Only X11 graphics. X11 graphics are not supported on i.MX8.

fsl-imx-wayland

Wayland weston graphics

fsl-imx-xwayland

Wayland graphics and X11. X11 applications using EGL are not supported

fsl-imx-fb

Frame Buffer graphics - no X11 or Wayland. Frame Buffer is not supported on i.MX8.

BASEBOARD

(It specifies the 'baseboard' variable in uEnv.txt)

pi, nymph, dwarf, hobbit

Compatible with TechNexion PICO-IMX6 (i.MX6 Solo/DL/Quad/UL/ULL).

gnome, fairy, tc0700, tc1000

Compatible with TechNexion EDM-IMX6 (i.MX6 Solo/DL/Dual/Quad/Quad Plus). (EDM-IMX7D only support gnome)

WIFI_MODULE

(It specifies the 'wifi_module' variable in uEnv.txt)

'qca', 'brcm', 'ath-pci'

Choose what kind of WLAN is on board.

WIFI_FIRMWARE

'y' or 'all'

'y' option depends on 'WIFI_MODULE'. If you specify 'WIFI_MODULE' as 'qca'. Then, it only add 'qca' firmware package in yocto build. 'all' option will add both 'qca', 'brcm' and 'ath-pci' firmware package in yocto build. Please refer to section "Prepare WIFI/BT firmware" to ensure you already put firmware files in the right place.

DISPLAY

(Parameter "DISPLAY" only works on i.mx6/i.mx8m) (It specifies the 'displayinfo' variable in uEnv.txt)

lvds7

(i.mx6) 7 inch 1024x600 LVDS panel

lvds10

(i.mx6) 10 inch 1280x800 LVDS panel

lvds15

(i.mx6) 15 inch 1366x768 LVDS panel

hdmi720p

(i.mx6) 1280x720 HDMI

hdmi1080p

(i.mx6) 1920x1080 HDMI

lcd

(i.mx6) 5 inch/7 inch 800x480 TTL parallel LCD panel

lvds7_hdmi720p

(i.mx6) Dual display output to both 7 inch LVDS and HDMI

custom

(i.mx6) Reserved for custom panel

mipi5

(i.mx8m) MIPI-DSI 5 inch panel(with ILI9881 controller)

hdmi

(i.mx8m) HDMI monitor (the resolution is decided by EDID)

-b

<build dir>

Assign the name of build directory

Table 2. Choosing Yocto target image
Image name Target

core-image-minimal

A small image that only allows a device to boot

core-image-base

A console-only image that fully supports the target device hardware

core-image-sato

An image with Sato, a mobile environment and visual style for mobile devices. The image supports X11 with a Sato theme, Pimlico applications. It contains a terminal, an editor and a file manager

fsl-image-machine-test

An FSL Community i.MX core image with console environment - no GUI interface

fsl-image-validation-imx

Builds an i.MX image with a GUI without any Qt content.

fsl-image-qt5-validation-imx

Builds an opensource Qt 5 image. These images are only supported for i.MX SoC with hardware graphics. They are not supported on the i.MX 6UltraLite, i.MX 6UltraLiteLite, and i.MX 7Dual.

Build Yocto for TechNexion target platform

Please don’t add argument 'WIFI_FIRMWARE=y' if you don’t put firmware files in "sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/files" . It would result in build failure. Please refer to section "Prepare WIFI/BT firmware".

For PICO-IMX8M

Wayland image for HDMI monitor:

$: DISPLAY=hdmi WIFI_FIRMWARE=y DISTRO=fsl-imx-wayland MACHINE=pico-imx8m source edm-setup-release.sh -b build-wayland
$: bitbake fsl-image-qt5-validation-imx

Wayland image for MIPI-DSI 5-inch panel:

$: DISPLAY=mipi5 WIFI_FIRMWARE=y DISTRO=fsl-imx-wayland MACHINE=pico-imx8m source edm-setup-release.sh -b build-wayland
$: bitbake fsl-image-qt5-validation-imx

DISTRO: DISTRO can be replaced to "fsl-imx-xwayland"

For PICO-IMX6

PI baseboard, QT5 with X11 image for HDMI output:

For PICO-IMX6 with QCA WLAN:
$: WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=pico-imx6 BASEBOARD=pi source edm-setup-release.sh -b build-x11-pico-imx6
For PICO-IMX6 with BRCM WLAN:
$: WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-x11 MACHINE=pico-imx6 BASEBOARD=pi source edm-setup-release.sh -b build-x11-pico-imx6
$: bitbake fsl-image-qt5-validation-imx

NYMPH baseboard, QT5 with X11 image for 7 inch LVDS panel:

For PICO-IMX6 with QCA WLAN:
$: DISPLAY=lvds7 WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=pico-imx6 BASEBOARD=nymph source edm-setup-release.sh -b build-x11-pico-imx6
For PICO-IMX6 with BRCM WLAN:
$: DISPLAY=lvds7 WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-x11 MACHINE=pico-imx6 BASEBOARD=nymph source edm-setup-release.sh -b build-x11-pico-imx6
$: bitbake fsl-image-qt5-validation-imx

For PICO-IMX7

PI baseboard, QT5 with X11 image for 7 inch/5 inch TTL-LCD panel:

For PICO-IMX7 with QCA WLAN:
$: WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=pico-imx7 BASEBOARD=pi source edm-setup-release.sh -b build-x11-pico-imx7
For PICO-IMX7 with BRCM WLAN:
$: WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-x11 MACHINE=pico-imx7 BASEBOARD=pi source edm-setup-release.sh -b build-x11-pico-imx7
$: bitbake fsl-image-qt5-validation-imx

For PICO-IMX6UL/ULL

PI baseboard, QT5 with X11 image for HDMI output:

For PICO-IMX6UL/ULL with QCA WLAN:
$: WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=pico-imx6ul BASEBOARD=pi source edm-setup-release.sh -b build-x11-pico-imx6ul
For PICO-IMX6UL/ULL with BRCM WLAN:
$: WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-x11 MACHINE=pico-imx6ul BASEBOARD=pi source edm-setup-release.sh -b build-x11-pico-imx6ul
$: bitbake fsl-image-qt5-validation-imx

NYMPH baseboard, QT5 with X11 image for 7 inch LVDS panel:

For PICO-IMX6UL/ULL with QCA WLAN:
$: DISPLAY=lvds7 WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=pico-imx6ul BASEBOARD=nymph source edm-setup-release.sh -b build-x11-pico-imx6ul
For PICO-IMX6UL/ULL with BRCM WLAN:
$: DISPLAY=lvds7 WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-x11 MACHINE=pico-imx6ul BASEBOARD=nymph source edm-setup-release.sh -b build-x11-pico-imx6ul
$: bitbake fsl-image-qt5-validation-imx

For EDM-IMX6

GNOME baseboard, QT5 with X11 image for 7 inch/5 inch TTL-LCD panel:

For EDM-IMX6 with QCA WLAN:
$: WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=gnome source edm-setup-release.sh -b build-x11-edm-imx6
For EDM-IMX6 with BRCM WLAN:
$: WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=gnome source edm-setup-release.sh -b build-x11-edm-imx6
$: bitbake fsl-image-qt5-validation-imx

FAIRY baseboard, QT5 with X11 image for 7 inch LVDS panel:

For EDM-IMX6 with QCA WLAN:
$: DISPLAY=lvds7 WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=fairy source edm-setup-release.sh -b build-x11-edm-imx6
For EDM-IMX6 with BRCM WLAN:
$: DISPLAY=lvds7 WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=fairy source edm-setup-release.sh -b build-x11-edm-imx6
$: bitbake fsl-image-qt5-validation-imx

TC0700 baseboard, QT5 with X11 image for 7 inch LVDS panel:

For EDM-IMX6 with QCA WLAN:
$: DISPLAY=lvds7 WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=tc0700 source edm-setup-release.sh -b build-x11-edm-imx6
For EDM-IMX6 with BRCM WLAN:
$: DISPLAY=lvds7 WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=tc0700 source edm-setup-release.sh -b build-x11-edm-imx6
$: bitbake fsl-image-qt5-validation-imx

TC1000 baseboard, QT5 with X11 image for 10 inch LVDS panel:

For EDM-IMX6 with QCA WLAN:
$: DISPLAY=lvds10 WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=tc1000 source edm-setup-release.sh -b build-x11-edm-imx6
For EDM-IMX6 with BRCM WLAN:
$: DISPLAY=lvds10 WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=tc1000 source edm-setup-release.sh -b build-x11-edm-imx6
$: bitbake fsl-image-qt5-validation-imx

For EDM-IMX7

GNOME baseboard, QT5 with X11 image for 7 inch/5 inch TTL-LCD panel:

For EDM-IMX7 with QCA WLAN:
$: WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=edm-imx7 BASEBOARD=gnome source edm-setup-release.sh -b build-x11-edm-imx7
$: bitbake fsl-image-qt5-validation-imx

For TEP-0500-IMX7/TEP-0700-IMX7

TEP-0500-IMX7/TEP-0700-IMX7, QT5 with X11 image:

For TEP1-IMX7 with PCIE WLAN:
$: WIFI_FIRMWARE=y WIFI_MODULE=ath-pci DISTRO=fsl-imx-x11 MACHINE=tep1-imx7 source edm-setup-release.sh -b build-x11-tep1-imx7
$: bitbake fsl-image-qt5-validation-imx

For TEP-0500-IMX6UL/TEP-0700-IMX6UL

TEP-0500-IMX6UL/TEP-0700-IMX6UL, QT5 with X11 image:

$: DISTRO=fsl-imx-x11 MACHINE=tep1-imx6ul source edm-setup-release.sh -b build-x11-tep1-imx6ul
$: bitbake fsl-image-qt5-validation-imx

For TEK3-IMX6

TEK3-IMX6 BOX PC, QT5 with X11 image for HDMI output:

For TEK3-IMX6 with PCIE WLAN:
$:  WIFI_FIRMWARE=y WIFI_MODULE=ath-pci DISTRO=fsl-imx-x11 MACHINE=tek-imx6 source edm-setup-release.sh -b build-x11-tek-imx6
$: bitbake fsl-image-qt5-validation-imx

For TEP-1010-IMX6/TEP-1560-IMX6/TWP-1010-IMX6/TWP-1560-IMX6

TEP-1010-IMX6/TWP-1010-IMX6, QT5 with X11 image:

For TEP-1010-IMX6/TWP-1010-IMX6 with PCIE WLAN:
$:  DISPLAY=lvds10 WIFI_FIRMWARE=y WIFI_MODULE=ath-pci DISTRO=fsl-imx-x11 MACHINE=tek-imx6 source edm-setup-release.sh -b build-x11-tek-imx6
$: bitbake fsl-image-qt5-validation-imx

TEP-1560-IMX6/TWP-1560-IMX6, QT5 with X11 image:

For TEP-1560-IMX6/TWP-1560-IMX6 with PCIE WLAN:
$:  DISPLAY=lvds15 WIFI_FIRMWARE=y WIFI_MODULE=ath-pci DISTRO=fsl-imx-x11 MACHINE=tek-imx6 source edm-setup-release.sh -b build-x11-tek-imx6
$: bitbake fsl-image-qt5-validation-imx

For TEK3-IMX6UL

TEK3-IMX6UL, QT5 with X11 image:

$: DISTRO=fsl-imx-x11 MACHINE=tek3-imx6ul source edm-setup-release.sh -b build-x11-tek3-imx6ul
$: bitbake fsl-image-qt5-validation-imx

QTWebkit

To start to go to /usr/share/qt5/examples/webkitwidgets/browser and run browser

Qt

Note that Qt has both a commercial and open source license options. Make the decision about which license to use before starting work on custom Qt applications. Once custom Qt applications are started with an open source Qt license the work can not be used with a commercial Qt license. Work with a legal representative to understand the differences between each license. Default builds use an open source Qt license.

Note Qt is not supported on i.MX 6UltraLite and i.MX 7Dual. It works on X11 backend only but is not a supported feature.

Image Deployment

When build completes, the generated release image is under “${BUILD-TYPE}/tmp/deploy/images/${MACHINE}”: $: bzip2 -fd fsl-image-XXX.rootfs.sdcard.bz2 "fsl-image-XXX.rootfs.sdcard"

If the i.mx8m module is only with eMMC, please use following tool to flash image into eMMC. Please set boot jumper to boot from serial download mode, then this tool will mount eMMC as USB mass storage:

Please follow the userguide below to flash the image into your target board to deploy yocto.

MFG tool: (can be excuted under both MS Windows and Linux)

PICO-IMX8M(1GB/2GB/3GB/4GB DRAM):

ftp://ftp.technexion.net/development_resources/development_tools/installer/

edm-yocto-bsp's People

Contributors

po-cheng-technexion avatar ray-chang avatar richard-hu avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

edm-yocto-bsp's Issues

Password for VMs

Hi
Please provide the password for virtual machine ubuntu 16.4.

tool chain not generated in build-x11-pico/tmp/deploy/sdk

Hi
I am not getting tool chain file for pico-imx6 (at build-x11-pico/tmp/deploy/sdk) ie,
poky-glibc-x86_64-meta-toolchain-cortexa9hf-vfp-neon-toolchain-1.7.sh

Instead fsl-imx-x11-glibc-x86_64-meta-toolchain-cortexa9hf-vfp-neon-toolchain-4.1.15-1.2.0.sh is available.

Bit bake commands

  1. For yocto build
    DISPLAY=lvds7 MACHINE=pico-imx6 BASEBOARD=nymph source edm-setup-release.sh
    -b build-x11-pico -e x11
    bitbake fsl-image-qt5

  2. For toolchain build
    bitbake meta-toolchain

Please tell me what is the issue. I am using ubuntu 16.04

Cross Compilation Issue

Hi
I am using your toolchain 4.1.15-1.2.0 for imx6.
while compiling gpsd (gps daemon) using this toolchain i am getting error :

sysroots/pico-imx6/usr/include/gnu/stubs.h:7:29: fatal error: gnu/stubs-soft.h: No such file or directory
compilation terminated.
scons: *** [ais_json.os] Error 1
scons: building terminated because of errors.

Below is complete log of it.

arm-poky-linux-gnueabi-gcc -o ais_json.os -c -O2 -pipe -g -feliminate-unused-debug-types --sysroot=/media/zahab/Linux_1/Navtool/OS/tn_imx_yocto-2.0-jethro_qt5_source_20161209/yocto_jethro_4.1.15-1.1.0_GA_20161209/build-x11-pico/tmp/sysroots/pico-imx6/ -pthread -Wextra -Wall -Wno-uninitialized -Wno-missing-field-initializers -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wpointer-arith -Wreturn-type -O2 -fPIC ais_json.c
In file included from /media/zahab/Linux_1/Navtool/OS/tn_imx_yocto-2.0-jethro_qt5_source_20161209/yocto_jethro_4.1.15-1.1.0_GA_20161209/build-x11-pico/tmp/sysroots/pico-imx6/usr/include/features.h:389:0,
from /media/zahab/Linux_1/Navtool/OS/tn_imx_yocto-2.0-jethro_qt5_source_20161209/yocto_jethro_4.1.15-1.1.0_GA_20161209/build-x11-pico/tmp/sysroots/pico-imx6/usr/include/stdio.h:27,
from ais_json.c:12:
/media/zahab/Linux_1/Navtool/OS/tn_imx_yocto-2.0-jethro_qt5_source_20161209/yocto_jethro_4.1.15-1.1.0_GA_20161209/build-x11-pico/tmp/sysroots/pico-imx6/usr/include/gnu/stubs.h:7:29: fatal error: : No such file or directory
compilation terminated.
scons: *** [ais_json.os] Error 1
scons: building terminated because of errors.

Yocto 2.5

Hello Richard

Is a release done with Yocto 2.5 ?
We want to move to QT5.12 and Yocto 2.4 is linked to QT5.9

Thanks

Compiler segmentation fault error

Hi
I am getting below while building tn_imx_yocto-2.0-jethro_qt5_source_20161209.zip

insn-opinit.c: In function 'void init_all_optabs(target_optabs*)':
insn-opinit.c:764:1: internal compiler error: Segmentation fault
init_all_optabs (struct target_optabs *optabs)

I was able to build it earlier.

log.do_compile.24363.zip

pico-imx6ul support - wifi driver error only if connman is installed

I made a layer and some recipes to:

  1. install correct WiFi drivers with the module bcmdhd;
  2. boot my board with the correct dtb file imx6ul-pico_pi.dtb;

When I do:

modprobe bcmdhd

This is the output and this is correct:

dhd_module_init in
wifi_plat_dev_drv_probe no GPIO for OOB in device tree.
wifi_plat_dev_drv_probe continue with non-OOB mode.
Power-up adapter 'DHD generic adapter'
wifi_platform_bus_enumerate device present 1
mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
mmc1: new high speed SDIO card at address 0001
F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x0 pkg:0x3
DHD: dongle ram size is set to 524288(orig 524288) at 0x0
wifi_platform_get_mac_addr
fw path is /lib/firmware/brcm/fw_bcm43438a0.bin 
nvram_path is /lib/firmware/brcm/nvram_ap6212.txt 
wl_create_event_handler(): thread:wl_event_handler:107 started
dhd_attach(): thread:dhd_watchdog_thread:108 started
dhd_attach(): thread:dhd_dpc:109 started
dhd_deferred_work_init: work queue initialized 
fw path is /lib/firmware/brcm/fw_bcm43438a0.bin 
nvram_path is /lib/firmware/brcm/nvram_ap6212.txt 
random: crng init done
dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
dhd_bus_init: enable 0x06, ready 0x06 (waited 0us)
wifi_platform_get_mac_addr
Firmware up: op_mode=0x0005, MAC=44:2c:05:be:c7:16
Firmware version = wl0: Nov 25 2016 15:04:47 version 7.46.57.5.apsta.r4.o12 (Station/Softap) FWID 01-b70fff29 es6.c5.n4.a3
dhd_wlfc_init(): successfully enabled bdcv2 tlv signaling, 79
dhd_wlfc_init: query wlfc_mode succeed, fw_caps=0x1c
dhd_wlfc_init(): wlfc_mode=0x1c, ret=0
Dongle Host Driver, version 1.141.100.6 (r)
Compiled in drivers/net/wireless/bcmdhd
Register interface [wlan0]  MAC: 44:2c:05:be:c7:16

The problem is if I add connman or connman-client to my machine, I get:

dhd_module_init in
wifi_plat_dev_drv_probe no GPIO for OOB in device tree.
wifi_plat_dev_drv_probe continue with non-OOB mode.
Power-up adapter 'DHD generic adapter'
wifi_platform_bus_enumerate device present 1
mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
mmc1: new high speed SDIO card at address 0001
F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x0 pkg:0x3
DHD: dongle ram size is set to 524288(orig 524288) at 0x0
wifi_platform_get_mac_addr
fw path is /lib/firmware/brcm/fw_bcm43438a0.bin 
nvram_path is /lib/firmware/brcm/nvram_ap6212.txt 
wl_create_event_handler(): thread:wl_event_handler:115 started
dhd_attach(): thread:dhd_watchdog_thread:117 started
dhd_attach(): thread:dhd_dpc:118 started
dhd_deferred_work_init: work queue initialized 
fw path is /lib/firmware/brcm/fw_bcm43438a0.bin 
nvram_path is /lib/firmware/brcm/nvram_ap6212.txt 
dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
dhd_bus_init: enable 0x06, ready 0x06 (waited 0us)
wifi_platform_get_mac_addr
Firmware up: op_mode=0x0005, MAC=44:2c:05:be:c7:16
Firmware version = wl0: Nov 25 2016 15:04:47 version 7.46.57.5.apsta.r4.o12 (Station/Softap) FWID 01-b70fff29 es6.c5.n4.a3
dhd_wlfc_init(): successfully enabled bdcv2 tlv signaling, 79
dhd_wlfc_init: query wlfc_mode succeed, fw_caps=0x1c
dhd_wlfc_init(): wlfc_mode=0x1c, ret=0
Dongle Host Driver, version 1.141.100.6 (r)
Compiled in drivers/net/wireless/bcmdhd
Register interface [wlan0]  MAC: 44:2c:05:be:c7:16
CFG80211-ERROR) wl_update_wiphybands : error reading vhtmode (-23)

My connman version is:

1.34

I'm able to connect to the WiFi even if I've the error.

What's that error?

UPDATE
This last line seems to be a message from system that is printed in the debug serial console

CFG80211-ERROR) wl_update_wiphybands : error reading vhtmode (-23)

libfm, libfm-extra_1.2.5 build failed

Hi,
I modified .bb recipes according to https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f0ccd96a6434e45bc885c5b6128630c4ad510da8

../edm_yocto/sources/poky/meta/recipes-support/libfm/libfm-extra_1.2.5.bb
DEPENDS and inherit changed to:
DEPENDS = "glib-2.0-native glib-2.0 intltool-native"
inherit autotools pkgconfig gtk-doc gettext

../edm_yocto/sources/poky/meta/recipes-support/libfm/libfm_1.2.5.bb
DEPENDS and inherit changed to:
DEPENDS = "glib-2.0 glib-2.0-native pango gtk+3 menu-cache intltool-native libexif libfm-extra
inherit autotools pkgconfig gtk-doc gettext distro_features_check

With this modification libfm, libfm-extra_1.2.5 build OK.

Miro

php error becouse binutils

Hi,
During adding php to the image i met such error when executing php in device:
root@pico-imx6:~# php
php: relocation error: php: symbol mysql_server_init, version libmysqlclient_16 not defined in file libmysqlclient.so.18 with link time reference

I found solution: http://www.variscite.com/support-forum/viewtopic.php?t=372
Needed new version of binutils
https://github.com/varigit/meta-variscite-imx/blob/Krogoth-imx-4.1.15-var01/recipes-devtools/binutils/binutils-cross_2.26.bbappend
After these path everything works fine. Please consider update in your yocto distribution.
Best regards,
Karol

Sumo 2.5

Is the new BSP sumo 2.5 is compatible with pico-imx6 ?
Thanks

ncurses compile error

When i try to build linux using the exact steps outlined in this guide i get the following error.
ERROR: Task 888 (virtual:native:/home/hatter/edm-yocto/sources/poky/meta/recipes-core/ncurses/ncurses_5.9.bb, do_compile) failed with exit code '1'

hciconfig fails to see wifi/bt module with bcm only drivers

4.9.88-2.0.0 used to compile and support BCM modules. After a recent build, the drivers where present as expected, but hciconfig was not able to communicate with the wifi/bt module.

Configuration script:
WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-fb MACHINE=pico-imx6 BASEBOARD=nymph source edm-setup-release.sh -b build-pico-imx6

local.conf:
MACHINE ??= 'pico-imx6'
DISTRO ?= 'fsl-imx-fb'
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks package-management ssh-server-dropbear"
DISTRO_FEATURES_append += "bluez5 bluetooth wifi systemd journald "
IMAGE_INSTALL_append += "packagegroup-core-buildessential sudo opkg apt connman
wget curl openssl nano git dhcp-client wireless-tools nodejs bluez5
python3 python3-pip python3-setuptools python3-dev python3-modules
kernel-modules iptables wpa-supplicant i2c-tools connman-client cmake swig"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS ??= "
STOPTASKS,${TMPDIR},1G,100K
STOPTASKS,${DL_DIR},1G,100K
STOPTASKS,${SSTATE_DIR},1G,100K
STOPTASKS,/tmp,100M,100K
ABORT,${TMPDIR},100M,1K
ABORT,${DL_DIR},100M,1K
ABORT,${SSTATE_DIR},100M,1K
ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
CONF_VERSION = "1"
BASE_BOARD ?= "nymph"
DISPLAY_INFO ?= "lcd"
RF_FIRMWARES ?= " qca "
MACHINEOVERRIDES =. "${@'' if d.getVar('RF_FIRMWARES', True) is None else '%s:' % ':'.join([fw.lower() for $
XZ_COMPRESSION_LEVEL = "-9"
XZ_INTEGRITY_CHECK = "crc64"

DL_DIR ?= "${BSPDIR}/downloads/"

bitbake:
bitbake core-image-base

Weston not displaying anything

Hi I'm building sumo branch for the pico-imx8m, the compilation (besides some issues with building for the machine I had, for whatever reason) goes fine, but when I try to run the image on the board, everything is just fine up to the moment when weston should kick in.
I'm getting black screen with a cursor in top-left corner and nothing else.
Weston logs show nothing special the process is running, either started with systemd or manually.
I've build both for xwayland and wayland, and the result is the same.
Do you happen to know what is going on?
I had similar situation when I tried to port your rocko branch to sumo, by myself and I thought I messed something up, and put it on the hook until someone (that actually knows what he/she is/are doing ;) ) fix the stuff. But now I'm stuck ...

BR

Audio support on PICO-PI-IMX8M-2G

Audio playback issue on PICO-PI-IMX8M-2G using the linux tn-imx_4.14.98_2.0.0_ga-wip kernel (prebuilt image fsl-image-qt5-validation-imx-pico-imx8mq).

Running some test commands I get the following output:
aplay /usr/shar/sounds/alsa/noise.wav

[ 2992.099490] fsl-sai 30050000.sai: failed to derive required Tx rate: 2822400
[ 2992.106651] fsl-sai 30050000.sai: ASoC: can't set 30050000.sai hw params: -22
ALSA lib ../../../alsa-lib-1.1.5/src/pcm/pcm_direct.c:1271:(snd1_pcm_direct_initialize_slave) unable to install hw params
ALSA lib ../../../alsa-lib-1.1.5/src/pcm/pcm_dmix.c:1111:(snd_pcm_dmix_open) unable to initialize slave
aplay: main:828: audio open error: Invalid argument

I see similar "failed to derive required Tx rate" issues if I try to play an mp4 through gplay-1.0 along with:

====== BEEP: 4.4.5 build on Apr 20 2019 15:58:42. ======
Core: AAC decoder Wrapper build on Dec 7 2017 18:13:51
file: /usr/lib/imx-mm/audio-codec/wrap/lib_aacd_wrap_arm_elinux.so.3
CODEC: BLN_MAD-MMCODECS_AACD_ARM_03.09.00_ARMV8 build on Sep 20 2017 15:02:50.
[ 3104.543472] cma: cma_alloc: alloc failed, req-size: 3544 pages, ret: -12
[ 3104.551425] cma: cma_alloc: alloc failed, req-size: 3544 pages, ret: -12

I will try to setup a build environment to build the latest, but this is using the latest prebuilt image available for download.

Ethernet not working with imx8mq-pico-pi-voicehat.dtb

Hello,

The ethernet connection works fine with the imx8mq-pico-pi.dtb file, however once I switch the dtb to imx8mq-pico-pi-voicehat.dtb , the ethernet connection stops running. I'm not using wifi - didn't install it during the yocto image build procedure.

I assume there is an issue with the dtb. Is there a fix for this issue or any directions what should be checked/fixed to get ethernet running even with the voicehat dtb?

Thank you very much for any kind of help and have a nice day,
Renegade

No pico-imx7d support?

Apparently the pico-imx7d board is not supported , any plan to implement the support for this?

Nothing RPROVIDES 'optee-os-imx' in technexion pico-pi-imx7 board yocto or No device /dev/tee0 ?

hi,
I try to add optee for pico-pi-imx7 board in current yocto version.
I add below lines in local.conf
..
DISTRO_FEATURES_append=" optee"
IMAGE_INSTALL_append = " optee-client-imx optee-os-imx optee-test-imx"
..

but I can not pass bitbake fsl-image-qt5-validation-imx
but I used a old version( a few month ago , I cloned it), It passed bitbake, I can find xtest. only there is no device /dev/tee? after boot

so I want to try the updated yocto source code version, but the error happended! I can find optee-test-imx_git.bb optee-client-imx _git.bb optee-os-imx_git.bb there but why can not bitbake?
I want to know if pico-pi-imx7 board can support optee?

=======================error====================
current (2019/10/10)yocto version error:

error:ERROR: Nothing RPROVIDES 'optee-os-imx' (but /opt/oe/configs/imx7/edm_yocto/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/images/fsl-image-qt5-validation-imx.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'optee-os-imx' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['optee-os-imx']
ERROR: Required build target 'fsl-image-qt5-validation-imx' has no buildable providers.
Missing or unbuildable dependency chain was: ['fsl-image-qt5-validation-imx', 'optee-os-imx']

============my config================
my local.conf:
MACHINE ??= 'pico-imx7'
DISTRO ?= 'fsl-imx-xwayland'
DISTRO_FEATURES_append=" optee"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
PARALLEL_MAKE ?= "-j 16"
BB_NUMBER_THREADS ?= "16"

BB_DISKMON_DIRS ??= "
STOPTASKS,${TMPDIR},1G,100K
STOPTASKS,${DL_DIR},1G,100K
STOPTASKS,${SSTATE_DIR},1G,100K
STOPTASKS,/tmp,100M,100K
ABORT,${TMPDIR},100M,1K
ABORT,${DL_DIR},100M,1K
ABORT,${SSTATE_DIR},100M,1K
ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
CONF_VERSION = "1"
BASE_BOARD ?= "pi"
DISPLAY_INFO ?= "lcd"
RF_FIRMWARES ?= "qca ath-pci"
MACHINEOVERRIDES =. "${@'' if d.getVar('RF_FIRMWARES', True) is None else '%s:' % ':'.join([fw.lower() for fw in d.getVar('RF_FIRMWARES', True).split(' ') if fw])}"
MACHINEOVERRIDES =. "${@'' if d.getVar('SOUNDCARD', True) is None else '%s:' % d.getVar('SOUNDCARD', True).lower()}"

DL_DIR ?= "${BSPDIR}/downloads/"
ACCEPT_FSL_EULA = "1"
IMAGE_INSTALL_append = " gnupg atftp atftpd ntp ntpdate fping optee-client-imx optee-os-imx optee-test-imx"
EXTRA_IMAGE_FEATURES ?= "tools-debug tools-profile debug-tweaks eclipse-debug"
IMAGE_INSTALL_append = "
tcf-agent
openssh-sftp-server
gdbserver
apache2
"
CORE_IMAGE_EXTRA_INSTALL += "
trace-cmd i2c-tools e2fsprogs-resize2fs
bash bc cpio gawk tree rsync ldd vim nano
diffutils coreutils findutils iputils
git git-perltools libwebsockets vlan tcpdump
"
INHERIT += "extrausers"
ROOT_PASSWORD = "*******"
EXTRA_USERS_PARAMS = "usermod -P ${ROOT_PASSWORD} root;"
EXTRA_USERS_PARAMS += "useradd -P ${ROOT_PASSWORD} myuser;"

bblayers,conf:

LCONF_VERSION = "7"

BBPATH = "${TOPDIR}"
BSPDIR := "${@os.path.abspath(os.path.dirname(d.getVar('FILE', True)) + '/../..')}"

BBFILES ?= ""
BBLAYERS = "
${BSPDIR}/sources/poky/meta
${BSPDIR}/sources/poky/meta-poky

${BSPDIR}/sources/meta-openembedded/meta-oe
${BSPDIR}/sources/meta-openembedded/meta-webserver
${BSPDIR}/sources/meta-openembedded/meta-multimedia

${BSPDIR}/sources/meta-freescale
${BSPDIR}/sources/meta-freescale-3rdparty
${BSPDIR}/sources/meta-freescale-distro
"

i.MX Yocto Project Release TechNexion Layers

BBLAYERS += " ${BSPDIR}/sources/meta-edm-bsp-release "

i.MX Yocto Project Release layers

BBLAYERS += " ${BSPDIR}/sources/meta-fsl-bsp-release/imx/meta-bsp "
BBLAYERS += " ${BSPDIR}/sources/meta-fsl-bsp-release/imx/meta-sdk "
BBLAYERS += " ${BSPDIR}/sources/meta-browser "
BBLAYERS += " ${BSPDIR}/sources/meta-openembedded/meta-gnome "
BBLAYERS += " ${BSPDIR}/sources/meta-openembedded/meta-networking "
BBLAYERS += " ${BSPDIR}/sources/meta-openembedded/meta-python "
BBLAYERS += " ${BSPDIR}/sources/meta-openembedded/meta-filesystems "
BBLAYERS += " ${BSPDIR}/sources/meta-qt5 "

Reboot issue while ethernet not connected

Hello,

While the board is not connected to internet and rebooted it sometimes happens that the reboot freezes. In 99% of time it happens at:

[ Ok ] Stopped Update UTMP about System Boot/Shutdown.

Is there a fix for this issue?

Thank you,
Renegade

pico-imx6ul support - wrong device tree

I'm building an image for my pico-imx6ul. The result is an image running without the right device tree.

For example, the board can't load any wifi card.

This is my build configuration:

    Build Configuration:
    BB_VERSION           = "1.36.0"
    BUILD_SYS            = "x86_64-linux"
    NATIVELSBSTRING      = "ubuntu-18.04"
    TARGET_SYS           = "arm-poky-linux-gnueabi"
    MACHINE              = "pico-imx6ul-itl"
    DISTRO               = "fsl-imx-fb"
    DISTRO_VERSION       = "4.9.88-2.0.0"
    TUNE_FEATURES        = "arm armv7ve vfp neon callconvention-hard cortexa7"
    TARGET_FPU           = "hard"
    meta
    meta-poky            = "HEAD:0ec241873367e18f5371a3ad9aca1e2801dcd4ee"
    meta-oe
    meta-multimedia      = "HEAD:dacfa2b1920e285531bec55cd2f08743390aaf57"
    meta-freescale       = "HEAD:49ac225a38f6d84519798e3264f2e4d19b84f70a"
    meta-freescale-3rdparty = "HEAD:1d6d5961dbf82624b28bb318b4950a64abc31d12"
    meta-freescale-distro = "HEAD:0ec6d7e206705702b5b534611754de0787f92b72"
    meta-bsp
    meta-sdk             = "HEAD:d65692ecb3a4136fc1cc137152634e8633ddb3c6"
    meta-browser         = "HEAD:d6f9aed41c73b75a97d71bff060b03a66ee087b1"
    meta-gnome
    meta-networking
    meta-python
    meta-filesystems     = "HEAD:dacfa2b1920e285531bec55cd2f08743390aaf57"
    meta-qt5             = "HEAD:32bb7d18a08d1c48873d7ab6332d4cc3815a4dff"
    meta-edm-bsp-release = "added-wifi-drivers:10f5373fedd09c19ffb1a393272e3f3ed83b643a"

At the moment I use dd to flash the content of this archive:

    core-image-base-pico-imx6ul.sdcard.bz2

u-boot is using this device tree:

    imx6ul-pico-qca_pi.dts

But I want this one:

    imx6ul-pico_pi.dtb

Should I use a new Yocto version to correct this?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.