I've just had a go at compiling and testing the various u-boot configurations on a KT2 and I get a similar error when trying to use imx60_wario_mfgtool config. It might be that MfgTool does things in a slightly different way to imx_usb_loader? I've never used it so can't say for sure.
However, I'm able to create working builds using the
imx60_wario and
imx60_wario_bist configs that are loadable using imx_usb_loader using the commands below:
Code:
# for production u-boot
CROSS_COMPILE=arm-kindlepw2-linux-gnueabi- ARCH=arm TYPE=prod make distclean
CROSS_COMPILE=arm-kindlepw2-linux-gnueabi- ARCH=arm TYPE=prod make imx60_wario_config
CROSS_COMPILE=arm-kindlepw2-linux-gnueabi- ARCH=arm TYPE=prod make
mv u-boot.bin u-boot_prod.bin
# for bist
CROSS_COMPILE=arm-kindlepw2-linux-gnueabi- ARCH=arm TYPE=bist make distclean
CROSS_COMPILE=arm-kindlepw2-linux-gnueabi- ARCH=arm TYPE=bist make imx60_wario_bist_config
CROSS_COMPILE=arm-kindlepw2-linux-gnueabi- ARCH=arm TYPE=bist make
mv u-boot.bin u-boot_bist.bin
Make sure that you're setting the TYPE env variable correctly as it changes which LD script is used:
Code:
# boards/imx50_yoshi/config.mk
ifeq ($(TYPE),prod)
LDSCRIPT := $(SRCTREE)/board/$(VENDOR)/$(BOARD)/u-boot.lds
TEXT_BASE = 0xF8007000
else
LDSCRIPT := $(SRCTREE)/board/$(VENDOR)/$(BOARD)/bist.lds
TEXT_BASE = 0x79800000
endif