Board Management Layer Notes

Here are notes about the different ways that system do board managemnent:

different systems

SLAV

Uses the following verbs or functions:

• dut_boot
• dut_login
• dut_exec
• dut_copyfrom
• dut_copyto
• fota = "flash-over-the-air" for flashing a board

Questions:

• what layer provides these?
• what layer calls these?

ttc (Tiny Target Control)

Uses the following verbse or functions:

• ttc kinstall - install kernel (either to target or tftp area on server)
• ttc fsinstall - install root filesystem (either to target or nfs area on server)
• ttc reboot - reboot the target
• ttc console - get access to console on the target
• ttc login - get to login shell on the target
• ttc run - execute a command on the target
• ttc cp - copy files to or from the target
  • example: ttc [<board>] cp file target:/tmp
  • example: ttc [<board>] cp target:/some/dir/file hostfile
• ttc rm - remove files from target
• ttc waitfor - wait for a command to complete successfully

reservations

• ttc status - show status of a board (including reservation)
• ttc reserve - reserve a target
• ttc release - release a target

Fuego

These are considered "transport" APIs:

• setup - can be used for provisioning or instantiation (for vms)
• teardown - used for instance destruction (for vms)
• connect - set up communication channel with board
• disconnect - disconnect communication channel with board
• cmd - execute a command on the device under test
• put - copy files and/or directories to the device under test
• get - copy files and/or directories from the device under test

The first 4 (setup, teardown, connect and disconnect) are often empty for a board, and provisioning is left as an exercise for a different layer.

And a board management API:

• reboot - reboot the device under test

syzbot

Uses 4 verbs: