All Boundary board variants now use Boundary kernel version 4.14
Kernel based on NXP imx_4.14.x_2.0.0_ga kernel release
linux-boundary now pulls boundary_defconfig from git for simplicity.
Signed-off-by: Chris Dimich <chris.dimich@boundarydevices.com>
In upstream openembedded-core, the definition for the B variable moved from
u-boot.inc to u-boot-common.inc. None of the recipes in this layer use
upstream's u-boot-common.inc, so add the B to the *common* include files here
so u-boot continues to build. See:
http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-bsp/u-boot?id=26023b6b0f897842fd98b3e10a8acd5b3ad8f418&h=master
Fixes:
meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-boundary_2018.07.bb:do_compile) failed with exit code '1'
Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
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>
OE-Core commit 4cbb7392c729a2436c26308c2320fdae5c450d7a
bumps revision to 20190618 and also move package version
to git from 20190618.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
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 defaults were taken from linux-fslc
| commit 75de4ee0c2
| Author: Pierre-Jean Texier <pjtexier@koncepto.io>
| Date: Sat Feb 23 17:28:39 2019 +0100
|
| imx7s-warp: Add bcm43430 nvram config
|
| Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
With the next commit
| commit 5d88f226ed
| Author: Alex Gonzalez <alex.gonzalez@digi.com>
| Date: Tue Feb 26 10:29:15 2019 +0100
|
| linux-fslc: ccimx6ul: Adapt to v4.20
|
| * Adapt patches to v4.20
| * Remove patches that are already included in the v4.20 kernel
|
| Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
linux-fslc moved to 4.20 and patches were adjusted.
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
The ConnectCore 6UL SBC Pro has a Wi-Fi interface with support for both
station and softAP modes.
This commit adds an interfaces file that defines a wlan0 interface for the
station mode, a wlan1 interface for the softAP mode.
Note that for softAP functionality to work, MAC addresses for the virtual
wireless interfaces need to be programmed in the uboot environment with:
env set wlan1addr aa:cc:cc:xx:yy:zz
env set wlan2addr aa:cc:cc:xx:yy:zz
env set wlan3addr aa:cc:cc:xx:yy:zz
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The ConnectCore 6UL SBC Express has a Wi-Fi interface with both station
and softAP functionality. This interfaces file adds the wlan0 interface for
station and wlan1 interface for softAP.
Note that for softAP functionality to work, MAC addresses for the virtual
wireless interfaces need to be programmed in the uboot environment with:
env set wlan1addr aa:cc:cc:xx:yy:zz
env set wlan2addr aa:cc:cc:xx:yy:zz
env set wlan3addr aa:cc:cc:xx:yy:zz
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The ConnectCore 6UL System-On-Module comes on different hardware
variants. This commit adds support for the wireless variant with
Qualcomm's QCA6564 WiFi / Bluetooth chipset.
* Modifies the device tree to add the SDIO wireless interface
* Patches the Linux kernel with QCA6564 specific feature additions
* Adds the unused HOSTAP module to the configuration so that the WEXT
config option is selected, even though the module won't be added to
to the target. Out-of-tree drivers have no way of selecting the legacy
WEXT support needed for the QCA6564.
* Removes the probe locking feature from the configuration as the
QCA6564 driver is not as well designed and it oops with warnings:
* Configure Bluetooth RFCOMM support in the kernel
* Sets the quality of the RNG so that it can be used by the kernel
[ 19.479089] ============================================
[ 19.484423] WARNING: possible recursive locking detected
[ 19.489761] 4.19.5-fslc+g093a10401c15 #1 Tainted: G O
[ 19.496135] --------------------------------------------
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This new package contains udev rules for the Digi International SOMs and
SBCs.
It initially contains only rules for the qca6564 Wi-Fi and BT and for the
ccimx6ul SOM, but it will get extended to cover other interfaces and
SOMs.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
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 project now expects contributions being made through
GitHub's pull-request feature. Reflect that in the README.
Text mostly taken from the README in meta-qt5.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
The ConnectCore 6UL SBC Pro has two wired ethernet interfaces. This commit
adds an interfaces file with both eth0 and eth1 interfaces.
Note that the ethernet interface that is enabled in U-Boot is the eth1
interface in the Linux kernel.
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>
Generalize the boot script used to boot Linux so that it can be shared
by multiple ConnectCore 6UL SOM based boards.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Adapt the interfaces file to the single wired ethernet available on the
ConnectCore 6UL SBC Express board.
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>
The ConnectCore 6UL SOM and SBC Express are already included in upstream
v4.19.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The ConnectCore 6UL Single Board Computer (SBC) Express contains the
ConnectCore 6UL System-On-Module.
Its hardware specifications are:
* 256MB DDR3 memory
* 256MB NAND flash
* Single Ethernet
* USB Host and USB-OTG
* MicroSD external storage
* Groove connectors and Raspberry Pi Hat compatible expansion heade
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-express
The ConnectCore 6UL SBC Express includes a ConnectCore 6UL
System-On-Module with the following specification:
* Based on a NXP i.MX6UL SoC
* Industrial temperature ranges (-40ºC to +85ºC)
* Up to 1GB DDR3 memory
* Up to 2GB NAND flash
* Dual Ethernet
* On module 802.11 WiFi and Bluetooth 4.2 (QCA6564)
* On module NXP Kinetis KL03
* On module Microchip ATECC508A crypto element
More details about the SOM can be found at:
https://www.digi.com/products/embedded-systems/system-on-modules/connectcore-for-i-mx6ul
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The support for the ConnectCore 6UL SOM and SBC Express is available in
v4.19 so it is added as patches here.
The GPMI BCH layout change is needed to match the kernel with the
NXP IMX vendor based U-Boot used in the ConnectCore 6UL SOM.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
This vendor U-Boot is based on v2017.03 and currently supports two
ConnectCore 6UL memory variants, 256MB and 1GB.
To program this U-Boot from a running TFTP server
type the following at the U-Boot prompt:
env set ipaddr <target IP address>
env set serverip <TFTP server IP address>
update linux tftp <filename>
Where filename is:
* u-boot.imx-ccimx6ulstarter - for 256MB variants
* u-boot.imx-ccimx6ulstarter1GB - for 1GB variants
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
This patch adds a new boot.ubifs image type that is programmed into the
boot partition of the NAND based ConnectCore modules.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
I observed a following build issue:
| ***
| *** Can't find default configuration "arch/../configs/colibri_imx7_emmc_defconfig"!
| ***
| scripts/kconfig/Makefile:128: recipe for target 'colibri_imx7_emmc_defconfig' failed
it's due to the colibri_imx7_emmc_defconfig does not exist in the
source, because u-boot-toradex and u-boot-fw-utils are not built from
same source. so the toradex machine specific uboot configs do not
present in the default u-boot-fw-utils source.
To fix it, a new u-boot-toradex-fw-utils recipe is added, it uses the
same source with u-boot-toradex, some common code is split out to
u-boot-toradex.inc, to be shared by both u-boot-toradex and
u-boot-toradex-fw-utils.
And we need set PREFERRED_PROVIDER and PREFERRED_RPROVIDER in machine
configs to u-boot-toradex-fw-utils.
Some files derive from u-boot-toradex-fw-utils recipe of:
git://git.toradex.com/meta-toradex-nxp.git
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
