tillitis-key/hw/application_fpga/apps
Michael Cardell Widerkrantz ba17a2b29e
build: Use only one Makefile for apps
- Use one common Makefile for all test device apps.
- Use a single copy of syscall.[Sh].
- Update docs for building.
2025-05-22 09:31:50 +02:00
..
defaultapp build: Use only one Makefile for apps 2025-05-22 09:31:50 +02:00
include build: Use only one Makefile for apps 2025-05-22 09:31:50 +02:00
reset_test build: Use only one Makefile for apps 2025-05-22 09:31:50 +02:00
testapp build: Use only one Makefile for apps 2025-05-22 09:31:50 +02:00
testloadapp build: Use only one Makefile for apps 2025-05-22 09:31:50 +02:00
Makefile build: Use only one Makefile for apps 2025-05-22 09:31:50 +02:00
README.md build: Use only one Makefile for apps 2025-05-22 09:31:50 +02:00
syscall.S build: Use only one Makefile for apps 2025-05-22 09:31:50 +02:00

Test applications

  • defaultapp: Immediately resets the TKey with the intention to start an app from the client, replicating the behaviour of earlier generations.
  • testapp: Runs through a couple of tests that are now impossible to do in the testfw.
  • reset_test: Interactively test different reset scenarios.
  • testloadapp: Interactively test management app things like installing an app (hardcoded for a small happy blinking app, see blink.h for the entire binary!) and to test verified boot.

Build

$ make

will build all the .elf and .bin files on the top level.

Use

Use tkey-runapp from tkey-devtools to load the apps:

$ tkey-runapp testapp.bin

All of these test apps are controlled through the USB CDC, typically by running picocom or similar terminal program, like:

$ picocom /dev/ttyACM1