Compile trusted applications on Jetson TX2

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Hello,
I can run hwkey_app in CA_sample, but I can’t run hwkey_agent(TA) in hwkey-agent. There is no configure file related to hwkey_agent in this directory. How can I run this trusted application?
Note: I use Jetson TX2 for work, so I didn’t use any cross-compilation tools, and there is no similar information in the developer guide.
thanks

3

hello fanyangyf688,

please check developer guide, Trusted Application Development.
thanks

4

hello,
thank you for your reply.
The problem is that I ran skel_app directly on TX2, but the system reported an error because “trusty_std.h” was not found. I went to /usr/include but did not find the header file.

5

hello fanyangyf688,

please access L4T sources from download center, you may found the header file of trusty.
for example,
$L4T_Sources/r32.4.3/Linux_for_Tegra/source/public/trusty/lib/include/trusty_std.h

you should rebuilding Trusty also rebuilds all of the TAs on your host.
thanks

6

thank you for your reply.
I don’t understand the sentence ‘you should rebuilding Trusty also rebuilds all of the TAs on your host’.
I think that after flashing, TOS (trusty) will be installed in TX2 along with the normal operating system, but the three example applications in trusty are not started by default. So I only need to compile these three applications on the host, and then download them to TX2 to run. There is no need to rebuild trusty. If there is a problem with my above ideas, please point it out.

7

hello fanyangyf688,

you may cross compiling on the host machine, please export the cross compiler’s path-name and run make.
for example,

$ export CROSS_COMPILER=<Path to the cross compiler>
$ make

BTW,
you could also building on the native device, if the compiler has been installed on the target,
then you can move the code on the target and build it with make.
thanks

8

hello,
thank you for your reply!
In fact, my question is: Is it possible to compile TA and make it run like compiling CA? Finally, I found that my understanding was wrong.
In Trusty, all Trusty applications are packaged with Trusty kernel images. The entire image is signed and verified by the boot loader during the boot process, and all TAs are designed in server mode, which will provide for CA or other TAs service (see here).
That is to say, during the flashing process of TX2, both trusty and TA are loaded into the target board. Once TX2 is turned on, TA is already running, but the user cannot observe it.