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>
Add custom imx-atf applicable only to Nitrogen8m, Nitrogen8mm and
Nitrogen8mn, which pulls from Boundary's imx-atf. This is done because
meta-freescale imx-atf_2.0 sets the RDC so that UART4 is only accessible
by M4 core.
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 script is not required as libubootenv handles the unlock
automatically, so we can drop it now.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Now we are using libubootenv and dropped the u-boot-toradex-fw-utils, we
need to move the configuration file to the main recipe.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Now we are using libubootenv and dropped the u-boot-boundary-fw-utils,
we need to move the configuration file to the main recipe.
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>
This helps in making it layer work in multi-bsp environment
Fixes double staging errors like
DEBUG: Staging files from TOPDIR/build/tmp/work/raspberrypi4-yoe-linux-gnueabi/u-boot-script-toradex/2019.07-r0/deploy-u-boot-script-toradex to TOPDIR/build/tmp/deploy/images/raspberrypi4
ERROR: The recipe u-boot-script-toradex is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
TOPDIR/build/tmp/deploy/images/raspberrypi4/boot.scr
(matched in manifest-raspberrypi4-rpi-u-boot-scr.deploy)
Please verify which recipe should provide the above files.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
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>
Fix build for GCC >= 9 and remove patches that are no longer needed
Add EDP version of Nitrogen8M
Fix PMIC voltage issue for 8M Mini
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
8f0e253cbce configs/colibri_vf.h: drop sdboot in favour of distro_bootcmd
db553084910 colibri_vf_defconfig: enable part cmd
bc2f29bb15d colibri_vf_defconfig: refresh with savedefconfig
1a390a7be57 Fix typo in .gitlab-ci.yml
1f8c4198070 board: apalis_imx6: Add KSZ9131 phy skew settings
cc96ed419f7 drivers: net: phy: micrel_ksz90x1.c: Add basic support for KSZ9131
28491c802d3 net: phy: micrel: Use defines for PHY_IDs and MASK
eac7cda6283 gitlab-ci: Change stage name to build-uboot
677a5647d4b gitlab-ci: enable by building all toradex boards
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
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>
Update SPL USB ID for UUU to work on 8M Mini and 8M Nano
Update flashing script to ease U-Boot upgrade
Add touch command support to prepare for 4.19 kernel
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
This adds a usefull fw_env.config for colibri-imx7-emmc.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
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>
These patches are originally from meta-freescale, commit 075681e8 , and
were modified slightly to apply to kernel 4.14.
This fixes errors while building other modules, especially
kernel-module-imx-gpu-viv, which otherwise produces compile errors like:
| [...]tmp/work-shared/nitrogen8m/kernel-source/include/linux/module.h:131:6: error: 'init_module' specifies less restrictive attribute than its target 'gpu_init': 'cold' [-Werror=missing-attributes]
| 131 | int init_module(void) __attribute__((alias(#initfn)));
| | ^~~~~~~~~~~
| [...]tmp/work/nitrogen8m-poky-linux/kernel-module-imx-gpu-viv/6.4.0.p1.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:1445:1: note: in expansion of macro 'module_init'
| 1445 | module_init(gpu_init);
| | ^~~~~~~~~~~
| [...]tmp/work/nitrogen8m-poky-linux/kernel-module-imx-gpu-viv/6.4.0.p1.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:1411:19: note: 'init_module' target declared here
| 1411 | static int __init gpu_init(void)
| | ^~~~~~~~
| In file included from [...]tmp/work/nitrogen8m-poky-linux/kernel-module-imx-gpu-viv/6.4.0.p1.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_linux.h:61,
| from [...]tmp/work/nitrogen8m-poky-linux/kernel-module-imx-gpu-viv/6.4.0.p1.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:61:
| [...]tmp/work-shared/nitrogen8m/kernel-source/include/linux/module.h:137:7: error: 'cleanup_module' specifies less restrictive attribute than its target 'gpu_exit': 'cold' [-Werror=missing-attributes]
| 137 | void cleanup_module(void) __attribute__((alias(#exitfn)));
| | ^~~~~~~~~~~~~~
| [...]tmp/work/nitrogen8m-poky-linux/kernel-module-imx-gpu-viv/6.4.0.p1.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:1446:1: note: in expansion of macro 'module_exit'
| 1446 | module_exit(gpu_exit);
| | ^~~~~~~~~~~
| [...]tmp/work/nitrogen8m-poky-linux/kernel-module-imx-gpu-viv/6.4.0.p1.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:1437:20: note: 'cleanup_module' target declared here
| 1437 | static void __exit gpu_exit(void)
| | ^~~~~~~~
Signed-off-by: Carlos Rafael Giani <crg7475@mailbox.org>
