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>
We now choose the BSP in a generic way and this commit changes the
machines to use the new mechanism setting it to mainline one.
Following changes are changed:
- imx6qdl-pico
- imx6ul-pico
- imx7d-pico
- imx7s-warp
- wandboard
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The recipe seems abandoned as their U-Boot is not update for ages, so we
are dropping it for now. If desired, it can be reverted once updated.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
After discussing this in OE-Core we are renaming it so it follows same
naming pattern as u-boot-default-env.
Fixes: 80be160 (u-boot-script-toradex: Set virtual/bootscript as provider)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Add virtual/bootscript to PROVIDES variable to make easier to use other
boot script just changing PREFERRED_PROVIDER_virtual/bootscript variable.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Rework recipe changing do_mkimage task, adding a do_install task and
changing do_deploy to output boot.scr file using machine name appended.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
With U-Boot 2019.07 booting from block devices is implemented with distro_bootcmd
needing an U-Boot script boot.cmd/scr.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
The new revisions of the SoM use the Atheros QCA9377 WiFi chip and to
allow its use out of box we need to add the firmware for the default
installation set.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
We have been carrying this machine for a while to easy the transition to
the nitrogen6x and now it is time to drop it.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Change-Id: I99b014cc5418c83fd2229645bdd76669341abf38
The machines using raw NAND flash need a binary which prepends u-boot.imx
with 1k byte for easier flashing.
With u-boot-toradex_2019.07 the u-boot-nand.imx target no longer exists.
so build that binary separately in do_configure.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
The previous commit adds machine file colibri-imx7-emmc that is used for
Colibri iMX7 with eMMC device, as the current colibri-imx7 is for
Colibri iMX7 with NAND device rename machine file accordingly.
Add colibri-imx7 to MACHINEOVERRIDES to maintain compatibility with
recipes that need to handle with the old name.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
A regress was introduced by me in commit 9a96fb93:
[ meta: change "+=" to "_append" for use-mainline-bsp overrides ]
a "+=" operator was changed to "_append" in that commit which is wrong
because that makes some non-existing dtb files being put into
KERNEL_DEVICETREE, hence leads build issue for mainline kernel.
Drop the "_append", change "+=" to "=" would be enough.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
At least since 4.14 all device trees are available in upsteram Linux
as well so drop the unnecessary use-mainline-bsp override.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
The "KERNEL_DEVICETREE_use-mainline-bsp +=" would override any other
assignment like:
- "KERNEL_DEVICETREE +="
- "KERNEL_DEVICETREE ="
- "KERNEL_DEVICETREE ?="
- "KERNEL_DEVICETREE ??="
change it to "_append" could fix the problem.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
meta-freescale commit 6be9d197386b5c3bd72023981df805d42f87684c
renamed imx-uboot-spl-bootpart.wks to imx-uboot-spl-bootpart.wks.in
The .in extension in wks files allows bitbake variables to be used in
kickstarter files. Set WKS_FILES for all machines to match this new
filename.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Since DM conversion, we have to adjust the binary name.
Also changes wks file for fix generation image
Signed-off-by: Joris Offouga <offougajoris@gmail.com>
Add machine definition forimx6qdl-pico board.
For more information about this SOM, please visit:
https://www.technexion.com/products/pico-compute-modules/detail/PICO-IMX6
This machine definition support PICO-DWARF, PICO-HOBBIT, and PICO-NYMPH baseboards.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
The ConnectCore 6UL SOM contains a Qualcomm QCA6564A wireless and Bluetooth
chipset with the following features:
* Dual band 5GHz 802.11ac or 2.4/5GHz 802.11n support
* Open, WPA and WPA2 personal and enterprise authentication
* AES/TKIP encryption
* Station, softAP and Wi-Fi direct modes
* FCC compliant US regulatory domain support
* Bluetooth 4.2, backwards compatible with older standard revisions
This commit builds an out-of-tree driver for it as well as installs
firmware files for both Wi-Fi and Bluetooth.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The ConnectCore 6UL Single Board Computer (SBC) Pro contains the
ConnectCore 6UL System-On-Module.
Its hardware specifications are:
* 256MB DDR3 memory
* On module 256MB NAND flash
* Dual 10/100 Ethernet
* USB Host and USB OTG
* Parallel RGB display header
* LVDS display header
* CSI camera
* GPIO header
* I2C, SPI, CAN headers
* PCIe mini card and micro SIM slot
* MicroSD external storage
* On board 4GB eMMC flash
* Audio headphone, line in/out, microphone lines
The build artifacts are:
U-Boot images: u-boot.imx
Linux partition image: <image name>.boot.ubifs
Root filesystem image: <image name>.ubifs
Root filesystem tarball (for network booting): <image name>.tar.bz2
To program a board from the U-boot prompt, copy the U-Boot, Linux and
root filesystem partition images to your TFTP server root and do:
env set ipaddr <target ip address>
env set serverip <TFTP server ip address>
update uboot tftp u-boot.imx
update linux tftp <image name>.boot.ubifs
update rootfs tftp <image name>.ubifs
More details about the SBC can be found at:
https://www.digi.com/products/embedded-systems/single-board-computers/connectcore-for-i-mx6ul-sbc-pro
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This commit prepares for the introduction of a second ConnectCore 6UL
System-On-Module based board by grouping the SOM configuration into its
own file avoiding code redundancy.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
