This commit fixes error on do_install task for u-boot-fslc.
The error occurs because u-boot.imx can't be found.
Signed-off-by: Vinicius Aquino <vinicius.aquino@ossystems.com.br>
Fix mistype in colibri-imx6ull machine include file when using nxp bsp.
Reported-by: Tomas Vilda
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
- Add the newly available device trees provided by the kernel update.
- Drop the prefered provider for u-boot-fw-utils, use libubootenv.
- Don't install epdc firmware, none of the machines supports epdc.
- Changed all maintainers to myself, Stefan left the company.
- Unify setting the preferred bootloader with IMX_DEFAULT_BOOTLOADER
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
See also commit 46c1c81 ("imx7s-warp: Set UBOOT_SUFFIX to imx").
Overwrite the new default from imx-base.inc.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Override the default imx-base.inc value that uses UBOOT_SUFFIX_pn-${IMX_DEFAULT_BOOTLOADER}
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
The weak assignment doesn't override the default imx-base.inc value, and
as the only bootloader provider is u-boot-toradex, we don't need to
allow override.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
The weak assignment doesn't override the default imx-base.inc value, and
as the only bootloader provider is u-boot-toradex, we don't need to
allow override.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
A change was made to meta-freescale to change how the bootloader was being
selected:
https://github.com/Freescale/meta-freescale/pull/696
As a result the choosing logic for the olinuxino MACHINEs was updated to
match.
Build tested for:
- imx233-olinuxino-maxi
- imx233-olinuxino-micro
- imx233-olinuxino-mini
- imx233-olinuxino-nano
Run tested on:
- imx233-olinuxino-maxi
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
In order to more easily update the uboot after flashing a yocto build,
add the generated uboot binary and upgrade uboot script to the boot
partition.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Update the linux-remarkable2 to use some patches on top of the
fslc-imx branch.
There are too many patches (about 25 and 35,000 lines) to store them all
here, so use a specific git repo for the linux-remarkable2 bb instead of
appending patches to the linux-fslc-imx bbappend.
Signed-off-by: Alistair Francis <alistair@alistair23.me>
In order to more easily update the uboot after flashing a yocto build,
add the generated uboot binary and upgrade uboot script to the boot
partition.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
In order to more easily update the uboot after flashing a yocto build,
add the generated uboot binary and upgrade uboot script to the boot
partition.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
In order to more easily update the uboot after flashing a yocto build,
add the generated uboot binary and upgrade uboot script to the boot
partition.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Add dedicated BOUNDARY_DEVICES_UBOOT_DEFCONFIG variable, as there can
be different board variants in which the defconfig needs to be
modified in the build.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Add dedicated BOUNDARY_DEVICES_UBOOT_DEFCONFIG variable, as there can
be different board variants in which the defconfig needs to be
modified in the build.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Add dedicated BOUNDARY_DEVICES_UBOOT_DEFCONFIG variable, as there can
be different board variants in which the defconfig needs to be
modified in the build.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Set a weak assignment for IMX_DEFAULT_BSP before include the
imx-base.inc to allow override IMX_DEFAULT_BSP in local.conf file.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
When removing the machine we ended not removing all files. This removes
all the related ones.
Fixes: e50d808 "ccimx6ul*: Drop unbuildable boards"
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Recipe of u-boot-karo has not been maintained for years; more recent
support does not cover the use of updated linux kernel and is not
compatible with dunfell.
Removed u-boot-karo, linux-karo and the machine configurations.
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: I02645c9f88e648c143b82c4baa89491a1baff934
The board is not building and received no maintenance, so it is being
removed along with linux-timesys that provides support for it.
kernel-module-mcc and libmcc2 were removed as they provided support
for pcm052 only.
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: I997059c1824484df8c11c9b31b2dae6e989430e7
With all required components as dependency added:
* rcw
* atf
* mc-utils
* u-boot
* linux
* wic template
... go ahead to enable building for Honeycomb or Clearfog LX2 if you are a
lucky one who could get one :)
Signed-off-by: Jens Rehsack <sno@netbsd.org>
The board are in unbuildable state for long time and they were
removed from U-Boot mainline in 2018 and nobody noticed so it
is clearly not in use.
This commit removes both boards and respective recipes from
the layer.
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: Ica122e72a0c357bba5924916c30a73d0874fae80
Old recipe had construction error due to virtual / kernel and updated linux 4.9 -> 5.4
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: I8d37a7766749421b41124ee5147fc3df65358edc
The pwm-buzzer, can, emmc and nandflash MACHINE_FEATURES are invalid and
as such should not be on the BSP. Remove them.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Change-Id: I577a9d0887a9520618188b39c0114b319a3d7217
Fixed the name of WKS_FILES, which was not found and
had an error during the build.
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: If51edd53b0f992858ad8289aed558f12d914aba0
Even with modifications, errors in the build of the image
persist. Since the board has not received updates in a long
time, it is being removed.
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: I8554a49ca9e34282d11c9613b35de4cb7f0aa181
The imx specific weston version which is otherwise set is not in
COMPATIBLE_MACHINE for Vybrids.
Prevents:
| NOTE: preferred version 8.0.0.imx of weston not available (for item weston)
| NOTE: versions of weston available: 8.0.0
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
We need to support both mainline and NXP BSP support, to allow that we
need:
- split generic and NXP BSP specific device trees
- avoid setting the default Linux kernel if we use mainline BSP
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
We need to support both mainline and NXP BSP support, to allow that we
need:
- split generic and NXP BSP specific device trees
- avoid setting the default Linux kernel if we use mainline BSP
This was applied for:
- colibri-imx7-emmc
- colibri-imx7-nand
Fixes: #78
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
This adds support for Kontron N63XX/N64XX SoM based boards and provides
following components:
- imx6ul-kontron machine definition
- u-boot-kontron recipe
- linux-kontron recipe
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Use UBOOT_CONFIG instead of UBOOT_MACHINE, as per matches imx8mnevk.
Define IMAGE_BOOTLOADER and IMXBOOT_TARGETS as per imx8mnevk.
Define DDR_FIRMWARE_NAME as per imx8mnevk.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Use UBOOT_CONFIG instead of UBOOT_MACHINE, as per imx8mmevk.
Define IMAGE_BOOTLOADER and IMXBOOT_TARGETS as per imx8mmevk.
Define DDR_FIRMWARE_NAME as per imx8mmevk.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Use UBOOT_CONFIG instead of UBOOT_MACHINE, as per imx8mqevk.
Define IMAGE_BOOTLOADER and IMXBOOT_TARGETS as per imx8mqevk.
Define DDR_FIRMWARE_NAME as per imx8mqevk.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
This fixes the following build error:
> Error, the PACKAGE_ARCHS variable (all any noarch ${PACKAGE_EXTRA_ARCHS_tune-cortexa53-crypto} nitrogen8m) for DEFAULTTUNE (cortexa53-crypto) does not contain TUNE_PKGARCH (${@bb.utils.contains('TUNE_FEATURES', 'aarch64', 'aarch64', '${ARMPKGARCH_tune-cortexa53-crypto}' ,d)}).Toolchain tunings invalid:
> Tuning 'cortexa53-crypto' has no defined features, and cannot be used.
Signed-off-by: Carlos Rafael Giani <crg7475@mailbox.org>
