Author : Jiri Andrys
Maintainer : Jiri Andrys
Contributors : Jiri Andrys
The bsp-probe is collecting information from BSP and storing to bsp-probe.log.
Till now only NXP based BSPs are supported.
The bsp-probe.log includes:
- repo url, hash, tag, name of manifest.xml + hash
- list of yocto layers
- yocto layers revisions
- git hashes(sha1) of all source files
- local.conf
- kernel configuration
Sometimes publicly accessible BSP is used by others to develop software and assembly of BSP(manifest.xml) can not include related software.
Usually people and teams whose developing applications software differs from teams which are responsible for platform development. In case that there is light bond in release chain, separation can speed up development process. Once application team stabilize release, then it can be added to BSP. Middle stages could be tightened by this tool as assembly information stored by this tool. Other case is when teams accross countries need to test different parts of product on base of same environment, again this tool can collect information about assembly and bsp-probe.log can be shared easilly.
The repo info command prints basic information about layers provided by manifest.xml. Once we have at least one layer out of manifest.xml we can not use repo info command.
We can use bitbake-layers show-layers or just parse local.conf in order to get current active layers, unfortunatelly this command can not give us versions.
Bsp-probe has been tested on following systems:
- Ubuntu 14.04(64bit, docker)
- Ubuntu 16.04(64bit, docker)
- Fedora 24(64bit, docker)
Together with git-stripper is bsp-probe used for releasing requests.
The best way is to store bsp-probe to base BSP assembly.
- No installation is necessary.
- The bsp-probe is added to BSP by maintainer and is located in bsp-release layer :
sources/meta-*-bsp-release/tools/bsp-probe ** - In order to ease of using bsp-probe link to tool is added to sources/poky/scripts directory which is included in PATH.
- Link in sources/poky/scripts is added by manifest.xml during repo sync phase.
The tool have to be executed in environment where
bitbake command is available
and
after all layers have been added to bblayers.conf
and
configuration in local.conf for build is in final state
and
build of image file have finished.
After we have finished configuration and build final image we can run bsp-probe(step 5).
1. fslbsp$ repo init -u https://github.com/XXX.git -b XXX -m XXX.xml
2. fslbsp$ repo sync
3. fslbsp$ SDKMACHINE=$(uname -m) MACHINE=XXX source fsl-setup-release.sh -b build
4. fslbsp/build$ bitbake imageXXX
5. fslbsp/build$ bsp-probe
- Standard tools, included in almost all kind of distros and installed by default:
bash, grep, awk, mkdir, git, find, sort, pwd, printf, sed, mktemp, dirname, readlink, bitbake, bitbake-layers