Giter Club home page Giter Club logo

meta-maaxboard's Introduction

meta-maaxboard

A meta-layer for Embest MaaXBoard.

This is the "zeus" / Yocto 3.0.4 branch. The zeus branch can only support MaaXBoard Nano now, For MaaXBoard / MaaXBoard Mini, please checkout the "sumo" / Yocto 2.5.3 branch. The "zeus" branch will support MaaXBoard / MaaXBoard Mini in the end of Dec 2020.

How to

Install Host Yocto Development Env

You should have a linux machine, below instructions show how to setup the env on a Ubuntu:18.04 machine.

$ sudo apt-get update && sudo apt-get install -y \
        gawk \
        wget \
        git-core \
        diffstat \
        unzip \
        texinfo \
        gcc-multilib \
        build-essential \
        chrpath \
        socat \
        libsdl1.2-dev \
        xterm \
        sed \
        cvs \
        subversion \
        coreutils \
        texi2html \
        docbook-utils \
        python-pysqlite2 \
        help2man \
        make \
        gcc \
        g++ \
        desktop-file-utils \
        libgl1-mesa-dev \
        libglu1-mesa-dev \
        mercurial \
        autoconf \
        automake \
        groff \
        curl \
        lzop \
        asciidoc \
        u-boot-tools \
        cpio \
        sudo \
        rsync \
        linux-headers-generic \
        locales

Install repo

sudo curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > /usr/bin/repo
sudo chmod a+x /usr/bin/repo

Fetch the source

Download meta layers from NXP

mkdir imx-yocto-bsp
$ cd imx-yocto-bsp
$ repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-zeus -m imx-5.4.24-2.1.0.xml
$ repo sync

Clone this repo and checkout to zeus branch

$ cd sources
$ git clone https://github.com/Avnet/meta-maaxboard.git
$ git checkout zeus

Do patch

NXP do some hook / patch according different machine / distro when init a new build. We need do this first.

If you're going to build MaaXBoard Nano

$ cd imx-yocto-bsp
$ mkdir imx8mnevk
$ DISTRO=fsl-imx-wayland MACHINE=imx8mnevk source imx-setup-release.sh -b imx8mnevk
$ rm -rf imx8mnevk

Build configure

$ cd imx-yocto-bsp
# Create the build directory
$ mkdir -p nano/build
# Create the default build conf in nano/build
$ source sources/poky/oe-init-build-env nano/build

Upate local conf

You should update 2 conf file in the build directory(nano/build/conf/):

  • local.conf
  • bblayers.conf

We provide a sample under /meta-maaxboard/conf:

  • local.conf.sample.nano for MaaXBoard Nano
  • bblayers.conf.sample

NOTE: variable 'BSPDIR' in bblayer.conf should be defined, the value should be the repo init directory. It is imx-yocto-bsp directory in above example

If you're going to build MaaXBoard Nano, you should change the Machine(in local.conf) to:

MACHINE ??= 'maaxboard-nano-ddr4-1g-sdcard'

Build

$ cd /path/to/bsp_dir/
$ source sources/poky/oe-init-build-env nano/build

$ bitbake lite-image

Flash sdcard

# This image will be generated under: /path/to/nano/build/tmp/deploy/images/maaxboard-nano-ddr4-1g-sdcard/lite-image-maaxboard-nano-ddr4-1g-sdcard-20201116084413.rootfs.wic.bz2
# unzip the bz2 file
$ bunzip2 lite-image-maaxboard-nano-*.rootfs.wic.bz2
## dd
$ sudo dd if=lite-image-maaxboard-nano-ddr4-1g-sdcard-20201116084413.rootfs.wic of=/dev/sda bs=10M conv=fsync
$ sync

Power On

The default login is user 'root' with the password 'avnet'

Build SDK

$ cd /path/to/bsp_dir/
$ source sources/poky/oe-init-build-env nano/build

$ bitbake lite-image -c populate_sdk
# The SDK will be generated under: /path/to/nano/build/tmp/deploy/sdk/
# fsl-imx-wayland-lite-glibc-x86_64-lite-image-aarch64-toolchain-5.4-zeus.sh

Install the SDK on a Host to develop Kernel / U-Boot

First, You should get the SDK: fsl-imx-wayland-lite-glibc-x86_64-lite-image-aarch64-toolchain-5.4-zeus.sh

$ chmod +x fsl-imx-wayland-lite-glibc-x86_64-lite-image-aarch64-toolchain-5.4-zeus.sh
# Install
$ ./fsl-imx-wayland-lite-glibc-x86_64-lite-image-aarch64-toolchain-5.4-zeus.sh

Configuration

  • Distor: 'fsl-imx-wayland-lite'
    • meta-maaxboard/conf/distro/fsl-imx-wayland-lite.conf
  • Image: "lite-image"
    • meta-maaxboard/images/lite-image.bb
  • Machine:
    • MaaXBoard Nano: maaxboard-nano-ddr4-1g-sdcard

Customization

  • You could add more packages in the image recipe: meta-maaxboard/images/lite-image.bb
  • Distro features: meta-maaxboard/conf/distro/fsl-imx-wayland-lite.conf
  • Machine features: meta-maaxboard/conf/machine/maaxboard-ddr4-2g-sdcard.conf

Setup a Debian Repository

Here we want to show you how to setup a Debian Repository. In this way, you could use apt-get install to install packages that you built in Yocto.

Host Setup

This is the host machine that you build the Yocto images. If you want to setup a Debian repository, you should also install a web server here.

$ sudo apt install nginx

Build Packages

Before using apt-get install a package, you should first build it. Let's take nano for example.

$ cd /path/to/bsp_dir/
$ source sources/poky/oe-init-build-env maaxboard/build

$ bitbake nano

Generate Packages index files

After build the packages, you should generate the package index files for apt-get to search.

First, change to the deb directory:

$ cd /home/build/maaxboard-nano/nano/build/tmp/deploy/deb
$ ls
aarch64  aarch64-mx8mn  all  maaxboard_nano_ddr4_1g_sdcard

Add a script called dpkg-scan.sh

$ nano dpkg-scan.sh

Add

#!/bin/bash

ls -d */  | sed 's/\///' | cat | while IFS=' ' read -r item
do
    echo "[$item]"
    echo -e "\t- Delete pevious generated package info(./Package, ./Package.gz, ./Release)"
    rm -rf ${item}/Packages.gz ${item}/Packages ${item}/Release
    echo -e "\t- Scan Packages and generate Packages.gz"
    dpkg-scanpackages ${item} | gzip > ${item}/Packages.gz
done
$ sudo chmod +x ./dpkg-scan.sh

Exec ./dpkg-scan.sh everytime you build a new package:

./dpkg-scan.sh

Config web server

sudo nano /etc/nginx/sites-available/deb

Add

server {
    listen 80 default_server;
    server_name yocto_deb_packages;
    root /home/build/maaxboard/maaxboard-yocto/maaxboard/build/tmp/deploy/deb/;

    location / {
        autoindex on;
    }
}

Enable website

# Disable the nginx default site
$ sudo rm /etc/nginx/sites-enabled/default
$ sudo ln -s /etc/nginx/sites-available/deb /etc/nginx/sites-enabled/deb

Start / Stop nginx

$ sudo systemctl restart nginx

In your client web browser, check the website:

http://192.168.2.58/

MaaXBoard Config

Add Sources List

$ sudo nano /etc/apt/sources.list

Add

deb http://192.168.2.58/ aarch64/
deb http://192.168.2.58/ aarch64-mx8mn/
deb http://192.168.2.58/ maaxboard_nano_ddr4_1g_sdcard/
deb http://192.168.2.58/ all/

apt-get update

$ sudo rm -rf /var/lib/apt/lists/*
$ sudo apt-get update

Install packages

sudo apt-get install nano

meta-maaxboard's People

Contributors

ahnniu avatar david-fuu avatar nickembest avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

meta-maaxboard's Issues

Installation issue while compiling NCEPLIBS-g2c lib on centos 8

Dear All,
Plz go through the make error and unable to install NCEPLIBS-g2c on centos 8. Plz find the error file.
ANy suggestion will hep a lot.

make
[ 0%] Building C object CMakeFiles/g2c.dir/src/cmplxpack.c.o
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:55:18: error: ‘G2C_SECTION1_ARRAY_LEN’ undeclared here (not in a function)
int section1[G2C_SECTION1_ARRAY_LEN]; /< Section 1 array. */
^~~~~~~~~~~~~~~~~~~~~~
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:132:15: error: ‘G2C_MAX_NAME’ undeclared here (not in a function); did you mean ‘G2C_MAX_MESSAGES’?
char path[G2C_MAX_NAME + 1]; /
< Path of the file. */
^~~~~~~~~~~~
G2C_MAX_MESSAGES
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:142:15: error: ‘G2C_MAX_GRIB_DESC_LEN’ undeclared here (not in a function); did you mean ‘G2C_MAGIC_HEADER_LEN’?
char desc[G2C_MAX_GRIB_DESC_LEN + 1];
^~~~~~~~~~~~~~~~~~~~~
G2C_MAGIC_HEADER_LEN
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:143:17: error: ‘G2C_MAX_GRIB_STATUS_LEN’ undeclared here (not in a function); did you mean ‘G2C_MAGIC_HEADER_LEN’?
char status[G2C_MAX_GRIB_STATUS_LEN + 1];
^~~~~~~~~~~~~~~~~~~~~~~
G2C_MAGIC_HEADER_LEN
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:144:15: error: ‘G2C_MAX_GRIB_CODE_LEN’ undeclared here (not in a function); did you mean ‘G2C_MAGIC_HEADER_LEN’?
char code[G2C_MAX_GRIB_CODE_LEN + 1];
^~~~~~~~~~~~~~~~~~~~~
G2C_MAGIC_HEADER_LEN
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:151:16: error: ‘G2C_MAX_GRIB_TITLE_LEN’ undeclared here (not in a function); did you mean ‘G2C_MAGIC_HEADER_LEN’?
char title[G2C_MAX_GRIB_TITLE_LEN + 1];
^~~~~~~~~~~~~~~~~~~~~~
G2C_MAGIC_HEADER_LEN
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:163:17: error: ‘G2C_MAX_NOAA_ABBREV_LEN’ undeclared here (not in a function); did you mean ‘G2C_MAGIC_HEADER_LEN’?
char abbrev[G2C_MAX_NOAA_ABBREV_LEN + 1]; /< NOAA abbreviation for this parameter. */
^~~~~~~~~~~~~~~~~~~~~~~
G2C_MAGIC_HEADER_LEN
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:169:8: error: redefinition of ‘struct gtemplate’
struct gtemplate
^~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:29,
from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/supplibs/include/grib2.h:163:8: note: originally defined here
struct gtemplate {
^~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:197:26: error: conflicting types for ‘gtemplate’
typedef struct gtemplate gtemplate; /
< Struct for GRIB template. */
^~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:29,
from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/supplibs/include/grib2.h:179:26: note: previous declaration of ‘gtemplate’ was here
typedef struct gtemplate gtemplate;
^~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:205:12: error: conflicting types for ‘getdrstemplate’
gtemplate *getdrstemplate(g2int number);
^~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:29,
from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/supplibs/include/grib2.h:230:19: note: previous declaration of ‘getdrstemplate’ was here
extern gtemplate *getdrstemplate(g2int);
^~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:206:12: error: conflicting types for ‘extdrstemplate’
gtemplate *extdrstemplate(g2int number, g2int *list);
^~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:29,
from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/supplibs/include/grib2.h:231:19: note: previous declaration of ‘extdrstemplate’ was here
extern gtemplate *extdrstemplate(g2int,g2int *);
^~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:207:12: error: conflicting types for ‘getpdstemplate’
gtemplate *getpdstemplate(g2int number);
^~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:29,
from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/supplibs/include/grib2.h:228:19: note: previous declaration of ‘getpdstemplate’ was here
extern gtemplate *getpdstemplate(g2int);
^~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:208:12: error: conflicting types for ‘extpdstemplate’
gtemplate *extpdstemplate(g2int number, g2int *list);
^~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:29,
from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/supplibs/include/grib2.h:229:19: note: previous declaration of ‘extpdstemplate’ was here
extern gtemplate *extpdstemplate(g2int,g2int *);
^~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:209:12: error: conflicting types for ‘getgridtemplate’
gtemplate *getgridtemplate(g2int number);
^~~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:29,
from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/supplibs/include/grib2.h:232:19: note: previous declaration of ‘getgridtemplate’ was here
extern gtemplate *getgridtemplate(g2int);
^~~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:210:12: error: conflicting types for ‘extgridtemplate’
gtemplate *extgridtemplate(g2int number, g2int *list);
^~~~~~~~~~~~~~~
In file included from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/grib2_int.h:29,
from /home/drdinesh/Desktop/WRF-MET/UPP/UPP-Libs/NCEPLIBS-g2c-develop/src/cmplxpack.c:7:
/home/supplibs/include/grib2.h:233:19: note: previous declaration of ‘extgridtemplate’ was here
extern gtemplate *extgridtemplate(g2int,g2int *);
^~~~~~~~~~~~~~~
make[2]: *** [CMakeFiles/g2c.dir/build.make:76: CMakeFiles/g2c.dir/src/cmplxpack.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:200: CMakeFiles/g2c.dir/all] Error 2
make: *** [Makefile:146: all] Error 2
(base) [root@localhost build]# make check install
make: *** No rule to make target 'check'. Stop.

Regards

Dr Dinesh
Central University of Jammu, India

Glibc build fails

Hi,

I'm trying to build a Yocto image but the build fails when compiling glibc.
I ran this command:

bitbake lite-image-qt5

I get a compilation error as follows:

u/LocalDisk/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-poky-linux/glibc/2.27-r0/build-aarch64-poky-linux/elf/ld.so -Wl,--no-as-needed -Wl,--end-group
| /media/ubuntu/LocalDisk/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-poky-linux/glibc/2.27-r0/build-aarch64-poky-linux/nptl/libpthread_nonshared.a(pthread_atfork.oS): In function `__pthread_atfork':
| /usr/src/debug/glibc/2.27-r0/git/nptl/pthread_atfork.c:51: undefined reference to `__dso_handle'
| /usr/src/debug/glibc/2.27-r0/git/nptl/pthread_atfork.c:51: undefined reference to `__dso_handle'
| /media/ubuntu/LocalDisk/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-poky-linux/glibc/2.27-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux.gcc-cross-initial-aarch64/../../libexec/aarch64-poky-linux.gcc-cross-initial-aarch64/gcc/aarch64-poky-linux/7.3.0/ld: /media/ubuntu/LocalDisk/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-poky-linux/glibc/2.27-r0/build-aarch64-poky-linux/rt/librt.so: hidden symbol `__dso_handle' isn't defined
| /media/ubuntu/LocalDisk/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-poky-linux/glibc/2.27-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux.gcc-cross-initial-aarch64/../../libexec/aarch64-poky-linux.gcc-cross-initial-aarch64/gcc/aarch64-poky-linux/7.3.0/ld: final link failed: Bad value
| collect2: error: ld returned 1 exit status
| ../Makerules:599: recipe for target '/media/ubuntu/LocalDisk/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-poky-linux/glibc/2.27-r0/build-aarch64-poky-linux/rt/librt.so' failed
| make[2]: *** [/media/ubuntu/LocalDisk/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-poky-linux/glibc/2.27-r0/build-aarch64-poky-linux/rt/librt.so] Error 1
| make[2]: Leaving directory '/media/ubuntu/LocalDisk/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-poky-linux/glibc/2.27-r0/git/rt'
| Makefile:235: recipe for target 'rt/others' failed
| make[1]: *** [rt/others] Error 2
| make[1]: Leaving directory '/media/ubuntu/LocalDisk/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-poky-linux/glibc/2.27-r0/git'
| Makefile:9: recipe for target 'all' failed
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /media/ubuntu/LocalDisk/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-poky-linux/glibc/2.27-r0/temp/log.do_compile.7744)
ERROR: Task (/media/ubuntu/LocalDisk/imx-yocto-bsp/sources/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 227 tasks of which 221 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /media/ubuntu/LocalDisk/imx-yocto-bsp/sources/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

how can I resolve the compilation error?

I have already carried out some solutions as follows:

clean

bitbake -c clean glibc
Compile the recipe

bitbake -f -c compile glibc
but this still produced the same error.

I can not build u-boot-fw-utils , and can I use fw_printenv, fw_setenv in user space to set uboot environment variables on maaxboard?

Hi all
I am playing rauc. there are two rootfs to boot.
so need to change uboot environment variables to switch boot between the first rootfs and redundant rootfs.
so need to add IMAGE_INSTALL_append +="u-boot-fw-utils " in yocto local file to enable fw_printenv, fw_setenv.
but bitbake can not pass build u-boot-fw-utils. it shows can find maaxboard_defconfig. so I use imx8mq_evk_defconfig to instead it.
it can pass building. but after bootup, I run fw_printenv , it shows error : can not find /dev/mtd1. and can not find /dev/mtd either
before I did not add IMAGE_INSTALL_append +="u-boot-fw-utils " , of course, there was not command fw_printenv. but it could find /dev/mtd ,only no content.

My question is that I want to know do I can use fw_printenv ? or Can I use uEnv.txt to change uboot environment variables to switch boot the two rootfs' ?
any help?
Thank you

how to install Latex(or texlive) in maaxboard yocto image in .bb files

Hi all ,
I posted the similar question at nxp forum and raspberry pi meta,
agherzan/meta-raspberrypi#1225
https://community.nxp.com/t5/i-MX-Processors/how-to-install-latex-or-texlive-in-imx8/m-p/1349791

I need to add Latex(or texlive) in my yocto image both in raspberry pi4 and nxp maaxboard.
but it seems nobody did before. I post as same question at https://community.nxp.com/t5/i-MX-Processors/how-to-install-latex-or-texlive-in-imx8/m-p/1349791 2 years ago. but no solutions.
I know in raspberry pi desktop. we can use below command to install it:
sudo apt-get update

sudo apt-get install texlive-base

sudo apt-get install texlive-latex-recommended

sudo apt-get install texlive

sudo apt-get install texlive-latex-extra

sudo apt-get install texlive-lang-cjk

sudo apt-get install texlive-lang-english

sudo apt-get install texlive-lang-european

sudo apt-get install texlive-lang-spanish

sudo apt-get install texlive-fonts-extra

after that I directly copy the installed binary executable code to my yocto image in pi4. but can I copy them to nxp board?(same arm64 ) .
finally I want to know how to create a .bb file in yocto to auoto build it? it seems both raspberry pi yocto and nxp yocto do not do it.
any help ?

Thank you so much.

how to burn yocto image into maaxboard emmc version with uuu tools

hi,
I want to burn yocto image (all file in it: u-boot,dtb, kernel image and rootfs)
for example ,we can burn the following file into sdcard,
lite-image-maaxboard-ddr4-2g-sdcard-20200515065319.rootfs.sdcard
but how to burn it into emmc?
do you have the script file ?
Thank you.
I asked my question at here too.

https://community.nxp.com/t5/i-MX-Processors/which-u-boot-file-in-yocto-can-I-burn-into-emmc-for-imx8mqevk/m-p/1191786#M165795

Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.'

Here is the issue:

ERROR: gstreamer1.0-1.22.0.imx-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus,guid=7d48257d4a2b2f287b6dc669665af38c"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/ubu/imx-yocto-bsp/maaxboard/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/ubu/imx-yocto-bsp/maaxboard/build/tmp/work/armv8a-poky-linux/gstreamer1.0/1.22.0.imx-r0/recipe-sysroot-native/usr/bin/python3-native:/home/ubu/imx-yocto-bsp/sources/poky/scripts:/home/ubu/imx-yocto-bsp/maaxboard/build/tmp/work/armv8a-poky-linux/gstreamer1.0/1.22.0.imx-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/home/ubu/imx-yocto-bsp/maaxboard/build/tmp/work/armv8a-poky-linux/gstreamer1.0/1.22.0.imx-r0/recipe-sysroot/usr/bin/crossscripts:/home/ubu/imx-yocto-bsp/maaxboard/build/tmp/work/armv8a-poky-linux/gstreamer1.0/1.22.0.imx-r0/recipe-sysroot-native/usr/sbin:/home/ubu/imx-yocto-bsp/maaxboard/build/tmp/work/armv8a-poky-linux/gstreamer1.0/1.22.0.imx-r0/recipe-sysroot-native/usr/bin:/home/ubu/imx-yocto-bsp/maaxboard/build/tmp/work/armv8a-poky-linux/gstreamer1.0/1.22.0.imx-r0/recipe-sysroot-native/sbin:/home/ubu/imx-yocto-bsp/maaxboard/build/tmp/work/armv8a-poky-linux/gstreamer1.0/1.22.0.imx-r0/recipe-sysroot-native/bin:/home/ubu/imx-yocto-bsp/sources/poky/bitbake/bin:/home/ubu/imx-yocto-bsp/maaxboard/build/tmp/hosttools"; export HOME="/home/ubu"; LANG=C git -c gc.autoDetach=false -c core.pager=cat clone --bare --mirror https://github.com/nxp-imx/gstreamer.git /home/ubu/imx-yocto-bsp/maaxboard/build/downloads/git2/github.com.nxp-imx.gstreamer.git --progress failed with exit code 128, no output
ERROR: gstreamer1.0-1.22.0.imx-r0 do_fetch: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.', 'gitsm://github.com/nxp-imx/gstreamer.git;protocol=https;branch=MM_04.08.00_2305_L6.1.y')
ERROR: Logfile of failure stored in: /home/ubu/imx-yocto-bsp/maaxboard/build/tmp/work/armv8a-poky-linux/gstreamer1.0/1.22.0.imx-r0/temp/log.do_fetch.450306
ERROR: Task (/home/ubu/imx-yocto-bsp/sources/meta-imx/meta-bsp/recipes-multimedia/gstreamer/gstreamer1.0_1.22.0.imx.bb:do_fetch) failed with exit code '1'

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.