summaryrefslogtreecommitdiffstats
path: root/recipes-bsp/imx-mkimage
Commit message (Collapse)AuthorAgeFilesLines
* imx-mkimage: use mkimage tool from sysrootAndrey Zhizhikin2021-10-253-3/+84
| | | | | | | | | | | | mkimage tool is provided as a part of sysroot and should not be used as a local copy, since it contains runtime dependencies which local copy does not account for. Drop the local copy on mkimage, introduce the patch that fixes mkimage invocations in build system. Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com> (cherry picked from commit c59f817b0d1ee70ef224405ff8acd31e0743ed91)
* imx-mkimage: update to 5.10.52-2.1.0Andrey Zhizhikin2021-10-251-2/+2
| | | | | | | | | | | | | | | | | | Following commits are included in this update: ---- 1112c88 ("MLK-25706: iMX8M: soc: fix support to override u-boot DTB file name") 5af389c ("iMX8ULP: support xip for m33 and add README") 37faca4 ("MLK-25490 imx8m: Remove unused DDR registers file") 4e241ae ("iMX8M: Support to override u-boot DTB file name") 7e5ff11 ("imx8ulp: Workaround ATXP flash header for dual boot") 394188b ("Support iMX8ULP secure boot") 32bf25f ("imx8ulp: Add flash_dualboot_m33 to generate M33 container") aa44b32 ("imx8ulp: Move M33 image before AP image for single boot") ad70dd2 ("imx8qm: cockpit: fix Linux image name in nightly targets") ---- Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com> (cherry picked from commit f0092d11699caf95f43aa8acfb2ba7d166608859)
* layer: Convert to new override syntaxKhem Raj2021-08-121-11/+11
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* imx-mkimage: Drop dcd files from deploy folderTom Hochstein2021-07-161-14/+1
| | | | | | The dcd files are apparently not needed and can be dropped. Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
* imx-mkimage: Upgrade to 5.10.35-2.0.0 releaseTom Hochstein2021-07-161-4/+3
| | | | Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
* imx-mkimage: fix node name generationsAndrey Zhizhikin2021-04-222-1/+170
| | | | | | | | | | | | | FIT node names generated by imx-mkimage script are not conformant to the latest version of mkimage tool and are caused to be skipped at parsing stage, leading to build errors. Introduce the patch to correct generated node names (drop unit address fields and replace with names-only). Fixes: #741 https://github.com/Freescale/meta-freescale/issues/741 Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com> Cc: Tom Hochstein <tom.hochstein@nxp.com>
* imx-boot: Add dependency on xxd-nativeNathan Rossi2021-04-201-0/+2
| | | | | | | | | | | | | | | | | | | | | | | The fspi_packer.sh script uses xxd in order to generate the SPI flash configuration header. If xxd is missing no error is produced and the output image does not work. The log however contains the following error messages (e.g. for iMX8MP flash_evk_flexspi target): ./../scripts/fspi_packer.sh ../scripts/fspi_header ./../scripts/fspi_packer.sh: 5: xxd: not found dd: failed to open 'qspi-header': No such file or directory 3333+1 records in 3333+1 records out 3413776 bytes (3.4 MB, 3.3 MiB) copied, 0.00566483 s, 603 MB/s dd: failed to open 'qspi-header.off': No such file or directory cp: cannot stat 'qspi-header.off': No such file or directory rm: cannot remove 'qspi-header*': No such file or directory F(Q)SPI IMAGE PACKED xxd is not in HOSTTOOLS or HOSTTOOLS_NONFATAL, as such the explicit DEPENDS is required. Signed-off-by: Nathan Rossi <nathan.rossi@digi.com>
* imx-boot: drop compatibility with mainline bspAndrey Zhizhikin2021-03-171-1/+1
| | | | | | | | | | | | | Mainline BSP switches from using imx-boot package, which provides the boot container for mx8 derivatives, to the boot container provided as a part of u-boot package and usage of imx-boot-container class. Drop the compatibility with mainline BSP from the recipe, and let derivatives that are built with it to integrate support of new boot container mechanism. Fixes: 6fc0971c ("imx-mkimage: allow to be used with mainline bsp for mx8m)" Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
* layer: license: fix GPL-2.0 license identifiers changed upstreamAndrey Zhizhikin2021-02-242-2/+2
| | | | | | | | | | | | | | | Upstream commit 2456f523cf ("licenses: Update license file to match current SPDX names") deprecated the usage of GPL-2.0 SPDX identifier, removed GPL-2.0 license file and replaced it with GPL-2.0-only SPDX identifier and text file. Adjust layer recipes to use new SDPX identifier and text file. imx-test recipe has license has been re-captured to use GPL-2.0-or-later identifier, since it is required by the license text accompanying the source code repository through "GPLv2 or later" statement in COPYING file. Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
* imx-mkimage: : update to 5.4.70_2.3.0Max Krummenacher2021-02-011-3/+3
| | | | Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
* imx-mkimage: Reorder inheriting native classKhem Raj2021-01-281-1/+1
| | | | | | | Fixes imx-mkimage-git: imx-mkimage: native/nativesdk class is not inherited last, this can result in unexpected behaviour. [native-last] Signed-off-by: Khem Raj <raj.khem@gmail.com>
* imx8qxpmek: Update the i.MX 8QXP default build to rev C0Tom Hochstein2021-01-212-2/+6
| | | | | | | | | | The current machine configuration support for 8QXP MEK is for rev B0 silicon. Support for rev C0 is implemented using a machine override `mx8qxpc0`. Update the default build to rev C0 silicon. Support for rev B0 is provided with a new machine feature `soc-revb0`. The machine override is removed. Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
* imx-mkimage: allow to be used with mainline bsp for all mx8 machinesGary Bisson2020-12-301-12/+0
| | | | Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
* imx-mkimage: allow to be used with mainline bsp for mx8mAndrey Zhizhikin2020-12-111-20/+14
| | | | | | | | | | | | | | | | | | | | | | | | | imx-boot provides a boot container, which is required for mx8m family of SOCs to execute a boot sequence. Allow the imx-boot to generate boot container for Mini, Nano and Plus SOCs by adding use-mainline-bsp to the list of compatible machines. In order to accommodate new boot container generation model, former SOC_TARGET variable has been renamed to IMX_BOOT_SOC_TARGET and should be explicitly defined in the target machine recipes. This is done to indicate that even if the mx8mm machine is finter out from MACHINEOVERRIDES by extender filter - this recipe picks up a proper target definition for boot container construction. Default ATF binary image is also now based on ATF_PLATFORM, which is explicitly defined in the machine configuration file. Current support includes only Mini, Nano and Plus SOCs from i.MX8M family, and additions of further machines would require the definition of ATF_PLATFORM and IMX_BOOT_SOC_TARGET to be moved out from imx-boot recipe to a machine configuration file. Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
* imx-mkimage: Update to imx_5.4.47_2.2.0 branchCristinel Panfir2020-10-201-2/+2
| | | | Signed-off-by: Cristinel Panfir <cristinel.panfir@nxp.com>
* imx-boot: allow for additional/different u-boot device-treeMax Krummenacher2020-10-021-3/+3
| | | | | | | | | | | | | | | | With the current call to imx-mkimage and SOC_TARGET = "iMX8M" the u-boot device tree file name is set to $(PLAT)-evk.dtb in iMX8M/soc.mak which happens to match ${UBOOT_DTB_NAME} if building for an NXP machine. Setting the dtbs environment variable to ${UBOOT_DTB_NAME} makes the build succeed also for other machines. In the hardcoded version $(dtbs) is an intermediate file and gets delete as the last step of make. Thus for several make targets we have to redo the copy step before each make invocation or the second one will fail as the device tree file is then missing. Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
* imx-mkimage: upgrade to version 1.0Andrey Zhizhikin2020-09-233-23/+61
| | | | | | | | This upgrade contains of following modifications: - introduce new i.MX8 derivatives; - upgrade imx-mkimage recipe to match NXP release; Signed-off-by: Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
* imx-boot: fix mkimage_uboot linking issueMing Liu2020-05-051-0/+2
| | | | | | | | | | | In imx-boot's Makefile, it downloads a native tool mkimage_uboot and executes it, but this native tool requires libssl.so.1.1, which is in ${STAGING_LIBDIR_NATIVE}, we need set LD_LIBRARY_PATH to include it, or it might run into following errors: | ./mkimage_uboot -E -p 0x3000 -f u-boot.its u-boot.itb | ./mkimage_uboot: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory Signed-off-by: Ming Liu <ming.liu@toradex.com>
* imx-mkimage: update to use new kernel 5.4.3-1.0.0 branchAndrey Zhizhikin2020-04-161-1/+1
| | | | | | | Update recipe to pull sources from new branch, which is aligned with new kernel version 5.4.3 Signed-off-by: Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
* u-boot: Split out u-boot toolsJoshua Watt2020-03-301-1/+2
| | | | | | | | | | | | | | | | | | | Splits out the IMX u-boot tools build to it's own recipe. This is required because these are native tools and thus need to be in a -native recipe to be properly relocated (instead of being built as part of the target u-boot-imx recipe). If the tools aren't built in a -native recipe, then the mkimage tool will contain a hard coded path to the uninative program loader from the sandbox where it was first built and this will not get corrected when restored from sstate. The result is that the mkimage_uboot executable can't run because it's looking for a hard coded program loader that does not exist, resulting in strange build errors like: ./mkimage_uboot: Command not found even though the executable is obviously in the correct location. Signed-off-by: Joshua Watt <Joshua.Watt@garmin.com>
* imx-boot: add support for i.MX8M Nano EVKAndrey Zhizhikin2020-01-081-1/+4
| | | | | | | Add ATF and platform machine definitions for i.MX8M Nano SoC in order to generate boot images. This mainly follows the setup done for i.MX8M Mini. Signed-off-by: Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
* imx-mkimage_git.inc: Update to 4.19.35_1.1.0Cristinel Panfir2019-12-191-2/+2
| | | | | | | | - Enable dual bootloader for imx8m - Add functionality to parse 8/8X container headers - Update the build target for different ddr firmware Signed-off-by: Cristinel Panfir <cristinel.panfir@nxp.com>
* imx-boot: Use imx-seco firmwareMihai Lindner2019-12-161-3/+3
| | | | | | Account for imx-seco split from firmware-imx. Signed-off-by: Mihai Lindner <mihai.lindner@nxp.com>
* optee: Add support for optee imx fork to imx8mqevkPeter Griffin2019-11-081-1/+14
| | | | | | | | optee imx fork like most other imx forked components is more fully featured for imx devices and supports things like CAAM accleration. Signed-off-by: Peter Griffin <peter.griffin@linaro.org>
* imx-boot: Pass DTB names to makeJoshua Watt2019-09-041-1/+1
| | | | | | | Passes the name of the DTBs to be built to make. This allows alternate DTBs to be built instead of assuming the default Signed-off-by: Joshua Watt <Joshua.Watt@garmin.com>
* imx-boot: Remove i.MX 8QXP u-boot configurationTom Hochstein2019-06-131-8/+0
| | | | | | IMXBOOT_TARGETS is now defined in imx8qxpmek.conf. Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
* imx-boot: Drop independent DCD componentTom Hochstein2019-06-131-8/+0
| | | | | | The DCD component has moved into the firmware. Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
* imx-boot: Add DisplayPort firmware for i.MX 8MTom Hochstein2019-06-131-2/+4
| | | | | | | Also, use explicit names to help remove surprises due to unexpected changes. Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
* imx-boot: Upgrade to L4.14.98-2.0.0_gaTom Hochstein2019-06-131-6/+9
| | | | | | | | - Rename atf binary - Update intermediate name for u-boot nodtb binary - Improve whitespace for file copies Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
* imx-mkimage: Upgrade to L4.14.98-2.0.0_gaTom Hochstein2019-06-131-3/+3
| | | | Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
* imx-boot: drop dependency to u-bootStefan Agner2019-05-201-1/+0
| | | | | | | | The recipe do_compile task depends on virtual/bootloader which makes sure the necessary dependencies are available once imx-boot do_compile is executed. Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
* imx-boot: imx-mkimage: do not compile with -staticMax Krummenacher2019-01-292-2/+2
| | | | | | | | | | | E.g. Fedora doesn't install glibc-static by default and the yocto prerequisites do not mandate installing it. Rather than requiring glibc-static drop linking with -static. Works around: | .../build/tmp/hosttools/ld: cannot find -lc Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
* imx-boot: drop adding m4 binaries to the boot containerMax Krummenacher2019-01-291-9/+3
| | | | | | The recipe which builds or injects the m4 binaries does not yet exist. Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
* meta: drop imx-m4-demos referencsMing Liu2019-01-291-9/+0
| | | | | | | | There is not a imx-m4-demos recipe at all, drop its references. They could be added back once the recipe is added. Signed-off-by: Ming Liu <liu.ming50@gmail.com>
* imx-boot: Fix the symbolic link filename to imx-bootDaiane Angolini2019-01-101-1/+1
| | | | | | | | | Fix the error: | File "/media/daiane/TRIFORCE/yocto/master/sources/poky/scripts/lib/wic/filemap.py", line 132, in _open_image_file | % (self._image_path, err)) | wic.filemap.Error: cannot open image file '/media/daiane/TRIFORCE/yocto/master/build/tmp/deploy/images/imx8mmevk/u-boot.imx': [Errno 2] No such file or directory: '/media/daiane/TRIFORCE/yocto/master/build/tmp/deploy/images/imx8mmevk/u-boot.imx' Signed-off-by: Daiane Angolini <daiane.angolini@nxp.com>
* imx-boot: Add recipe for i.MX 8 boot partition packagesTom Hochstein2018-12-131-0/+191
| | | | Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
* imx-mkimage: Add recipe for i.MX 8 boot partition packagesTom Hochstein2018-12-132-0/+46
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>