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>
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>
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>
This adds the bcm4339 nvram configuration which allows the use of WiFi
connectivity out of box, using latest Linux FSLC release.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Tested:
* HDMI
* MMC
* eMMC (mounted)
* NAND (kernel log - no partitions)
* RTC
* USB-Host
* Ethernet
* WiFi
* Bluetooth
* serial console
Open:
* HDMI sound
* Onboard sound (ALSA looks good has no phones connected yet)
* User-Button
* USB-OTG
Cannot test:
* CAN
Additional comments:
1. The way, the dt-files are copied into the kernel sources is not state of the
art. But since this is some work in progress it makes my worklow a lot easier.
2. My target is to send dt-files to mainline kernel but they are not yet ready
for that 'environment'. Once done I'll send backports to meta-fslc and 1.
can go.
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
It is mx6 default but gets lost for use-mainline-bsp override:
In meta-freescale/conf/machine/include/imx-base.inc
MACHINEOVERRIDES_EXTENDER_FILTER_OUT_use-mainline-bsp contains
all mx6 variants. So all mx6.. overrides are are filtered which
is usually fine but not for DEFAULTTUNE: Without this patch
armv7hf-neon is build.
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The MACHINE_FEATURES definition usually goes near the end of machine
file as it makes easier to compare the contents related to kernel,
bootloader and other general aspects of BSP.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
