view rvinterf/lowlevel/Makefile @ 497:74610c4f10f7

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.
author Mychaela Falconia <falcon@freecalypso.org>
date Sat, 25 May 2019 20:44:05 +0000
parents 90d7c360a614
children d43dc6dfb44c
line wrap: on
line source

CC=	gcc
CFLAGS=	-O2
PROGS=	rvtdump rvinterf tfc139
LIBS=	../../libserial/libserial.a ../libg23/libg23.a

INSTALL_PREFIX=	/opt/freecalypso

INSTBIN=${INSTALL_PREFIX}/bin

RVTDUMP_OBJS=	format.o format_fc.o output.o packetrx.o rvtdump.o

RVINTERF_OBJS=	clientcmd.o format.o format_fc.o localsock.o logsent.o \
		output.o packetrx.o packettx.o pktfwd.o rviflcd.o \
		rvifmain.o

TFC139_OBJS=	format.o output.o packetrx.o packettx.o tfc139.o

all:	${PROGS}

rvtdump:	${RVTDUMP_OBJS} ${LIBS}
	${CC} ${CFLAGS} -o $@ ${RVTDUMP_OBJS} ${LIBS}

rvinterf:	${RVINTERF_OBJS} ${LIBS}
	${CC} ${CFLAGS} -o $@ ${RVINTERF_OBJS} ${LIBS}

tfc139:		${TFC139_OBJS} ${LIBS}
	${CC} ${CFLAGS} -o $@ ${TFC139_OBJS} ${LIBS}

install:	${PROGS}
	mkdir -p ${INSTBIN}
	install -c ${PROGS} ${INSTBIN}

clean:
	rm -f *.o *.out *errs ${PROGS}