view target-utils/calversion/main.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 1dcc9e4b71fd
children
line wrap: on
line source

#include "types.h"

main()
{
	uart_select_init();
	printf("Calypso version ID program running\n");
	print_boot_rom_info();
	printf("Device ID code: 0x%04X\n", *(volatile u16 *)0xFFFEF000);
	printf("Device version code: 0x%04X\n", *(volatile u16 *)0xFFFEF002);
	printf("ARM ID code: 0x%04X\n", *(volatile u16 *)0xFFFFFE00);
	printf("cDSP ID code: 0x%04X\n", *(volatile u16 *)0xFFFFFE02);
	dsp_power_on();
	for (;;) {
		putchar('=');
		if (command_entry())
			command_dispatch();
	}
}