Boards with an SSH server (Wind River Linux, vendor BSP and Yocto images) are declared per workspace and reached through the same OpenSSH client and SSH configuration as the build host, including ProxyJump through the lab's jump host. The scripts run on a board use only a POSIX shell and the BusyBox applets of the Yocto Project's default configuration, so production images work.
State: modelled with OpenSSH 9.6p1 as client and server on one Linux machine against stand-in boards (BusyBox 1.36.1 built with poky scarthgap's configuration in a chroot, and GNU coreutils): host-key trust, identity, the build match over Git, byte-exact files, copy modes, command cancel, reboot and power-off requests, and the running app (view, Explorer folder, confirmed save, copy, reboot). Not run on a real board (such as the i.MX 8M Plus) or a real reboot, on Windows, with Dropbear for copies (a 2.4 MB copy to a Dropbear board ended with EPIPE, a known issue), on Wind River Linux images or through a jump host. The terminal was not shown in the app in the lab.
Add a board
Run Add Target... (or + in the Targets view) and give a name, the host or SSH alias, the user, the MACHINE and notes. It is stored in neuralInverse.embeddedLinux.targets:
{
"neuralInverse.embeddedLinux.targets": [
{ "name": "gateway-bench3", "host": "<host or ssh alias>", "user": "root", "machine": "imx8mp-lpddr4-evk", "notes": "Bench 3, CAN harness B" }
]
}Each target takes name, host (a link-local IPv6 address with its interface works for a direct link), user, port, identityFile, machine and notes. Edit Targets in Settings opens the setting; Remove Target from Workspace... removes one.
On a first connection the board says its host key is not trusted. Trust Target Host Key... shows the fingerprint to compare with ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub on the board's console. Set Target Key Passphrase... and Remove Target Key Passphrase work as for the build host.
What the view shows
For each board: the connection; the running image (from os-release, /etc/buildinfo and /etc/version) matched to its build in the build history by layer revisions; the kernel, uptime, memory and storage; the account; the declared MACHINE and the notes. Refresh Targets reads them again. The board's running system has its own groups (see The board's system and boot time).
Files on the board
- Add Target Folder to Workspace... adds a board folder (for example
/etc) to the Explorer; Open File on Target... opens one file in an editor. - Every save, new file or folder, delete, rename and paste in a board's folder asks first, naming the board and every path.
- Download from Target... copies a file or folder to this computer; Change Permissions on Target... sets an octal mode.
Adding a board folder makes the workspace multi-root, where only window-scoped settings carry over; the build hosts setting does not, which is a known limitation.
Copy, terminal, reboot
- Copy to Target... copies files and folders to a folder on the board after a confirmation. Replaced files keep their mode and owner; new programs (recognised from their ELF header) are made executable.
- Open Terminal on Target opens a shell on the board.
- Reboot Target... and Power Off Target... ask first, then wait for the board to answer again after a reboot.
The serial console
U-Boot and kernel consoles use the Embedded module's Open Serial Monitor (for example at 115200 baud on the board's debug UART): stopping autoboot and typing at the U-Boot prompt, the kernel log and the login prompt. It has run only between two virtual serial ports on Linux, never on a real board's console.
Agent tools
Targets, a board's state, folders and files are read-only tools. Copying to a board, running a command, reboot and power-off always ask first, naming the board and every path.