Searched full:rom (Results 1 – 25 of 135) sorted by relevance
123456
| /trusted-firmware-m-latest/docs/platform/arm/rse/rom_releases/2024-04/ |
| D | readme.rst | 2 RSE ROM Release 2024-04-08
12 - A ROM bootloader for RSE that supports chainloading a second immutable boot
16 - Hardware-accelerated crypto operations using the built-in CryptoCell-3xx ROM
20 - A DMA Initial Command Sequence placed at offset 0x1F000 in the ROM.
31 address for the DMA ICS concatenation with the ROM code. The build
33 correct address is 0x1F000, instead of 0x1E000. Some distributed ROM binaries
36 If a ROM binary does not boot, it can be checked for this error using the
41 xxd -s 0x1F000 rom.bin
43 If there is no output, or the output is all zero-words, then the ROM binary is
44 affected by the issue. It is possible to fix a ROM binary affected by the
[all …]
|
| /trusted-firmware-m-latest/platform/ext/target/arm/rse/common/bl1/scripts/ |
| D | dma_config.yaml | 8 rom:
41 - storage_location: "rom"
42 execution_location: "rom"
51 - storage_location: "rom"
52 execution_location: "rom"
60 - storage_location: "rom"
61 execution_location: "rom"
71 - storage_location: "rom"
72 execution_location: "rom"
81 - storage_location: "rom"
[all …]
|
| /trusted-firmware-m-latest/platform/ext/target/nxp/common/Native_Driver/drivers/ |
| D | fsl_iap_kbp.h | 22 /*! @brief ROM API status group number */
25 /*! @brief ROM API status codes. */
28 …kStatus_RomApiExecuteCompleted = kStatus_Success, /*!< ROM successfully process the whole sb file/…
30 …MAKE_STATUS(kStatusGroup_RomApi, 1), /*!< ROM needs more data to continue processing the boot imag…
39 * @brief Details of the operation to be performed by the ROM.
187 * @brief Initialize ROM API for a given operation.
189 * Inits the ROM API based on the options provided by the application in the second
205 * @brief Cleans up the ROM API context.
218 * data from the boot image (SB file) that is to be processed. The ROM will perform
223 * @param session Current ROM context pointer.
[all …]
|
| D | fsl_iap.c | 209 /*! Get pointer to flash driver API table in ROM. */
278 … runCmdFuncOption.commandAddr = 0x1300413bU; /*!< get the flash erase api location adress in rom */ in FLASH_Erase()
301 …runCmdFuncOption.commandAddr = 0x1300419dU; /*!< get the flash program api location adress in rom*/ in FLASH_Program()
316 /*!< get the flash read api location adress in rom*/ in FLASH_Read()
323 /*!< get the flash read api location adress in rom*/ in FLASH_Read()
361 …uncOption.commandAddr = 0x1300427dU; /*!< get the flash verify program api location adress in rom*/ in FLASH_VerifyProgram()
609 * @brief Initialize ROM API for a given operation.
611 * Inits the ROM API based on the options provided by the application in the second
621 * @brief Cleans up the ROM API context.
636 * data from the boot image (SB file) that is to be processed. The ROM will perform
[all …]
|
| /trusted-firmware-m-latest/docs/design_docs/booting/ |
| D | bl1.rst | 13 Some devices that use TF-M will require initial boot code that is stored in ROM.
22 Henceforth any bootloader stored in ROM will be referred to as BL1, as it would
29 A reference ROM bootloader BL1 has now being added with the same motivation -
37 The reference ROM bootloader provides the following features:
39 - A split between code being stored in ROM and in other non-volatile memory.
42 ROM-only bootloaders.
49 constrained in flash space but have ROM.
67 BL1 is split into two distinct boot stages, BL1_1 which is stored in ROM and
73 Bugs in ROM bootloaders usually cannot be fixed once a device is provisioned /
74 in the field, as ROM code is immutable the only option is fixing the bug in
[all …]
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CA7/RTE/Device/ARMCA7/ |
| D | ARMCA7_gcc.ld | 4 ROM (rx) : ORIGIN = __ROM_BASE, LENGTH = __ROM_SIZE
45 } > ROM
50 } > ROM
56 } > ROM
68 } > ROM
77 } > ROM
|
| D | ARMCA7.ld | 5 ROM (rx) : ORIGIN = __ROM_BASE, LENGTH = __ROM_SIZE
47 } > ROM
52 } > ROM
58 } > ROM
70 } > ROM
79 } > ROM
|
| D | mem_ARMCA7.h | 38 /*--------------------- ROM Configuration ------------------------------------
40 // <h> ROM Configuration
42 // <o0> ROM Base Address <0x0-0xFFFFFFFF:0x100000>
43 // <o1> ROM Size (in Bytes) <0x0-0xFFFFFFFF:0x100000>
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CA9/RTE/Device/ARMCA9/ |
| D | ARMCA9_gcc.ld | 4 ROM (rx) : ORIGIN = __ROM_BASE, LENGTH = __ROM_SIZE
45 } > ROM
50 } > ROM
56 } > ROM
68 } > ROM
77 } > ROM
|
| D | ARMCA9.ld | 5 ROM (rx) : ORIGIN = __ROM_BASE, LENGTH = __ROM_SIZE
47 } > ROM
52 } > ROM
58 } > ROM
70 } > ROM
79 } > ROM
|
| D | mem_ARMCA9.h | 38 /*--------------------- ROM Configuration ------------------------------------
40 // <h> ROM Configuration
42 // <o0> ROM Base Address <0x0-0xFFFFFFFF:0x100000>
43 // <o1> ROM Size (in Bytes) <0x0-0xFFFFFFFF:0x100000>
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CA5/RTE/Device/ARMCA5/ |
| D | ARMCA5_gcc.ld | 4 ROM (rx) : ORIGIN = __ROM_BASE, LENGTH = __ROM_SIZE
45 } > ROM
50 } > ROM
56 } > ROM
68 } > ROM
77 } > ROM
|
| D | mem_ARMCA5.h | 38 /*--------------------- ROM Configuration ------------------------------------
40 // <h> ROM Configuration
42 // <o0> ROM Base Address <0x0-0xFFFFFFFF:0x100000>
43 // <o1> ROM Size (in Bytes) <0x0-0xFFFFFFFF:0x100000>
|
| /trusted-firmware-m-latest/lib/ext/mbedcrypto/mbedcrypto_config/ |
| D | tfm_mbedcrypto_config_profile_small_client.h | 90 * Use precomputed AES tables stored in ROM.
92 * Uncomment this macro to use precomputed AES tables stored in ROM.
95 * Tradeoff: Using precomputed ROM tables reduces RAM usage by ~8kb
98 * It comes at the cost of additional ~8kb ROM use (resp. ~2kb if \c
100 * performance if ROM access is slower than RAM access.
110 * Use less ROM/RAM for AES tables.
113 * ROM / RAM (depending on the value of \c MBEDTLS_AES_ROM_TABLES)
117 * Tradeoff: Uncommenting this reduces the RAM / ROM footprint
171 * Enable an implementation of SHA-256 that has lower ROM footprint but also
254 * Use only 128-bit keys in AES operations to save ROM.
|
| D | tfm_mbedcrypto_config_profile_small.h | 90 * Use precomputed AES tables stored in ROM.
92 * Uncomment this macro to use precomputed AES tables stored in ROM.
95 * Tradeoff: Using precomputed ROM tables reduces RAM usage by ~8kb
98 * It comes at the cost of additional ~8kb ROM use (resp. ~2kb if \c
100 * performance if ROM access is slower than RAM access.
110 * Use less ROM/RAM for AES tables.
113 * ROM / RAM (depending on the value of \c MBEDTLS_AES_ROM_TABLES)
117 * Tradeoff: Uncommenting this reduces the RAM / ROM footprint
171 * Enable an implementation of SHA-256 that has lower ROM footprint but also
258 * Use only 128-bit keys in AES operations to save ROM.
|
| D | tfm_mbedcrypto_config_profile_medium_client.h | 90 * Use precomputed AES tables stored in ROM.
92 * Uncomment this macro to use precomputed AES tables stored in ROM.
95 * Tradeoff: Using precomputed ROM tables reduces RAM usage by ~8kb
98 * It comes at the cost of additional ~8kb ROM use (resp. ~2kb if \c
100 * performance if ROM access is slower than RAM access.
110 * Use less ROM/RAM for AES tables.
113 * ROM / RAM (depending on the value of \c MBEDTLS_AES_ROM_TABLES)
117 * Tradeoff: Uncommenting this reduces the RAM / ROM footprint
182 * Enable an implementation of SHA-256 that has lower ROM footprint but also
265 * Use only 128-bit keys in AES operations to save ROM.
|
| D | tfm_mbedcrypto_config_profile_medium.h | 90 * Use precomputed AES tables stored in ROM.
92 * Uncomment this macro to use precomputed AES tables stored in ROM.
95 * Tradeoff: Using precomputed ROM tables reduces RAM usage by ~8kb
98 * It comes at the cost of additional ~8kb ROM use (resp. ~2kb if \c
100 * performance if ROM access is slower than RAM access.
110 * Use less ROM/RAM for AES tables.
113 * ROM / RAM (depending on the value of \c MBEDTLS_AES_ROM_TABLES)
117 * Tradeoff: Uncommenting this reduces the RAM / ROM footprint
182 * Enable an implementation of SHA-256 that has lower ROM footprint but also
269 * Use only 128-bit keys in AES operations to save ROM.
|
| D | tfm_mbedcrypto_config_profile_large_client.h | 90 * Use precomputed AES tables stored in ROM.
92 * Uncomment this macro to use precomputed AES tables stored in ROM.
95 * Tradeoff: Using precomputed ROM tables reduces RAM usage by ~8kb
98 * It comes at the cost of additional ~8kb ROM use (resp. ~2kb if \c
100 * performance if ROM access is slower than RAM access.
110 * Use less ROM/RAM for AES tables.
113 * ROM / RAM (depending on the value of \c MBEDTLS_AES_ROM_TABLES)
117 * Tradeoff: Uncommenting this reduces the RAM / ROM footprint
|
| D | tfm_mbedcrypto_config_profile_large.h | 90 * Use precomputed AES tables stored in ROM.
92 * Uncomment this macro to use precomputed AES tables stored in ROM.
95 * Tradeoff: Using precomputed ROM tables reduces RAM usage by ~8kb
98 * It comes at the cost of additional ~8kb ROM use (resp. ~2kb if \c
100 * performance if ROM access is slower than RAM access.
110 * Use less ROM/RAM for AES tables.
113 * ROM / RAM (depending on the value of \c MBEDTLS_AES_ROM_TABLES)
117 * Tradeoff: Uncommenting this reduces the RAM / ROM footprint
|
| /trusted-firmware-m-latest/docs/platform/arm/rse/ |
| D | readme.rst | 13 RSE initially boots from immutable code (BL1_1) in its internal ROM, before
79 To run the built images, first the ROM image must be created from the bl1_1
80 binary and the ROM DMA Initial Command Sequence (ICS).::
85 -o rom.bin -Binary
169 The RSE ROM binary should be placed in RSE ROM at ``0x11000000`` and the host
|
| D | rse_provisioning.rst | 70 AEAD encryption support in the cc312-rom-lib driver. The
76 TCI mode and cold-reset. Production ROM implementations must disable
77 ``TFM_DUMMY_PROVISIONING``, which will cause RSE to loop in the ROM until either
81 mode will be set by the ROM code.
105 The state of the RSE ROM boot/provisioning flow is signalled outside of the RSE
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/Core/Template/Device_A/Config/ |
| D | mem_Device.h | 35 /*--------------------- ROM Configuration ------------------------------------
37 // <h> ROM Configuration
38 // <o0> ROM Base Address <0x0-0xFFFFFFFF:8>
39 // <o1> ROM Size (in Bytes) <0x0-0xFFFFFFFF:8>
|
| /trusted-firmware-m-latest/platform/ext/target/arm/rse/rdfremont/ |
| D | rse_memory_sizes.h | 36 * this must match the size configured into the ROM part of the ICS.
39 /* How much space in ROM is used for the DMA Initial Command Sequence */
|
| /trusted-firmware-m-latest/platform/ext/target/arm/rse/tc/ |
| D | rse_memory_sizes.h | 38 * this must match the size configured into the ROM part of the ICS.
41 /* How much space in ROM is used for the DMA Initial Command Sequence */
|
| /trusted-firmware-m-latest/platform/ext/target/arm/rse/kronos/ |
| D | rse_memory_sizes.h | 39 * this must match the size configured into the ROM part of the ICS.
42 /* How much space in ROM is used for the DMA Initial Command Sequence */
|
123456
