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.

/*
 * FreeCalypso buzzer "melodies" have times measured in TDMA frames,
 * as that is the time unit in the main firmware which will ultimately
 * play them.  In this standalone buzzer player we simulate TDMA frame
 * timing by programming Calypso TIMER1 with the period of 1875, and
 * we detect timer overflow (one virtual TDMA frame time having passed)
 * by polling the read register to avoid the need for interrupt handling
 * infrastructure.
 */

#include "types.h"
#include "timer.h"

void
timer_init()
{
	TIMER1_REGS.cntl = CNTL_CLOCK_ENABLE;
	TIMER1_REGS.load = 1875;
	TIMER1_REGS.cntl = CNTL_CLOCK_ENABLE | CNTL_AUTO_RELOAD | CNTL_START;
}

void
wait_for_tdma_frame()
{
	u16 read1, read2;

	read1 = TIMER1_REGS.read;
	for (;;) {
		read2 = TIMER1_REGS.read;
		if (read2 > read1)
			return;
		read1 = read2;
	}
}