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.

/*
 * This utility allows a single AT command to be issued
 * through the atinterf framework.
 */

#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include "../../rvinterf/include/exitcodes.h"

extern char at_response[];

int_callback()
{
	puts(at_response+1);
}

main(argc, argv)
	char **argv;
{
	int c;
	extern int optind;

	while ((c = getopt(argc, argv, "B:np:RX:")) != EOF)
		if (!atinterf_cmdline_opt(c)) {
			/* error msg already printed */
			exit(ERROR_USAGE);
		}
	if (argc != optind + 1 || strncasecmp(argv[optind], "AT", 2)) {
		fprintf(stderr, "usage: %s [options] at-cmd\n", argv[0]);
		exit(ERROR_USAGE);
	}
	atinterf_init();
	atinterf_exec_cmd(argv[optind], (char *) 0, int_callback);
	puts(at_response+1);
	exit(0);
}