view rvinterf/etmsync/tmscmdtab.c @ 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 886f65760d09
children 379574e5cf5e
line wrap: on
line source

/*
 * fc-tmsync command dispatch table
 */

#include "cmdtab.h"

extern int cmd_dieid();
extern int cmd_exec();
extern int cmd_exit();
extern int cmd_memdump();
extern int cmd_omemdump();
extern int cmd_rfpr();
extern int cmd_rfpw();
extern int cmd_rftr();
extern int cmd_tms();
extern int cmd_ttr();
extern int cmd_ttr_all();

extern int get_pirelli_vbat_cal();
extern int get_pirelli_imei();

struct cmdtab cmdtab[] = {
	{"dieid", 0, 0, cmd_dieid},
	{"exec", 1, 1, cmd_exec},
	{"exit", 0, 0, cmd_exit},
	{"memdump", 2, 2, cmd_memdump},
	{"omemdump", 2, 2, cmd_omemdump},
	{"pirelli-get-imei", 0, 0, get_pirelli_imei},
	{"pirelli-vbat-cal", 0, 0, get_pirelli_vbat_cal},
	{"rfpr", 1, 1, cmd_rfpr},
	{"rfpw", 2, 3, cmd_rfpw},
	{"rftr", 1, 2, cmd_rftr},
	{"tms", 1, 1, cmd_tms},
	{"ttr", 1, 1, cmd_ttr},
	{"ttr-all", 1, 1, cmd_ttr_all},
	{0, 0, 0, 0}
};