This is broken ever since we switched to using U-Boot as first stage bootloader. Since no one seems to test this actively, let's just drop this entirely. There are other tools available for re-flashing the DB410c.
Signed-off-by: Stephan Gerhold <stephan.gerh...@linaro.org> --- board/qualcomm/dragonboard410c/dragonboard410c.env | 26 ---------------------- 1 file changed, 26 deletions(-) diff --git a/board/qualcomm/dragonboard410c/dragonboard410c.env b/board/qualcomm/dragonboard410c/dragonboard410c.env index 9d9a575a0c3f7a4739e4fb77a980d742e10510f5..57a30031f743f43d4a6389286b426b404d2f371b 100644 --- a/board/qualcomm/dragonboard410c/dragonboard410c.env +++ b/board/qualcomm/dragonboard410c/dragonboard410c.env @@ -1,30 +1,4 @@ /* SPDX-License-Identifier: GPL-2.0+ */ - -/* Does what recovery does */ -#define REFLASH(file, partnum) \ -part start mmc 0 partnum start && \ -part size mmc 0 partnum size && \ -tftp $loadaddr file && \ -mmc write $loadaddr $start $size && - -reflash= -mmc dev 0 && -usb start && -dhcp && -tftp $loadaddr dragonboard/rescue/gpt_both0.bin && -mmc write $loadaddr 0 43 && -mmc rescan && -REFLASH(dragonboard/rescue/NON-HLOS.bin, 1) -REFLASH(dragonboard/rescue/sbl1.mbn, 2) -REFLASH(dragonboard/rescue/rpm.mbn, 3) -REFLASH(dragonboard/rescue/tz.mbn, 4) -REFLASH(dragonboard/rescue/hyp.mbn, 5) -REFLASH(dragonboard/rescue/sec.dat, 6) -REFLASH(dragonboard/rescue/emmc_appsboot.mbn, 7) -REFLASH(dragonboard/u-boot.img, 8) -usb stop && -echo Reflash completed - loadaddr=0x81000000 initrd_high=0xffffffffffffffff linux_image=Image -- 2.47.2
