Yocto Linux meta recipe for wolfTPM examples

[aidangarske]

Description

Added recipes-examples/wolftpm/wolftpm-wrap-test.bb and recipes-examples/wolftpm/wolftpm_%.bbappend to add support for wolfTPM wrap_test example.
IMAGE_INSTALL argument for wolftpm examples -> wolftpm-wrap-test
Tested on Scarthgap and Kirkstone works on both now.
Runs in runqemu qemux86-64 in usr/bin examplescan be ran like this:

./wolftpm-wrap-test

[night1rider]

Few things that need to happen before we can merge this.

[night1rider]

Seems to be a path issue, it is use the original host system's path and not the target systems.

[night1rider]

Reviewed again and it seems that resulting script that gets created by libtool uses the host system's paths and not the target systems paths.

Examples: relink_command="(cd /home/msi-debian/WolfWork/yocto/kirkstone/build/tmp/work/core2-64-poky-linux/wolftpm/3.2.0-r0/build; { test -z \" when /home/msi-debian/WolfWork/yocto/kirkstone/build/tmp/work/core2-64-poky-linux/wolftpm/3.2.0-r0/build should be set to /usr/bin as the instructions allude to.

This goes the same for all the tool paths as well so gcc and other tools the script needs don't point to the target's path but the host builder's paths.

Is there a way to override these and provide a path so the libtool script gets generated correctly or is this a change needed in the tooling of wolfTPM?

[night1rider]

I tested this and now it does seem to execute however the output is lacking?
Is this the expect output of the wrap-test?

root@qemux86-64:~# wolftpm-wrap-test 
TPM2 Demo for Wrapper API's
root@qemux86-64:~# 

Am I missing some setup, instructions, or packages?

[aidangarske]

@night1rider @dgarske This is the expected output for the wrap test without a tpm simulator. If you wanted to run the full test you need to have a tpm simulator loaded onto your image as well and start the simulator before you run the test. Just like if you were running it locally.
I have not tested with the simulator. If you think it would be a good idea to test this fully I can. But this is the same output we get running locally without the simulator. I'll update the readme with this information. So users know to start their tpm/sim before executing the test.

[dgarske]

@night1rider @dgarske This is the expected output for the wrap test without a tpm simulator. If you wanted to run the full test you need to have a tpm simulator loaded onto your image as well and start the simulator before you run the test. Just like if you were running it locally. I have not tested with the simulator. If you think it would be a good idea to test this fully I can. But this is the same output we get running locally without the simulator. I'll update the readme with this information. So users know to start their tpm/sim before executing the test.

@aidangarske please add instructions to the README.md for how to setup the TPM simulator with Yocto and QEMU.

[night1rider]

Seems that there are some missing instructions or dependencies not indicated in the README.

[night1rider]

Needs to be bitbake wolftpm-wrap-test not bitbake wolftpm-examples

[night1rider]

Please specify this configuration variable needs to be in a wolftpm_%.bbappened to avoid confusion

[night1rider]

I am getting a ERROR: Nothing RPROVIDES for all these packages other than the wolfssl/tpm ones, this means that yocto cannot find a package/recipe with the names of all these libraries/tools. Do you have some external meta library plugged in that is not specified here in the README? This would be in your build/conf/bblayers.conf file.

I am using kirkstone, is it possible these tools are included by default with a newer release of yocto?

[night1rider]

Missing step to enter qemu for the created target image. I use runqemu nographic is this appropriate?

[night1rider]

swtpm is not found. I assume this has to do with the missing packages as described earlier.