target-utils: added 10 ms delay at the end of abb_power_off() The deosmification of the ABB access code (replacement of osmo_delay_ms() bogus delays with correctly-timed ones, which are significantly shorter) had one annoying side effect: when executing the poweroff command from any of the programs, one last '=' prompt character was being sent (and received by the x86 host) as the Calypso board powers off. With delays being shorter now, the abb_power_off() function was returning and the standalone program's main loop was printing its prompt before the Iota chip fully executed the switch-off sequence! I thought about inserting an endless tight loop at the end of the abb_power_off() function, but the implemented solution of a 10 ms delay is a little nicer IMO because if the DEVOFF operation doesn't happen for some reason in a manual hacking scenario, there won't be an artificial blocker in the form of a tight loop keeping us from further poking around.

CC=	arm-elf-gcc
CFLAGS=	-Os -fno-builtin
CPPFLAGS=-I../include
LD=	arm-elf-ld
OBJCOPY=arm-elf-objcopy

OBJS=	vectors.o crt0.o cmdtab.o main.o mygetchar.o uartbase.o uartinit.o \
	watchdog.o
LIBS=	../libcommon/libcommon.a ../libprintf/libprintf.a ../libbase/libbase.a \
	../libc/libc.a
LIBGCC=	`${CC} -print-file-name=libgcc.a`
LDS=	ld.script

all:	fbt-mode0.bin fbt-mode1.bin

crt0.S:
	ln -s ../env/crt0.S .

fbt-mode0.elf:	${OBJS} magic0.o ${LIBS} ${LDS}
	${LD} -N -T ${LDS} -o $@ ${OBJS} magic0.o ${LIBS} ${LIBGCC}

fbt-mode0.bin:	fbt-mode0.elf
	${OBJCOPY} -O binary $< $@

fbt-mode1.elf:	${OBJS} magic1.o ${LIBS} ${LDS}
	${LD} -N -T ${LDS} -o $@ ${OBJS} magic1.o ${LIBS} ${LIBGCC}

fbt-mode1.bin:	fbt-mode1.elf
	${OBJCOPY} -O binary $< $@

clean:
	rm -f *.o *errs *core *.elf *.bin *.srec crt0.S

FRC: