FreeCalypso > hg > freecalypso-tools
view rvinterf/asyncshell/poweroff.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 | e7502631a0f9 |
children |
line wrap: on
line source
/* * fc-shell poweroff and tgtreset commands */ #include <sys/types.h> #include <stdio.h> #include <stdlib.h> #include "pktmux.h" #include "etm.h" send_etm_cmd(buf, len) u_char *buf; { int i, c; buf[0] = RVT_TM_HEADER; c = 0; for (i = 1; i <= len; i++) c ^= buf[i]; buf[i] = c; send_pkt_to_target(buf, len + 2); return 0; } cmd_poweroff() { u_char cmdpkt[7]; cmdpkt[1] = ETM_CORE; cmdpkt[2] = TMCORE_OPC_CODEC_WR; cmdpkt[3] = 30; /* VRPCDEV */ cmdpkt[4] = 0x01; /* low 8 bits */ cmdpkt[5] = 0; /* high 2 bits */ return send_etm_cmd(cmdpkt, 5); } cmd_tgtreset() { u_char cmdpkt[4]; cmdpkt[1] = ETM_CORE; cmdpkt[2] = TMCORE_OPC_RESET; return send_etm_cmd(cmdpkt, 2); }