Searched refs:commands (Results 1 – 23 of 23) sorted by relevance
20 To build S and NS application image without a BL2, run the following commands:33 To build S and NS application along with a BL2, run the following commands:46 To buld the S and NS regression tests without BL2, run the following commands:63 If you built TF-M with the BL2 secondary bootloader, use the following commands:
148 commands = program['commands'] variable150 for command in commands:176 commands = program['commands'] variable177 for command in commands:
7 Build TF-M regression test with M2351 by following commands:38 The commands are as follows:
7 Build TF-M regression test with M2354 by following commands:38 The commands are as follows:
10 for additional information ( contents, build commands and more ).
19 You need to download it manually before building any tests with the following commands:33 The basic commands for building the regression tests will be:
69 - Please use "/" instead of "\\" for paths when running CMAKE commands under
89 - Use the BL1 generated from the below commands to place it inside FPGA board SD Card.90 - Use the cs1000.bin created from the below commands to place it inside FPGA board SD Card.
108 The RSE ROM image should be generated with the following build commands:
182 The following commands build Profile Medium-ARoT-less without test cases on **Musca-B1** with196 The following commands build Profile Medium-ARoT-less with regression test cases on
387 The following commands build Profile Large without test cases on **AN521** with401 The following commands build Profile Large with regression test cases on
415 The following commands build Profile Medium without test cases on **AN521** with429 The following commands build Profile Medium with regression test cases on
541 The following commands build Profile Small without test cases on **AN521** with556 The following commands build Profile Small with regression test cases on
149 extracted from the GPT image using the following commands (and can then be150 patched and reinserted using the above commands)::
25 following commands:
32 following commands:
149 The output reveales wich commands are chained and their error output if any.
33 following commands:
333 run the following commands:372 run the following commands:
238 # This tag can be used to specify a number of aliases that act as commands in307 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in630 # list. This list is created by putting \todo commands in the documentation.636 # list. This list is created by putting \test commands in the documentation.642 # list. This list is created by putting \bug commands in the documentation.648 # the deprecated list. This list is created by putting \deprecated commands in755 # markup commands wrongly.892 # searched for input files to be used with the \include or \dontinclude commands1138 # footer and what special commands can be used inside the footer. See also1175 # files will be copied as-is; there are no commands or markers available.[all …]
300 the root by changing the ``-B`` option of the commands, for example,
632 - Apply commands below in the ``Commands`` debug window to dump the token in640 - Execute commands below on the host computer to verify the token:
