In a standard Greentea test setup, the host sends a sync signal to the target to start the test. This helps to avoid synchronisation issues, e.g. test already running before the host is ready.
To enable this, set "wait-for-sync" to 1 in mbed_app.json, or pass --sync to test_psa_target.py.
Note: Images built this way will NOT start tests on its own - they need to be driven by the Greentea host tools.
Log:
[1612528946.71][CONN][RXD] Booting TFM v1.1
[1612528946.71][CONN][RXD] Waiting for Greentea host
[1612528946.71][CONN][RXD] mbedmbedmbedmbedmbedmbedmbedmbed
[1612528946.72][CONN][RXD] Starting TF-M regression tests
[1612528946.72][CONN][INF] found SYNC in stream: {{__sync;4c998dcc-79ef-4f03-a9ae-450f65db60da}} it is #0 sent, queued...
In a standard Greentea test setup, the host sends a sync signal to the target to start the test. This helps to avoid synchronisation issues, e.g. test already running before the host is ready.
To enable this, set "wait-for-sync" to 1 in
mbed_app.json
, or pass--sync
totest_psa_target.py
.Note: Images built this way will NOT start tests on its own - they need to be driven by the Greentea host tools.
Log: