diff options
author | Fabio Estevam <fabio.estevam@nxp.com> | 2018-03-09 08:25:00 -0300 |
---|---|---|
committer | Stefano Babic <sbabic@denx.de> | 2018-03-09 13:04:02 +0100 |
commit | b5b0e4e351e20a606de22db6a56ad6bc1e2aa8fd (patch) | |
tree | 87d08c5b06ed3b852f175120e31a5cec5bd6671c /scripts | |
parent | 5e62f828256d66e2b28def4f9ef20a2a05c2d04f (diff) | |
download | u-boot-b5b0e4e351e20a606de22db6a56ad6bc1e2aa8fd.tar.gz |
imximage: Remove failure when no IVT offset is found
Sometimes imximage throws the following error:
CFGS board/freescale/vf610twr/imximage.cfg.cfgtmp
CFGS board/freescale/vf610twr/imximage.cfg.cfgtmp
MKIMAGE u-boot-dtb.imx
Error: No BOOT_FROM tag in board/freescale/vf610twr/imximage.cfg.cfgtmp
arch/arm/mach-imx/Makefile:100: recipe for target 'u-boot-dtb.imx' failed
Later on, when running mkimage for the u-boot.imx it will succeed in
finding the IVT offset.
Looks like some race condition happening during parallel build when
processing mkimage for u-boot-dtb.imx and u-boot.imx.
A proper fix still needs to be implemented, but as a workaround let's
remove the error when the IVT offset is not found.
It is useful to have such message, especially during bring-up phase,
but the build error that it causes is severe, so better avoid the
build error for now.
The error checking can be re-implemented later when we have a proper
fix.
Reported-by: Breno Lima <breno.lima@nxp.com>
Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions