Home
last modified time | relevance | path

Searched refs:test (Results 1 – 25 of 99) sorted by relevance

1234

/trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Project/
Dvalidation.xsl5 <xsl:variable name="buildName" select="//report/test/title"/>
6 <xsl:variable name="numberOfTests" select="//report/test/summary/tcnt"/>
7 <xsl:variable name="numberOfExecutes" select="//report/test/summary/exec"/>
8 <xsl:variable name="numberOfPasses" select="//report/test/summary/pass"/>
9 <xsl:variable name="numberOfFailures" select="//report/test/summary/fail"/>
16 <xsl:for-each select="//report/test/test_cases/tc">
21 <xsl:when test="res='PASSED'"/>
22 <xsl:when test="res='NOT EXECUTED'">
/trusted-firmware-m-latest/docs/configuration/
Dtest_configuration.rst10 Regression test configuration is controlled entirely by ``TEST_NS`` or
11 ``TEST_S`` or single test suite configuration. The group test
12 configurations and single test suite configurations are listed below, all of
57 Individual test suites can be enabled when their dependencies like partitions or
58 other specific configurations are set. On the one hand, some test suites depend
59 on other test suites. On the other hand, some test suites conflict with
60 other test suites. Test configurations and dependencies will be
61 checked in ``${TFM_TEST_REPO_PATH}/test/config/check_config.cmake``.
64 test suites will be enabled or disabled as appropriate for the TF-M
105 variable should be set to the name of the test suite that is desired. It is
[all …]
Dbuild_configuration.rst16 3. If TEST_PSA_TEST is set, then PSA API test related config is applied from
27 9. If ``TEST_S`` or ``TEST_NS`` or other single test suite config like
29 config from ``${TFM_TEST_REPO_PATH}/test/config/set_config.cmake`` and
30 ``${TFM_TEST_REPO_PATH}/test/config/default_ns_test_config.cmake`` or
31 ``${TFM_TEST_REPO_PATH}/test/config/default_s_test_config.cmake`` or
32 ``${TFM_TEST_REPO_PATH}/test/config/default_test_config.cmake`` is
/trusted-firmware-m-latest/lib/ext/t_cose/test/
Dt_cose_test.c718 struct test_case *test; in bad_parameters_test() local
720 for(test = bad_parameters_tests_table; test->test_option; test++) { in bad_parameters_test()
721 if(run_test_sign_and_verify(test->test_option) != test->result) { in bad_parameters_test()
722 return (int_fast32_t)(test - bad_parameters_tests_table); in bad_parameters_test()
772 struct test_case *test; in crit_parameters_test() local
774 for(test = crit_tests_table; test->test_option; test++) { in crit_parameters_test()
775 if(run_test_sign_and_verify(test->test_option) != test->result) { in crit_parameters_test()
776 return (int_fast32_t)(test - crit_tests_table); in crit_parameters_test()
/trusted-firmware-m-latest/docs/building/
Dtests_build_instruction.rst6 Thus, tests require an extension of SPE side with test code and extra functionality
7 for some Non-Secure test cases. To inject that test code into SPE the
11 Also, test configurations should be passed to SPE build to include building Secure Tests.
30 The regression test application is located under **/tests_reg** folder.
48 enable individual test suites by using ``-DTEST_S_<SUITE>=ON`` or ``-DTEST_NS_<SUITE>=ON``.
49 For the available test suites, refer to the ``default_s_test_config.cmake`` and
53 All the test suite config options should be passed to the SPE build command, including NS ones.
55 All options passing to SPE build does not have to be duplicated in NSPE build, including NS test
67 The PSA API test codes are located under **/tests_psa_arch** folder.
70 Select one of the following test suites to be run.
Drun_tfm_examples_on_arm_platforms.rst59 To test TF-M with bootloader, one must apply the following changes:
72 BL2 bootloader is mandatory to test software update. Furthermore, two TF-M blobs
73 must be built. Outputs of example application and regression test can be used to
74 test it. Load output of example application to the primary slot (0x10080000) and
75 output of regression test to the secondary slot (0x10180000). Add the following
143 #### Execute test suites for the protected storage service ####
151 This test is DEPRECATED and the test execution was SKIPPED
155 This test is DEPRECATED and the test execution was SKIPPED
199 #### Execute test suites for the protected storage service ####
207 This test is DEPRECATED and the test execution was SKIPPED
[all …]
/trusted-firmware-m-latest/docs/releases/
D1.4.0.rst81 * - | PSA Arch Crypto test suite have several known failures.
85 * - | Protected Storage Regression test 4001 is stuck on SSE-300 in isolation
92 * - | Image size overflow on Musca-B1 PSA Arch test suite debug build.
111 * - | IPC Regression test fail when non-secure regression test is enabled and
112 | secure regression test is disabled.
115 * - | Panic test in PSA Arch IPC test suite generates inconsistent results
D1.5.0.rst23 - Support out-of-tree build of platform specific test suites.
26 - Support to select/deselect single or multiple TF-M regression test cases.
27 - Decouple regression test flag configuration from TF-M.
89 * - | PSA Arch Crypto test suite have several known failures.
112 * - | Protected Storage Regression test 4001 is stuck on SSE-300 in isolation
116 * - | Image size overflow on Musca-B1 PSA Arch test suite debug build.
D1.3.0.rst98 * - | PSA Arch Crypto test suite have several known failures.
102 * - | Protected Storage Regression test 4001 is stuck on SSE-300 in isolation
106 * - | IPC Regression test fail when non-secure regression test is enabled and
107 | secure regression test is disabled.
110 * - | Panic test in PSA Arch IPC test suite generates inconsistent results
D1.0.rst32 - Testcases running baremetal and with RTX to test the functionality.
55 - `Musca-A test chip board.
56 …oper.arm.com/products/system-design/development-boards/iot-test-chips-and-boards/musca-a-test-chip…
57 - `Musca-B1 test chip board.
58 …oper.arm.com/products/system-design/development-boards/iot-test-chips-and-boards/musca-b-test-chip…
59 - `Musca-S1 test chip board.`
113 * - PS test case 2002 and 1002 does not fail on Musca-B1 flash when
129 * - When SST/ITS are using Flash on Musca-B1, PSA Arch FF test fails due
/trusted-firmware-m-latest/platform/ext/target/nordic_nrf/common/nrf91/tests/
Dpsa_arch_tests_config.cmake9 # Use nrf9160 until test target name in PSA arch test repository has been updated to nrf91
/trusted-firmware-m-latest/platform/ext/target/arm/mps2/an519/tests/
Dtfm_tests_config.cmake8 # Make FLIH IRQ test as the default IRQ test
/trusted-firmware-m-latest/platform/ext/target/arm/mps3/corstone310/common/tests/
Dtfm_tests_config.cmake8 # Make FLIH IRQ test as the default IRQ test on Corstone-310
/trusted-firmware-m-latest/platform/ext/target/arm/mps4/corstone315/tests/
Dtfm_tests_config.cmake8 # Make FLIH IRQ test as the default IRQ test on Corstone-315
/trusted-firmware-m-latest/platform/ext/target/nordic_nrf/common/core/tests/
Dtfm_tests_config.cmake11 # Make FLIH IRQ test as the default IRQ test on nordic platforms
/trusted-firmware-m-latest/platform/ext/target/rpi/rp2350/tests/
Dtfm_tests_config.cmake6 # Make FLIH IRQ test as the default IRQ test on RP2350
/trusted-firmware-m-latest/platform/ext/target/arm/mps2/an521/tests/
Dtfm_tests_config.cmake8 # Make FLIH IRQ test as the default IRQ test on AN521
/trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/Core/Test/
DREADME.md3 This folder contains a unit test suite that validates CMSIS-Core implementation.
4 It uses test tools from LLVM, namely LIT and FileCheck, to validate consistency across compilers an…
15 ┣ �� lit.cfg.py LIT test suite configuration
127 The summary lists the amount of test cases executed and passed.
129 ## Analyse failing test cases
131 In case of failing test cases, one can run a single test case with verbose output like this:
151 Failing FileCheck requires in detail analysis of the `// CHECK` annotations in the test source file
152 against the `llvm-objdump` output of the test compilation.
171 This output is expected to match the test case
178 I.e., the test case expects the `mrs {{r[0-9]+}}, apsr` instruction, additional whitespace is ignor…
/trusted-firmware-m-latest/platform/ext/target/nuvoton/m2354/tests/
Dtfm_tests_config.cmake9 # Make FLIH IRQ test as the default IRQ test on M2354
/trusted-firmware-m-latest/platform/ext/target/nuvoton/m2351/tests/
Dtfm_tests_config.cmake9 # Make FLIH IRQ test as the default IRQ test on M2354
/trusted-firmware-m-latest/docs/platform/nuvoton/m2351/
DREADME.rst7 Build TF-M regression test with M2351 by following commands:
11 $ cd tf-m-test/tests_reg
26 Define TEST_NS=ON or TEST_S=ON for non-secure or secure regression test.
/trusted-firmware-m-latest/docs/platform/nuvoton/m2354/
DREADME.rst7 Build TF-M regression test with M2354 by following commands:
11 $ cd tf-m-test/tests_reg
26 Define TEST_NS=ON or TEST_S=ON for non-secure or secure regression test.
/trusted-firmware-m-latest/platform/
DKconfig.platform25 bool "Use the PS test NV counters"
29 test/secure_fw/suites/ps/secure/nv_counters of the tf-m-tests repo,
32 enabled by default, but has no effect when the secure regression test is
34 tests. In this case, the PS rollback protection test suite will not be
38 The remainder of the PS test suites will run using the hardware NV
56 ######################### TFM psa api test target ##############################
/trusted-firmware-m-latest/secure_fw/partitions/initial_attestation/
DKconfig22 bool "Include test code"
27 test suite
/trusted-firmware-m-latest/lib/ext/cryptocell-312-runtime/host/src/tests/integration_cc3x/runtime_integration_test/
DREADME.txt1 The purpose of the integration tests is to test and verify the user's system integration,
10 - Chapter "Appendix C - Integration test" in the Software Integrators Manual
12 abstraction layer between the integration test and the operating system of the user's choice.

1234