view target-utils/buzplayer/melentry.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 eb5960dc258c
children 9092ff68e37d
line wrap: on
line source

#include <sys/types.h>
#include <ctype.h>
#include <stdlib.h>
#include "types.h"
#include "melody.h"

extern struct melentry *melody_buf_start, *melody_buf_tailptr;

void
melody_init()
{
	melody_buf_tailptr = melody_buf_start;
}

void
melody_entry(argbulk)
	char *argbulk;
{
	char *argv[3];
	u32 tone, dur;

	if (parse_args(argbulk, 2, 2, argv, 0) < 0)
		return;
	tone = strtoul(argv[0], 0, 0);
	dur = strtoul(argv[1], 0, 0);
	if (tone > 255 || dur < 1 || dur > 0xFFFF) {
		printf("ERROR: argument(s) out of range\n");
		return;
	}
	melody_buf_tailptr->tone = tone;
	melody_buf_tailptr->dur = dur;
	melody_buf_tailptr++;
}