This is a new intermediate file that will be reused in every iteration if it's
not removed, causing all imx-boot images to have the same U-Boot binary.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This reflects the fact that the firmware is customized for Digi platforms. The
versioning still follows the one used by NXP in their recipe.
https://jira.digi.com/browse/DEL-6158
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These patches were originally introduced in the recipe because the DCD files
were needed by mkimage to create the final imx-boot binaries. Now they are
in the SCFW source code instead.
https://jira.digi.com/browse/DEL-6158
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The "sha384sum" tool included in the coreutils package is needed by mkimage
when creating the imx-boot image.
https://jira.digi.com/browse/DEL-6158
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Otherwise, the default imx-boot images will include the Cortex M4 demo.
https://jira.digi.com/browse/DEL-6158
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These adaptations include changing the mkimage targets and removing any
handling of the DCD files, since they are now included in the SCFW. Note that
these changes break support for step A0 of the silicon.
The md5sum of the imx-sc-firmware tarball will be updated once the step B0 CPUs
are ready.
https://jira.digi.com/browse/DEL-6158
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
When the imx-boot recipe is added in EXTRA_IMAGEDEPENDS the
license file is being referenced in image postcommand
write_deploy_manifest, but the licenses of the dependant
packages are missing. This leads to the license files of the
recipes to be missing when write_deploy_manifest runs,
causing build errors to appear.
https://jira.digi.com/browse/DEL-6251
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Generalize DCD patch to be agnostic of the platform and modify the imx-boot
recipe to depend only on the memory configuration instead of the platform name.
https://jira.digi.com/browse/DEL-6205
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This way, customers are less likely to flash the plain u-boot by accident
instead of imx-boot. Also, have the imx-boot recipe look for the u-boot files
in the imx-boot-tools directory.
https://jira.digi.com/browse/DEL-6185
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since this binary (u-boot-atf.bin) wasn't being deleted, the mkimage makefile
was using the one from the previous iteration, causing the 1GB imx-boot to
contain the 2GB U-Boot.
https://jira.digi.com/browse/DEL-6094
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Also, move all of the recipe's patches from the .bbappend file to the .bb file,
because the .bb file's modifications depend greatly on said patches.
https://jira.digi.com/browse/DEL-6085
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This package is the combination of U-Boot and the other i.MX firmware binaries.
In our case, these binaries are: the SCFW, the ATF and the DCD.
The recipe has been ported from the meta-fsl-bsp-release repo, with a couple of
important changes:
* Support for our platform (based on the mx8qxpa0, which uses A0-specific
parameters for mkimage and appends the DCD explicitly)
* Support for multiple UBOOT_CONFIG values (NXP only uses one UBOOT_CONFIG
string per platform; so the compile, install and deploy functions had to
be tweaked to build both 1GB and 2GB variants for our platform).
Our DCD patch used in imx-mkimage is also used, since both packages share the
same repo and imx-boot is the one responsible for generating the final,
bootable image.
https://jira.digi.com/browse/DEL-6085
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Gabriel Valcazar
Arturo Buzarra