Home
last modified time | relevance | path

Searched refs:number (Results 1 – 25 of 81) sorted by relevance

1234

/trusted-firmware-m-3.7.0/secure_fw/partitions/lib/runtime/
Dtfm_sp_log_raw.c56 uint32_t number = (uint32_t)num; in _tfm_dec_num_output() local
62 number = -num; in _tfm_dec_num_output()
66 num_buff[k++] = '0' + number % 10; in _tfm_dec_num_output()
67 number /= 10; in _tfm_dec_num_output()
68 } while (number); in _tfm_dec_num_output()
/trusted-firmware-m-3.7.0/interface/include/multi_core/
Dtfm_mailbox_config.h.in15 /* Get number of mailbox queue slots from build configuration */
27 * The number of slots should be no more than the number of bits in
/trusted-firmware-m-3.7.0/secure_fw/partitions/firmware_update/bootloader/
Dtfm_bootloader_fwu_abstraction.h109 uint8_t number);
128 uint8_t number);
/trusted-firmware-m-3.7.0/platform/ext/common/
Dtfm_s_linker_alignments.h18 #define ROUND_UP_TO_MULTIPLE(number, multiple) \ argument
19 ((((number) + (multiple) - 1) / (multiple)) * (multiple))
/trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CA5/
Dmodel_config.txt9 …x123456 # (int , init-time) default = '0x123456' : ARM SVC number for semihosting : …
10 …=0xAB # (int , init-time) default = '0xAB' : Thumb SVC number for semihosting : …
11 …=0xF000 # (int , init-time) default = '0xF000' : ARM HLT number for semihosting : …
12 …=0x3C # (int , init-time) default = '0x3C' : Thumb HLT number for semihosting : …
/trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CA9/
Dmodel_config.txt9 …x123456 # (int , init-time) default = '0x123456' : ARM SVC number for semihosting : …
10 …=0xAB # (int , init-time) default = '0xAB' : Thumb SVC number for semihosting : …
11 …=0xF000 # (int , init-time) default = '0xF000' : ARM HLT number for semihosting : …
12 …=0x3C # (int , init-time) default = '0x3C' : Thumb HLT number for semihosting : …
/trusted-firmware-m-3.7.0/secure_fw/partitions/firmware_update/bootloader/mcuboot/
Dtfm_mcuboot_fwu.c198 psa_status_t fwu_bootloader_install_image(const psa_fwu_component_t *candidates, uint8_t number) in fwu_bootloader_install_image() argument
221 for (cand_index = 0; cand_index < number; cand_index++) { in fwu_bootloader_install_image()
286 for (index_i = 0; index_i < number; index_i++) { in fwu_bootloader_install_image()
290 if ((index_i < number) && (mcuboot_ctx[dep.image_id].fap != NULL)) { in fwu_bootloader_install_image()
327 for (cand_index = 0; cand_index < number; cand_index++) { in fwu_bootloader_install_image()
382 uint8_t number) in fwu_bootloader_mark_image_accepted() argument
402 for (trial_index = 0; trial_index < number; trial_index++) { in fwu_bootloader_mark_image_accepted()
416 for (trial_index = 0; trial_index < number; trial_index++) { in fwu_bootloader_mark_image_accepted()
429 (void)number; in fwu_bootloader_mark_image_accepted()
/trusted-firmware-m-3.7.0/docs/security/security_advisories/
Dsvc_caller_sp_fetching_vulnerability.rst68 handler gets the SVC number by referencing the memory at the 2 bytes subtracted
71 functions indicated by the SVC number. The PSP_S may point to the bottom
80 Even if a valid SVC number is returned, the stack seal values are part of the
90 As a summary, the impacts of the vulnerability depend on whether an SVC number
92 number corresponds to:
94 - A memory access fault when fetching the SVC number from memory. This fault
96 - The SVC number corresponds to the initialization process in TF-M. SPM
100 - The SVC number corresponds to the boot data fetching function. If the
105 - The SVC number corresponds to the log output function. If the unpredictable
108 - The SVC number corresponds to other valid numbers other than above. The
/trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CA7/
Dmodel_config.txt9 …x123456 # (int , init-time) default = '0x123456' : ARM SVC number for semihosting : …
10 …=0xAB # (int , init-time) default = '0xAB' : Thumb SVC number for semihosting : …
11 …=0xF000 # (int , init-time) default = '0xF000' : ARM HLT number for semihosting : …
12 …=0x3C # (int , init-time) default = '0x3C' : Thumb HLT number for semihosting : …
/trusted-firmware-m-3.7.0/lib/ext/cryptocell-312-runtime/codesafe/src/secure_boot_debug/util/
Dutil.h47 #define COUNT_ONE_BITS(number, BitCount) \ argument
50 uint32_t tmp_num = number; \
/trusted-firmware-m-3.7.0/secure_fw/spm/
DKconfig.comp13 int "Maximal number of handling secure services"
16 The maximal number of secure services that are connected or requested at
/trusted-firmware-m-3.7.0/secure_fw/partitions/crypto/
DKconfig.comp32 int "Max number of concurrent operations"
35 The max number of concurrent operations that can be active (allocated) at
39 bool "PSA Crypto random number generator module"
/trusted-firmware-m-3.7.0/lib/ext/cryptocell-312-runtime/host/src/cc_mng/
Dmbedtls_cc_mng_int.h122 #define CC_MNG_COUNT_ONE_BITS(number, BitCount) \ argument
125 uint32_t tmp_num = number; \
/trusted-firmware-m-3.7.0/platform/ext/target/arm/corstone1000/bl1/
DCMakeLists.txt13 # BL1 only loads the BL2 image, image number always equals 1
35 # configuration, where image number is 3. (Coming from BL2 build). To not to collide with BL1's
36 # build where image number is 1 mbedcrypto library is separated from the build of other source
47 # be built with wrong image number macro (value coming from BL2 config), so the start-up files
48 # added here, as those not use this image number macro.
62 # to bl1, again pulling the image number property matching with BL2 build, so scatter setup done
/trusted-firmware-m-3.7.0/lib/ext/tf-m-tests/
Dread_version.cmake13 # Parse the version number after "version="
/trusted-firmware-m-3.7.0/docs/design_docs/services/
Dtfm_uniform_secure_service_signature.rst86 * in_len: the number of input parameters, i.e. psa_invecs
87 * out_len: the number of output parameters, i.e. psa_outvecs
90 The number of vectors that can be passed to a secure service is constrained:
/trusted-firmware-m-3.7.0/secure_fw/partitions/protected_storage/
DKconfig.comp72 int "Maximum stored assets number"
75 Defines the maximum number of assets to be stored in the PS area. This
76 number is used to dimension statically the object table size in
/trusted-firmware-m-3.7.0/lib/ext/cryptocell-312-runtime/host/src/tests/TestAL/
DReadMe.txt7 2. Run the build_config.sh script, with or without a configuration number.
/trusted-firmware-m-3.7.0/docs/integration_guide/
Dnon-secure_client_extension_integration_guide.rst85 number of the contexts requested by the NS entity. The number of assigned
87 context number based on the current available resource in TF-M. If
88 `ctx_requested` is `0`, then the maximum available context number will be
164 the NS tasks that need to call secure services. If the number of tasks is less
171 requested context number to initialize the non-secure context in TF-M. The
172 actual allocated context number will be returned. `0` means initialization
174 context number allocated to it. TF-M only supports one context for now.
/trusted-firmware-m-3.7.0/cmake/
Dversion.cmake25 # remove a commit number
/trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CM55S/
Dmodel_config.txt9 … # (int , init-time) default = '0xAB' : T32 SVC number for semihosting : …
17 …the Non-Secure MPU. If Security Extentions are absent, this is the total number of MPU regions : […
/trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CM55/
Dmodel_config.txt9 … # (int , init-time) default = '0xAB' : T32 SVC number for semihosting : …
17 …the Non-Secure MPU. If Security Extentions are absent, this is the total number of MPU regions : […
/trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CM55NS/
Dmodel_config.txt9 … # (int , init-time) default = '0xAB' : T32 SVC number for semihosting : …
17 …the Non-Secure MPU. If Security Extentions are absent, this is the total number of MPU regions : […
/trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CM3/
Dmodel_config.txt6 …SVC=0xAB # (int , init-time) default = '0xAB' : T32 SVC number for semihosting : …
/trusted-firmware-m-3.7.0/docs/design_docs/booting/
Dtfm_secure_boot.rst198 At boot time MCUBoot inspects the version number in the image header and passes
306 - **Image identifier:** The number of the image which the current image (whose
444 An image version number is written to its header by one of the Python scripts,
445 and this number is used by the bootloader when the direct execute-in-place or
450 The version number of the image (single image boot) can manually be passed in
455 Alternatively, the version number can be less specific (e.g 1, 1.2, or 1.2.3),
457 number argument is optional, and if it is left out, then the version numbers of
459 this case, the last component (the build number) automatically increments from
461 **until a number is explicitly provided**. If automatic versioning is in place
462 and then an image version number is provided for the first time, the new number
[all …]

1234