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.

/*
 * For sizing our buffers etc in rvinterf, we need a limit on the size of
 * message packets we can send to the target.  As it happens, the packet
 * Rx code in RVT on the target side also has a limit (quite naturally,
 * as it needs to use a static buffer to reassemble incoming packets as
 * they arrive at the UART in unpredictable interrupt-sized chunks), so
 * we set our limit to match that in RVT.
 */

#define	MAX_PKT_TO_TARGET	255

/*
 * The above limit definition counts all bytes between the opening and
 * closing STX flags, but not DLEs inserted for binary transparency.
 */