From db5067371e83d56d16b0312b1c67806a0d5ec8a8 Mon Sep 17 00:00:00 2001 From: Javier Viguera Date: Wed, 30 Nov 2022 18:06:57 +0100 Subject: [PATCH] meta-digi: get rid of ccimx8mp-dvk Platform not supported. Signed-off-by: Javier Viguera --- meta-digi-arm/conf/machine/ccimx8mp-dvk.conf | 56 ---- .../conf/machine/include/digi-defaults.inc | 1 - .../firmware-murata/firmware-murata.bb | 2 +- .../u-boot/u-boot-dey/ccimx8mp-dvk/boot.txt | 96 ------ .../recipes-bsp/u-boot/u-boot-dey_2021.04.bb | 11 - .../ccimx8mp/80-mm-net-device-blacklist.rules | 18 -- .../wpa-supplicant/wpa-supplicant_%.bbappend | 1 - .../ccimx8mp-dvk/libdigiapix.conf | 36 --- sdk/build-github.sh | 2 - sdk/build.sh | 1 - sdk/config/ccimx8mp-dvk/bblayers.conf.sample | 26 -- sdk/config/ccimx8mp-dvk/conf-notes.txt | 11 - sdk/config/ccimx8mp-dvk/local.conf.sample | 293 ------------------ sdk/mkproject.sh | 2 +- 14 files changed, 2 insertions(+), 554 deletions(-) delete mode 100644 meta-digi-arm/conf/machine/ccimx8mp-dvk.conf delete mode 100644 meta-digi-arm/recipes-bsp/u-boot/u-boot-dey/ccimx8mp-dvk/boot.txt delete mode 100644 meta-digi-arm/recipes-bsp/u-boot/u-boot-dey_2021.04.bb delete mode 100644 meta-digi-dey/recipes-connectivity/modemmanager/modemmanager/ccimx8mp/80-mm-net-device-blacklist.rules delete mode 100644 meta-digi-dey/recipes-digi/libdigiapix/libdigiapix-git/ccimx8mp-dvk/libdigiapix.conf delete mode 100644 sdk/config/ccimx8mp-dvk/bblayers.conf.sample delete mode 100644 sdk/config/ccimx8mp-dvk/conf-notes.txt delete mode 100644 sdk/config/ccimx8mp-dvk/local.conf.sample diff --git a/meta-digi-arm/conf/machine/ccimx8mp-dvk.conf b/meta-digi-arm/conf/machine/ccimx8mp-dvk.conf deleted file mode 100644 index 61e6a7db5..000000000 --- a/meta-digi-arm/conf/machine/ccimx8mp-dvk.conf +++ /dev/null @@ -1,56 +0,0 @@ -#@TYPE: Machine -#@NAME: ConnectCore 8M Plus Development Kit. -#@DESCRIPTION: Machine configuration for Digi's ConnectCore 8M Plus DVK. - -# Include the machine configuration for Digi's ConnectCore 8M module. -include conf/machine/include/ccimx8m.inc - -# Temporarily remove wifi and bluetooth machine features until -# we have proper support for the Murata module. -MACHINE_FEATURES:remove = "wifi bluetooth" - -DIGI_FAMILY = "ccimx8mp" -MACHINEOVERRIDES =. "mx8:mx8m:mx8mp:ccimx8m:${DIGI_FAMILY}:" - -BOOTLOADER_SEEK_USERDATA = "32" -BOOTLOADER_SEEK_BOOT = "0" - -# U-Boot configurations -# Last one is the default (the one the symlinks point at) -UBOOT_CONFIG ??= "ccimx8mp_dvk" -UBOOT_CONFIG[ccimx8mp_dvk] = "ccimx8mp_dvk_defconfig,,u-boot-dtb.${UBOOT_SUFFIX}" - -# Set DDR FIRMWARE -DDR_FIRMWARE_VERSION = "202006" -DDR_FIRMWARE_NAME = " \ - lpddr4_pmu_train_1d_dmem_${DDR_FIRMWARE_VERSION}.bin \ - lpddr4_pmu_train_1d_imem_${DDR_FIRMWARE_VERSION}.bin \ - lpddr4_pmu_train_2d_dmem_${DDR_FIRMWARE_VERSION}.bin \ - lpddr4_pmu_train_2d_imem_${DDR_FIRMWARE_VERSION}.bin \ -" - -SPL_BINARY = "spl/u-boot-spl.bin" - -# Set u-boot DTB -UBOOT_DTB_NAME = "ccimx8mp-dvk.dtb" - -ATF_PLATFORM = "imx8mp" - -KERNEL_DEVICETREE ?= " \ - digi/ccimx8mp-dvk.dtb \ -" - -SERIAL_CONSOLES ?= "115200;ttymxc0" - -# Bluetooth tty -BT_TTY ?= "ttymxc1" - -# XBees -XBEE_RESET_N_GPIO ?= "mca-gpio@15,gpio1@8" -XBEE_SLEEP_RQ_GPIO ?= "mca-gpio@11,gpio1@7" -XBEE_TTY ?= "ttymxc3" - -# Image FS types -IMAGE_FSTYPES ?= '${@bb.utils.contains("IMAGE_FEATURES", "read-only-rootfs", \ - "boot.vfat tar.bz2 recovery.vfat squashfs", \ - "boot.vfat ext4.gz sdcard.gz tar.bz2 recovery.vfat", d)}' diff --git a/meta-digi-arm/conf/machine/include/digi-defaults.inc b/meta-digi-arm/conf/machine/include/digi-defaults.inc index 8f2f9bb2c..5080047a8 100644 --- a/meta-digi-arm/conf/machine/include/digi-defaults.inc +++ b/meta-digi-arm/conf/machine/include/digi-defaults.inc @@ -16,7 +16,6 @@ PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg" # ccimx8x 5.4 2020.04 (packaged in imx-boot) # ccimx8mn 5.4 2020.04 (packaged in imx-boot) # ccimx8mm 5.4 2020.04 (packaged in imx-boot) -# ccimx8mp 5.10 2021.04 (packaged in imx-boot) # ccmp15 5.15 2021.10 # ccmp13 5.15 2021.10 # diff --git a/meta-digi-arm/recipes-bsp/firmware-murata/firmware-murata.bb b/meta-digi-arm/recipes-bsp/firmware-murata/firmware-murata.bb index 418dec3f9..36da2d5af 100644 --- a/meta-digi-arm/recipes-bsp/firmware-murata/firmware-murata.bb +++ b/meta-digi-arm/recipes-bsp/firmware-murata/firmware-murata.bb @@ -66,4 +66,4 @@ INSANE_SKIP:${PN} += "build-deps" INSANE_SKIP:${PN} += "file-rdeps" PACKAGE_ARCH = "${MACHINE_ARCH}" -COMPATIBLE_MACHINE = "(ccimx8mp|ccmp1)" +COMPATIBLE_MACHINE = "(ccmp1)" diff --git a/meta-digi-arm/recipes-bsp/u-boot/u-boot-dey/ccimx8mp-dvk/boot.txt b/meta-digi-arm/recipes-bsp/u-boot/u-boot-dey/ccimx8mp-dvk/boot.txt deleted file mode 100644 index 3efee8a11..000000000 --- a/meta-digi-arm/recipes-bsp/u-boot/u-boot-dey/ccimx8mp-dvk/boot.txt +++ /dev/null @@ -1,96 +0,0 @@ -# -# U-Boot bootscript for EMMC/SD images created by Yocto. -# - -# As the first step in the boot script, check if we are using DualBoot and -# if an upgrade is available. This requires the script to change some variables -# and save them, while the rest of the script changes variables only temporarily -# without saving them. - -# Dual boot update verification -if test "${dualboot}" = "yes"; then - if test "${upgrade_available}" = "1"; then - echo "Update detected; Booting new system in ${active_system} (try ${bootcount})" - else - if test "${active_system}" = "linux_a"; then - echo "Booting from system A" - part number mmc ${mmcbootdev} linux_a pi - setenv mmcpart ${pi} - # Save the partition index on variable rootfs_a_index - part number mmc ${mmcbootdev} rootfs_a rootfs_a_index - # Save the rootfs_a UUID into mmcroot_a - part uuid mmc ${mmcbootdev}:${rootfs_a_index} mmcroot_a - setenv mmcroot PARTUUID=${mmcroot_a} - else - echo "Booting from system B" - part number mmc ${mmcbootdev} linux_b pi - setenv mmcpart ${pi} - # Save the partition index on variable rootfs_b_index - part number mmc ${mmcbootdev} rootfs_b rootfs_b_index - # Save the rootfs_b UUID into mmcroot_b - part uuid mmc ${mmcbootdev}:${rootfs_b_index} mmcroot_b - setenv mmcroot PARTUUID=${mmcroot_b} - fi - fi -else - # Get the UUID of the configured boot partition. - part uuid mmc ${mmcbootdev}:${mmcpart} bootpart - # Check the boot source. - if test "${bootpart}" = "${part1_uuid}"; then - # We are booting from the eMMC using 'linux'. - true - elif test "${bootpart}" = "${part2_uuid}"; then - # We are booting from the eMMC using 'recovery'. - setenv boot_initrd true - setenv initrd_file uramdisk-recovery.img - else - # We are booting from the SD card. - setenv mmcroot /dev/mmcblk${mmcbootdev}p2 - fi -fi - - -# Back up environment variables -setenv ORIG_overlays ${overlays} -setenv ORIG_extra_bootargs ${extra_bootargs} - -# Set SOC type to "imx8mp" if not already defined by U-Boot -if test ! -n "${soc_type}"; then - setenv soc_type "imx8mp" -fi - -# -# Determine overlays to apply depending on the hardware capabilities -# described by the HWID, SOM version, and carrier board version. -# -if test -n "${module_ram}"; then - setexpr module_has_wifi ${hwid_2} \& 10000 - setexpr module_has_wifi ${module_has_wifi} / 10000 - setexpr module_has_bt ${hwid_2} \& 20000 - setexpr module_has_bt ${module_has_bt} / 20000 - - ## - ## @TODO: THE OVERLAYS NEED TO BE ADJUSTED ONCE THE MURATA SUPPORT - ## IS IN PLACE. - ## - if test "${module_has_bt}" = "1" && test -z "${disable_bt}"; then - setenv overlays _ov_som_bt_ccimx8m.dtbo,${overlays} - fi - - if test "${module_has_wifi}" = "1" && test -z "${disable_wifi}"; then - setenv overlays _ov_som_wifi_ccimx8m.dtbo,${overlays} - fi -fi - -setenv extra_bootargs fbcon=logo-pos:center ${extra_bootargs} -dboot linux mmc ${mmcbootdev}:${mmcpart} - - - -# We only get here in case of an error on the dboot command. - -# Undo changes to environment variables -setenv overlays ${ORIG_overlays} -setenv ORIG_overlays -setenv extra_bootargs ${ORIG_extra_bootargs} -setenv ORIG_extra_bootargs diff --git a/meta-digi-arm/recipes-bsp/u-boot/u-boot-dey_2021.04.bb b/meta-digi-arm/recipes-bsp/u-boot/u-boot-dey_2021.04.bb deleted file mode 100644 index a7125775d..000000000 --- a/meta-digi-arm/recipes-bsp/u-boot/u-boot-dey_2021.04.bb +++ /dev/null @@ -1,11 +0,0 @@ -# Copyright (C) 2022 Digi International - -require digi-u-boot.inc -LIC_FILES_CHKSUM = "file://Licenses/README;md5=5a7450c57ffe5ae63fd732446b988025" - -DEPENDS += "flex-native bison-native" - -SRCBRANCH = "v2021.04/master" -SRCREV = "${AUTOREV}" - -COMPATIBLE_MACHINE = "(ccimx8mp)" diff --git a/meta-digi-dey/recipes-connectivity/modemmanager/modemmanager/ccimx8mp/80-mm-net-device-blacklist.rules b/meta-digi-dey/recipes-connectivity/modemmanager/modemmanager/ccimx8mp/80-mm-net-device-blacklist.rules deleted file mode 100644 index b5f43b430..000000000 --- a/meta-digi-dey/recipes-connectivity/modemmanager/modemmanager/ccimx8mp/80-mm-net-device-blacklist.rules +++ /dev/null @@ -1,18 +0,0 @@ -ACTION!="add|change|move|bind", GOTO="mm_net_device_blacklist_end" - -# ModemManager documentation states that the best practice is to use the DEVPATH -# this way rather than other rules such as KERNEL, so be careful when modifying - -# Remove Ethernet interfaces from ModemManager probing -SUBSYSTEM=="net", DEVPATH=="/devices/platform/30be0000.ethernet*", ENV{ID_MM_CANDIDATE}="0", ENV{ID_MM_DEVICE_IGNORE}="1" - -# Remove SPI-to-CAN interface from ModemManager probing -SUBSYSTEM=="net", DEVPATH=="/devices/platform/30840000.ecspi*", ENV{ID_MM_CANDIDATE}="0", ENV{ID_MM_DEVICE_IGNORE}="1" - -# Remove MMC interfaces from ModemManager probing -SUBSYSTEM=="net", DEVPATH=="/devices/platform/30b40000.mmc*", ENV{ID_MM_CANDIDATE}="0", ENV{ID_MM_DEVICE_IGNORE}="1" - -# Remove PCIe interfaces from ModemManager probing -SUBSYSTEM=="net", DEVPATH=="/devices/platform/33800000.pcie*", ENV{ID_MM_CANDIDATE}="0", ENV{ID_MM_DEVICE_IGNORE}="1" - -LABEL="mm_net_device_blacklist_end" diff --git a/meta-digi-dey/recipes-connectivity/wpa-supplicant/wpa-supplicant_%.bbappend b/meta-digi-dey/recipes-connectivity/wpa-supplicant/wpa-supplicant_%.bbappend index d9596a6c7..e5081c079 100644 --- a/meta-digi-dey/recipes-connectivity/wpa-supplicant/wpa-supplicant_%.bbappend +++ b/meta-digi-dey/recipes-connectivity/wpa-supplicant/wpa-supplicant_%.bbappend @@ -42,7 +42,6 @@ MURATA_COMMON_PATCHES = " \ SRC_URI:append:ccimx6sbc = " file://wpa_supplicant_p2p.conf_atheros" SRC_URI:append:ccmp1 = " ${MURATA_COMMON_PATCHES}" -SRC_URI:append:ccimx8mp = " ${MURATA_COMMON_PATCHES}" do_install:append() { install -m 600 ${WORKDIR}/wpa_supplicant_p2p.conf ${D}${sysconfdir}/wpa_supplicant_p2p.conf diff --git a/meta-digi-dey/recipes-digi/libdigiapix/libdigiapix-git/ccimx8mp-dvk/libdigiapix.conf b/meta-digi-dey/recipes-digi/libdigiapix/libdigiapix-git/ccimx8mp-dvk/libdigiapix.conf deleted file mode 100644 index 5a4886fc3..000000000 --- a/meta-digi-dey/recipes-digi/libdigiapix/libdigiapix-git/ccimx8mp-dvk/libdigiapix.conf +++ /dev/null @@ -1,36 +0,0 @@ -[board] -model = Digi International ConnectCore 8M Plus DVK. - -[GPIO] - -# USER LED1 -USER_LED = mca-gpio,12 -USER_LED1 = mca-gpio,12 - -# USER_LED2 -USER_LED2 = mca-gpio,18 - -# USER_LED3 -USER_LED3 = gpio2,19 - -# USER BUTTON1 -USER_BUTTON = mca-gpio,10 -USER_BUTTON1 = mca-gpio,10 - -# USER BUTTON2 -USER_BUTTON2 = gpio3,7 - -[I2C] - -# I2C-4 on Expansion connector. -DEFAULT_I2C_BUS = 4 - -[PWM] - -# PWM0 channel 1 USER_LED1. -DEFAULT_PWM = 0,1 - -[ADC] - -# MCA_IO1 (channel 1) at XBEE1_UART_TX. Not enabled by default. -DEFAULT_ADC = 0,1 diff --git a/sdk/build-github.sh b/sdk/build-github.sh index 3c468ba1f..961f8de49 100755 --- a/sdk/build-github.sh +++ b/sdk/build-github.sh @@ -25,7 +25,6 @@ set -e AVAILABLE_PLATFORMS=" \ ccimx8mm-dvk \ ccimx8mn-dvk \ - ccimx8mp-dvk \ ccimx8x-sbc-pro \ ccimx8x-sbc-express \ ccimx6qpsbc \ @@ -143,7 +142,6 @@ while read _pl _tgt; do done<<-_EOF_ ccimx8mm-dvk dey-image-qt ccimx8mn-dvk dey-image-qt - ccimx8mp-dvk dey-image-qt ccimx8x-sbc-pro dey-image-qt ccimx8x-sbc-express dey-image-qt ccimx6qpsbc dey-image-qt diff --git a/sdk/build.sh b/sdk/build.sh index 2dc47ed90..85e84a6a6 100755 --- a/sdk/build.sh +++ b/sdk/build.sh @@ -160,7 +160,6 @@ while read -r _pl _tgt; do done<<-_EOF_ ccimx8mm-dvk dey-image-qt,dey-image-crank ccimx8mn-dvk dey-image-qt,dey-image-crank - ccimx8mp-dvk dey-image-qt,dey-image-crank ccimx8x-sbc-pro dey-image-qt,dey-image-crank ccimx8x-sbc-express dey-image-qt ccimx6qpsbc dey-image-qt,dey-image-crank diff --git a/sdk/config/ccimx8mp-dvk/bblayers.conf.sample b/sdk/config/ccimx8mp-dvk/bblayers.conf.sample deleted file mode 100644 index f716b9844..000000000 --- a/sdk/config/ccimx8mp-dvk/bblayers.conf.sample +++ /dev/null @@ -1,26 +0,0 @@ -# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf -# changes incompatibly -POKY_BBLAYERS_CONF_VERSION = "2" - -BBPATH = "${TOPDIR}" -BBFILES ?= "" - -BBLAYERS ?= " \ - ##OEROOT##/meta \ - ##OEROOT##/meta-poky \ - ##OEROOT##/meta-yocto-bsp \ - ##DIGIBASE##/meta-openembedded/meta-oe \ - ##DIGIBASE##/meta-openembedded/meta-python \ - ##DIGIBASE##/meta-openembedded/meta-networking \ - ##DIGIBASE##/meta-openembedded/meta-webserver \ - ##DIGIBASE##/meta-qt5 \ - ##DIGIBASE##/meta-swupdate \ - ##DIGIBASE##/meta-freescale \ - ##DIGIBASE##/meta-fsl-demos \ - ##DIGIBASE##/meta-webkit \ - ##DIGIBASE##/meta-imx/meta-ml \ - ##DIGIBASE##/meta-selinux \ - ##DIGIBASE##/meta-timesys \ - ##DIGIBASE##/meta-digi/meta-digi-arm \ - ##DIGIBASE##/meta-digi/meta-digi-dey \ - " diff --git a/sdk/config/ccimx8mp-dvk/conf-notes.txt b/sdk/config/ccimx8mp-dvk/conf-notes.txt deleted file mode 100644 index b49f5e14b..000000000 --- a/sdk/config/ccimx8mp-dvk/conf-notes.txt +++ /dev/null @@ -1,11 +0,0 @@ -Digi Embedded Yocto provides the following image recipes: - - * dey-image-qt: graphical QT image - - By default the image is XWayland-based so it provides a full Weston - desktop environment. - - * dey-image-webkit: graphical WebKit image - - By default the image is XWayland-based so it provides a full Weston - desktop environment. diff --git a/sdk/config/ccimx8mp-dvk/local.conf.sample b/sdk/config/ccimx8mp-dvk/local.conf.sample deleted file mode 100644 index 157cb272c..000000000 --- a/sdk/config/ccimx8mp-dvk/local.conf.sample +++ /dev/null @@ -1,293 +0,0 @@ -# -# This file is your local configuration file and is where all local user settings -# are placed. The comments in this file give some guide to the options a new user -# to the system might want to change but pretty much any configuration option can -# be set in this file. More adventurous users can look at -# local.conf.sample.extended which contains other examples of configuration which -# can be placed in this file but new users likely won't need any of them -# initially. -# -# Lines starting with the '#' character are commented out and in some cases the -# default values are provided as comments to show people example syntax. Enabling -# the option is a question of removing the # character and making any change to the -# variable as required. - -# -# Machine Selection -# -# You need to select a specific machine to target the build with. There are a selection -# of emulated machines available which can boot and run in the QEMU emulator: -# -#MACHINE ?= "qemuarm" -#MACHINE ?= "qemuarm64" -#MACHINE ?= "qemumips" -#MACHINE ?= "qemumips64" -#MACHINE ?= "qemuppc" -#MACHINE ?= "qemux86" -#MACHINE ?= "qemux86-64" -# -# There are also the following hardware board target machines included for -# demonstration purposes: -# -#MACHINE ?= "beaglebone-yocto" -#MACHINE ?= "genericx86" -#MACHINE ?= "genericx86-64" -#MACHINE ?= "edgerouter" -# -# This sets the default machine to be qemux86-64 if no other machine is selected: -#MACHINE ??= "qemux86-64" - -MACHINE = "ccimx8mp-dvk" - -# -# Use Digi's internal git repositories -# -#DIGI_INTERNAL_GIT ?= "1" - -# -# Where to place downloads -# -# During a first build the system will download many different source code tarballs -# from various upstream projects. This can take a while, particularly if your network -# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you -# can preserve this directory to speed up this part of subsequent builds. This directory -# is safe to share between multiple builds on the same machine too. -# -# The default is a downloads directory under TOPDIR which is the build directory. -# -#DL_DIR ?= "${TOPDIR}/downloads" - -# -# Where to place shared-state files -# -# BitBake has the capability to accelerate builds based on previously built output. -# This is done using "shared state" files which can be thought of as cache objects -# and this option determines where those files are placed. -# -# You can wipe out TMPDIR leaving this directory intact and the build would regenerate -# from these files if no changes were made to the configuration. If changes were made -# to the configuration, only shared state files where the state was still valid would -# be used (done using checksums). -# -# The default is a sstate-cache directory under TOPDIR. -# -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# -# Where to place the build output -# -# This option specifies where the bulk of the building work should be done and -# where BitBake should place its temporary files and output. Keep in mind that -# this includes the extraction and compilation of many applications and the toolchain -# which can use Gigabytes of hard disk space. -# -# The default is a tmp directory under TOPDIR. -# -#TMPDIR = "${TOPDIR}/tmp" - -# -# Default policy config -# -# The distribution setting controls which policy settings are used as defaults. -# The default value is fine for general Yocto project use, at least initially. -# Ultimately when creating custom policy, people will likely end up subclassing -# these defaults. -# -DISTRO ?= "dey" -# As an example of a subclass there is a "bleeding" edge policy configuration -# where many versions are set to the absolute latest code from the upstream -# source control systems. This is just mentioned here as an example, its not -# useful to most new users. -# DISTRO ?= "poky-bleeding" - -# -# Package Management configuration -# -# This variable lists which packaging formats to enable. Multiple package backends -# can be enabled at once and the first item listed in the variable will be used -# to generate the root filesystems. -# Options are: -# - 'package_deb' for debian style deb files -# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) -# - 'package_rpm' for rpm style packages -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -# We default to rpm: -PACKAGE_CLASSES ?= "package_rpm" - -# -# SDK target architecture -# -# This variable specifies the architecture to build SDK items for and means -# you can build the SDK packages for architectures other than the machine you are -# running the build on (i.e. building i686 packages on an x86_64 host). -# Supported values are i686, x86_64, aarch64 -#SDKMACHINE ?= "i686" - -# -# Extra image configuration defaults -# -# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated -# images. Some of these options are added to certain image types automatically. The -# variable can contain the following options: -# "dbg-pkgs" - add -dbg packages for all installed packages -# (adds symbol information for debugging/profiling) -# "src-pkgs" - add -src packages for all installed packages -# (adds source code for debugging) -# "dev-pkgs" - add -dev packages for all installed packages -# (useful if you want to develop against libs in the image) -# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages -# (useful if you want to run the package test suites) -# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) -# "tools-debug" - add debugging tools (gdb, strace) -# "eclipse-debug" - add Eclipse remote debugging support -# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) -# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) -# "debug-tweaks" - make an image suitable for development -# e.g. ssh root access has a blank password -# There are other application targets that can be used here too, see -# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. -# We default to enabling the debugging tweaks. -EXTRA_IMAGE_FEATURES ?= "debug-tweaks" - -# -# Additional image features -# -# The following is a list of additional classes to use when building images which -# enable extra features. Some available options which can be included in this variable -# are: -# - 'buildstats' collect build statistics -USER_CLASSES ?= "buildstats" - -# -# Runtime testing of images -# -# The build system can test booting virtual machine images under qemu (an emulator) -# after any root filesystems are created and run tests against those images. It can also -# run tests against any SDK that are built. To enable this uncomment these lines. -# See classes/test{image,sdk}.bbclass for further details. -#IMAGE_CLASSES += "testimage testsdk" -#TESTIMAGE_AUTO:qemuall = "1" - -# -# Interactive shell configuration -# -# Under certain circumstances the system may need input from you and to do this it -# can launch an interactive shell. It needs to do this since the build is -# multithreaded and needs to be able to handle the case where more than one parallel -# process may require the user's attention. The default is iterate over the available -# terminal types to find one that works. -# -# Examples of the occasions this may happen are when resolving patches which cannot -# be applied, to use the devshell or the kernel menuconfig -# -# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none -# Note: currently, Konsole support only works for KDE 3.x due to the way -# newer Konsole versions behave -#OE_TERMINAL = "auto" -# By default disable interactive patch resolution (tasks will just fail instead): -PATCHRESOLVE = "noop" - -# -# Disk Space Monitoring during the build -# -# Monitor the disk space during the build. If there is less that 1GB of space or less -# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully -# shutdown the build. If there is less than 100MB or 1K inodes, perform a hard halt -# of the build. The reason for this is that running completely out of space can corrupt -# files and damages the build in ways which may not be easily recoverable. -# It's necessary to monitor /tmp, if there is no space left the build will fail -# with very exotic errors. -BB_DISKMON_DIRS ??= "\ - STOPTASKS,${TMPDIR},1G,100K \ - STOPTASKS,${DL_DIR},1G,100K \ - STOPTASKS,${SSTATE_DIR},1G,100K \ - STOPTASKS,/tmp,100M,100K \ - HALT,${TMPDIR},100M,1K \ - HALT,${DL_DIR},100M,1K \ - HALT,${SSTATE_DIR},100M,1K \ - HALT,/tmp,10M,1K" - -# -# Shared-state files from other locations -# -# As mentioned above, shared state files are prebuilt cache data objects which can be -# used to accelerate build time. This variable can be used to configure the system -# to search other mirror locations for these objects before it builds the data itself. -# -# This can be a filesystem directory, or a remote url such as https or ftp. These -# would contain the sstate-cache results from previous builds (possibly from other -# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the -# cache locations to check for the shared objects. -# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH -# at the end as shown in the examples below. This will be substituted with the -# correct path within the directory structure. -#SSTATE_MIRRORS ?= "\ -#file://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \ -#file://.* file:///some/local/dir/sstate/PATH" - -# -# Yocto Project SState Mirror -# -# The Yocto Project has prebuilt artefacts available for its releases, you can enable -# use of these by uncommenting the following lines. This will mean the build uses -# the network to check for artefacts at the start of builds, which does slow it down -# equally, it will also speed up the builds by not having to build things if they are -# present in the cache. It assumes you can download something faster than you can build it -# which will depend on your network. -# Note: For this to work you also need hash-equivalence passthrough to the matching server -# -#BB_HASHSERVE_UPSTREAM = "typhoon.yocto.io:8687" -#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/4.0/PATH;downloadfilename=PATH" - -# -# Qemu configuration -# -# By default native qemu will build with a builtin VNC server where graphical output can be -# seen. The line below enables the SDL UI frontend too. -PACKAGECONFIG:append:pn-qemu-system-native = " sdl" -# By default libsdl2-native will be built, if you want to use your host's libSDL instead of -# the minimal libsdl built by libsdl2-native then uncomment the ASSUME_PROVIDED line below. -#ASSUME_PROVIDED += "libsdl2-native" - -# You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds -# a handy set of menus for controlling the emulator. -#PACKAGECONFIG:append:pn-qemu-system-native = " gtk+" - -# -# Hash Equivalence -# -# Enable support for automatically running a local hash equivalence server and -# instruct bitbake to use a hash equivalence aware signature generator. Hash -# equivalence improves reuse of sstate by detecting when a given sstate -# artifact can be reused as equivalent, even if the current task hash doesn't -# match the one that generated the artifact. -# -# A shared hash equivalent server can be set with ":" format -# -#BB_HASHSERVE = "auto" -#BB_SIGNATURE_HANDLER = "OEEquivHash" - -# -# Memory Resident Bitbake -# -# Bitbake's server component can stay in memory after the UI for the current command -# has completed. This means subsequent commands can run faster since there is no need -# for bitbake to reload cache files and so on. Number is in seconds, after which the -# server will shut down. -# -#BB_SERVER_TIMEOUT = "60" - -# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to -# track the version of this file when it was generated. This can safely be ignored if -# this doesn't mean anything to you. -CONF_VERSION = "2" - -# -# Enable local PR server -# -PRSERV_HOST = "localhost:0" - -# -# Some libraries and packages are covered by NXP EULA -# -#ACCEPT_FSL_EULA = "1" diff --git a/sdk/mkproject.sh b/sdk/mkproject.sh index c4ac381c3..4f6c60305 100755 --- a/sdk/mkproject.sh +++ b/sdk/mkproject.sh @@ -28,7 +28,7 @@ MKP_NONE="\033[0m" MKP_CONFIGPATH="${MKP_SCRIPTPATH}/sources/meta-digi/sdk/config" # Blacklist platforms (not officially supported in a DEY release) -MKP_BLACKLIST_PLATFORMS="ccimx6qpsbc ccimx6sbc ccimx8mm-dvk ccimx8mn-dvk ccimx8mp-dvk ccimx8x-sbc-express ccimx8x-sbc-pro" +MKP_BLACKLIST_PLATFORMS="ccimx6qpsbc ccimx6sbc ccimx8mm-dvk ccimx8mn-dvk ccimx8x-sbc-express ccimx8x-sbc-pro" MKP_SETUP_ENVIRONMENT='#!/bin/bash