FreeCalypso > hg > freecalypso-tools
view target-utils/README @ 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
The following target utilities or code components are currently buildable in this target-utils tree: compalstage For Compal phones only: a little piece of code that is fed to the original fw's bootloader via the serial download protocol provided by the latter; it re-enables the Calypso chip boot ROM and jumps to it, allowing our loadagent to be loaded in the same way as on freedom-enabled devices. helloapp Template/skeleton for building programs like loadagent and pirexplore. loadagent Loadagent is built to be loaded and run out of the Calypso internal (on-chip) RAM, and does not depend on any hardware outside of the Calypso chip itself - thus it should run unchanged on all Calypso targets. It expects to be loaded by the Calypso ROM bootloader in the UART download mode, and it reads a RAM variable left behind by the ROM code that indicates which UART has been used to perform that download - it then uses that same UART to communicate with the host, presenting an interactive command prompt. You can run loadagent "raw" by loading loadagent.srec with fc-iram, but normally it is used "behind the scenes" by fc-loadtool and fc-xram. pirexplore For Pirelli DP-L10 target only: this program is built in the same manner as loadagent (also runs out of IRAM, expects to be loaded with fc-iram, and presents an interactive command prompt on the autodetected UART), but it automatically performs some hardware (board level) initialization specific to the Pirelli, and offers additional commands for exploring the hardware features of this device. tf-breakin Here we build the payload for the tfc139 hack-utility; see ../rvinterf/lowlevel/tfc139.c for the ugly details.