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>
Add the git repository in the recipe in order to build u-boot for
Gateworks imx6 boards.
Signed-off-by: Sandra Tobajas <sandra.tobajas@savoirfairelinux.com>
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>
Now that the kernel headers are fixed to 4.9 in meta-freescale, 3rd
party kernel better match that same version.
We currently do not have the bandwidth to maintain such RT version so
remove it to avoid confusion.
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Update with the ARMv7 defconfig to enable IPU and display
Signed-off-by: Ken Lin <ken.lin@advantech.com>
Signed-off-by: Ken Lin <yungching0725@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
It fails to build for non-arm machines anyway since it does not provide
the needed env file for anything other than arm and aarch64
Let cross version build too
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
From: Ian Coolidge <ian@boundarydevices.com>
Compatible with nitrogem8m board
Blog post: https://boundarydevices.com/u-boot-v2018-07/
Signed-off-by: Ian Coolidge <ian@boundarydevices.com>
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Changelog summary:
- Includes stable v4.9.126
- Adds OV5640 MIPI support for our Nitrogen8M
- Improves SDIO perf for WiFi/BT & eMMC
- Improves SPI display support
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
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>
* Licence
have no idea what changed in the license file README. For
plausibility a grep here on checksum a2c678cfd4a4d97135585cad908541c6 unveiled:
recipes-bsp/u-boot/u-boot-boundary-common_2017.07.inc
recipes-bsp/u-boot/u-boot-toradex.inc
recipes-bsp/u-boot/u-boot-boundary-common_2017.03.imx8m.inc
All these set license to GPLv2+ - so we should be fine.
* Fix-the-compile-issue-under-gcc6.patch
Later versions of u-boot support a version independent gcc header file
making the patch obsolete
* COMPATIBLE_MACHINE
resrict to imx6qdl-variscite-som
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>
Currently, the recipe uses the script found relative to ${THISDIR}.
Using ${THISDIR} prevents other recipes from using FILESEXTRAPATHS to
overwrite the default boot script. This commit fixes this by using
${WORKDIR} instead.
Signed-off-by: Jean-François Têtu <jean-francois.tetu@savoirfairelinux.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
commit 040e4f031f2dc581c48253405da9036def035b68 (HEAD -> dev, ssh-push/master-next, ssh-push/master)
Author: Max Krummenacher <max.krummenacher@toradex.com>
Date: Mon Jul 23 22:13:19 2018 +0200
dtc-145: Deploy renamed binary only and add new class
dtc-145-native is used by older U-Boot recipes. U-Boot only depends on
the native dtc binary. So, to not clash with files from the regular dtc native
build do only install the dtc binary renamed to dtc-145. Also, create
a new class to handle with dtc-145 dependency.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
From meta-freescale commit:
commit 040e4f031f2dc581c48253405da9036def035b68
Author: Max Krummenacher <max.krummenacher@toradex.com>
Date: Mon Jul 23 22:13:19 2018 +0200
dtc-145: Deploy renamed binary only and add new class
dtc-145-native is used by older U-Boot recipes. U-Boot only depends on
the native dtc binary. So, to not clash with files from the regular dtc native
build do only install the dtc binary renamed to dtc-145. Also, create
a new class to handle with dtc-145 dependency.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Since master now uses dtc 1.4.6, need to use the 1.4.5 in order to
build older U-Boot versions like 2017.03.
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
The Toradex Colibri iMX6ULL computer module is based on i.MX 6ULL.
The Colibri iMX6 is a member of the pincompatible Colibri family.
They feature on module RAM and NAND, Ethernet PHY, Resistive Touch
Controller and optional Wi-Fi module.
For additional specifications please visit:
https://www.toradex.com/de/computer-on-modules/colibri-arm-family/nxp-imx6ull
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
imx-base.inc unconditionally sets SERIAL_CONSOLE to ttymxc0.
So assigning with ?= here to the same value does nothing and may
confuse if someone wants to assign to a different UART.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
