To use SystemTap, we need to add it to our target image by adding it specifically, as follows:

IMAGE_INSTALL_append = " systemtap" 

Or we can also add it by using the tools-profile image feature, or an -sdk image.

We will also need an SSH server running on the target. This is already available on the -sdk image; otherwise we can add one to our image with the following:

EXTRA_IMAGE_FEATURES += "ssh-server-openssh" 

We will also need to compile the kernel with the CONFIG_DEBUG_INFO configuration variable to include debug information, but not the CONFIG_DEBUG_INFO_SPLIT as this is not handled well by SystemTap, as well as performance events counters and kprobes (CONFIG_KPROBES, CONFIG_UPROBES) as explained in previous recipes.

Other kernel configuration parameters needed are CONFIG_RELAY, CONFIG_ARM_UNWIND, CONFIG_DEBUG_FS, CONFIG_MODULES, and CONFIG_MODULE_UNLOAD, but these are usually part of the default kernel configurations and they are already defined on the default Wandboard's defconfig.