mirror of
https://github.com/linux-msm/cdba.git
synced 2026-02-25 13:11:56 -08:00
dcccae8226
If conmux goes away, e.g. by someone invoking ~$quit, the read() from the conmux fd will continously return 0, which is not discarded as an error, but sent as a console output message to the client, continuously. Quit bad when this happens, instead. Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
= CDBA control tool
The CDBA control tool is used for remotely booting images on development boards
attached using a CDB Assist or Conmux.
= Device side
On the host with the CDB Assist or Conmux attached the "bad" executable is run
from sandbox/cdba/bad. Available devices are read from $HOME/.cdba
= Client side
The client is invoked as:
cdba -b <board> -h <host> [-c <power-cylce-count>] boot.img
<host> will be connected to using ssh and <board> will be selected for
operation. As the board's fastboot interface shows up the given boot.img will
be transfered and booted on the device.
The board will execute until the key sequence ^A q is invoked or the board
outputs a sequence of 20 ~ (tilde) chards in a row.
If the optional -c is given, the board will upon receiving the tilde sequence
restart the board the given number of times. Each time booting the given
boot.img.
== Device configuration
The list of attached devices is read from $HOME/.cdba and is YAML formatted.
=== Example
devices:
- board: db2k
cdba: 00000001
name: "DragonBoard2k"
fastboot: abcdef1
voltage: 8000
- board: mtp2k
conmux: mtp2k
fastboot: abcdef2
fastboot_set_active: true