mirror of
https://github.com/linux-msm/cdba.git
synced 2026-02-25 13:11:56 -08:00
2205666349877bb3ea7a1e34b597ea6767fadf24
For some devices it's not possible to use fastboot boot and as such they will not enter fastboot unless the fastboot key is held. Expose this functionality in the device api. 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
Description
Languages
C
93.3%
Shell
3.8%
Meson
2.4%
Python
0.5%