Home
last modified time | relevance | path

Searched full:memory (Results 1 – 25 of 72) sorted by relevance

123

/mcuboot-latest/boot/cypress/MCUBootApp/
DExternalMemory.md1 ### External Memory support for Secondary Slot
5 Given document describes the use of external memory module as a secondary (upgrade) slot with Cypre…
8 The memory module present on board is S25FL512SAGMFI010 512-Mbit external Quad SPI NOR Flash.
10 Using external memory for secondary slot allows to nearly double the size of Boot Image.
14 The design is based on using SFDP command's auto-discovery functionality of memory module IC and Cy…
17 * The memory-module used is SFDP-compliant;
21 This corresponds to PSoC6's SMIF (Serial Memory InterFace) IP block mapping.
22 * The slot size for upgrade slot is even (or smaller) to erase size (0x40000) of given memory modul…
57 …PIO configurations, SMIF IP block configurations, SFDP protocol read and memory-config structure i…
59 After that MCUBootApp is ready to accept upgrade image from external memory module.
[all …]
DMCUBootApp.ld8 * input files should be mapped into the output file, and to control the memory
54 /* The MEMORY section below describes the location and size of blocks of memory in the target.
55 * Use this section to specify the memory regions available for allocation.
57 MEMORY
59 /* The ram and flash regions control RAM and flash memory allocation for the CM0+ core.
60 * You can change the memory allocation by editing the 'ram' and 'flash' regions.
62 * Using this memory region for other purposes will lead to unexpected behavior.
63 …* Your changes must be aligned with the corresponding memory regions for the CM4 core in 'xx_cm4_d…
71 * You can assign sections to this memory region for only one of the cores.
72 … * Note some middleware (e.g. BLE, Emulated EEPROM) can place their data into this memory region.
[all …]
Dcy_serial_flash_prog.c6 * attached serial flash memory. The variables used here must be placed at
8 * to know that there is an attached memory and its characteristics. Uses the
32 * Variables for informing programming tools that there is an attached memory device and what
33 * its characteristics are so it can be programmed just like the on-chip memory.
57 * This data can be placed anywhere in the internal memory, but it must be at a location that
60 * 1) Placing it in a dedicated memory block with a known address. (as done here)
71 * process and programming tools to determine key characteristics about the memory usage including
73 * (if any). This must consume a full row of flash memory row. The last entry is a checksum of the
Dmain.c54 * 0 - SMIF disabled (no external memory);
55 * 1, 2, 3 or 4 - slave select line memory module is connected to.
57 uint32_t smif_id = 1; /* Assume SlaveSelect_0 is used for External Memory */
125 * memory usage */ in main()
130 BOOT_LOG_INF("External Memory initialized w/ SFDP."); in main()
134 BOOT_LOG_ERR("External Memory initialization w/ SFDP FAILED: 0x%02x", (int)rc); in main()
DREADME.md34 Memory (stack) corruption of CM0p application can cause failure if SystemCall-served operations inv…
44 ### How to modify memory map
53 Now define and initialize `struct flash_area *boot_area_descs[]` with flash memory addresses and si…
115 __Note:__ It is also possible to place secondary (upgrade) slots in external memory module so resul…
116 For more details about External Memory usage, please refer to separate guiding document `ExternalMe…
152 …l memory support - pass `USE_EXTERNAL_FLASH=1` flag to `make` command in examples above. In this c…
/mcuboot-latest/boot/cypress/platforms/PSOC_062_2M/CM0P/GCC_ARM/
Dcy8c6xxa_cm0plus.ld8 * input files should be mapped into the output file, and to control the memory
54 /* The MEMORY section below describes the location and size of blocks of memory in the target.
55 * Use this section to specify the memory regions available for allocation.
57 MEMORY
59 /* The ram and flash regions control RAM and flash memory allocation for the CM0+ core.
60 * You can change the memory allocation by editing the 'ram' and 'flash' regions.
62 * Using this memory region for other purposes will lead to unexpected behavior.
63 …* Your changes must be aligned with the corresponding memory regions for the CM4 core in 'xx_cm4_d…
70 * You can assign sections to this memory region for only one of the cores.
71 … * Note some middleware (e.g. BLE, Emulated EEPROM) can place their data into this memory region.
[all …]
/mcuboot-latest/boot/cypress/BlinkyApp/linker/
DBlinkyApp_template.ld8 * input files should be mapped into the output file, and to control the memory
58 /* The MEMORY section below describes the location and size of blocks of memory in the target.
59 * Use this section to specify the memory regions available for allocation.
61 MEMORY
63 /* The ram and flash regions control RAM and flash memory allocation for the CM4 core.
64 * You can change the memory allocation by editing the 'ram' and 'flash' regions.
66 * Using this memory region for other purposes will lead to unexpected behavior.
67 …* Your changes must be aligned with the corresponding memory regions for CM0+ core in 'xx_cm0plus.…
74 * You can assign sections to this memory region for only one of the cores.
75 … * Note some middleware (e.g. BLE, Emulated EEPROM) can place their data into this memory region.
[all …]
/mcuboot-latest/boot/cypress/platforms/PSOC_062_2M/CM4/GCC_ARM/
Dcy8c6xxa_cm4_dual.ld8 * input files should be mapped into the output file, and to control the memory
57 /* The MEMORY section below describes the location and size of blocks of memory in the target.
58 * Use this section to specify the memory regions available for allocation.
60 MEMORY
62 /* The ram and flash regions control RAM and flash memory allocation for the CM4 core.
63 * You can change the memory allocation by editing the 'ram' and 'flash' regions.
65 * Using this memory region for other purposes will lead to unexpected behavior.
66 …* Your changes must be aligned with the corresponding memory regions for CM0+ core in 'xx_cm0plus.…
73 * You can assign sections to this memory region for only one of the cores.
74 … * Note some middleware (e.g. BLE, Emulated EEPROM) can place their data into this memory region.
[all …]
/mcuboot-latest/ext/mbedtls-asn1/include/mbedtls/
Dbignum.h42 #define MBEDTLS_ERR_MPI_ALLOC_FAILED -0x0010 /**< Memory allocation failed. */
218 * \return #MBEDTLS_ERR_MPI_ALLOC_FAILED if memory allocation failed.
234 * \return #MBEDTLS_ERR_MPI_ALLOC_FAILED if memory allocation failed
250 * \return #MBEDTLS_ERR_MPI_ALLOC_FAILED if memory allocation failed.
280 * information through branch prediction and/or memory access
284 * \return #MBEDTLS_ERR_MPI_ALLOC_FAILED if memory allocation failed.
304 * information through branch prediction and/or memory access
308 * \return #MBEDTLS_ERR_MPI_ALLOC_FAILED if memory allocation failed.
321 * \return #MBEDTLS_ERR_MPI_ALLOC_FAILED if memory allocation failed.
350 * \return #MBEDTLS_ERR_MPI_ALLOC_FAILED if memory allocation failed.
[all …]
/mcuboot-latest/docs/
DPORTING.md146 /*< Reads `len` bytes of flash memory at `off` to the buffer at `dst` */
149 /*< Writes `len` bytes of flash memory at `off` from the buffer at `src` */
152 /*< Erases `len` bytes of flash memory at `off` */
178 ## Memory management for Mbed TLS
180 `Mbed TLS` employs dynamic allocation of memory, making use of the pair
185 memory `Mbed TLS` uses the following call:
/mcuboot-latest/boot/cypress/BlinkyApp/
DReadme.md39 Memory (stack) corruption of CM0p application can cause failure if SystemCall-served operations inv…
84 **How to build upgrade image for external memory:**
86 To prepare MCUBootApp for work with external memory please refer to `MCUBootApp/ExternalMemory.md`.
88 For build BlinkyApp upgrade image for external memory use command:
94 `ERASED_VALUE` defines the memory cell contents in erased state. It is `0x00` for PSoC6's internal …
/mcuboot-latest/boot/bootutil/include/bootutil/
Dboot_record.h29 /** Error codes for using the shared memory area. */
56 * Add an image's all boot status information to the shared memory area
70 * Add application specific data to the shared memory area between the
/mcuboot-latest/boot/espressif/include/flash_map_backend/
Dflash_map_backend.h61 //! Reads `len` bytes of flash memory at `off` to the buffer at `dst`
64 //! Writes `len` bytes of flash memory at `off` from the buffer at `src`
67 //! Erases `len` bytes of flash memory at `off`
/mcuboot-latest/boot/espressif/port/esp32c2/ld/
Dbootloader.ld7 /** Simplified memory map for the bootloader.
8 * Make sure the bootloader can load into main memory without overwriting itself.
39 MEMORY
50 …* 3. Update (SRAM_DRAM_END + I_D_SRAM_OFFSET) in components/esp_system/ld/esp32c2/memory.ld.in to …
/mcuboot-latest/boot/espressif/port/esp32c6/ld/
Dbootloader.ld7 /** Simplified memory map for the bootloader.
8 * Make sure the bootloader can load into main memory without overwriting itself.
36 MEMORY
47 * 3. Update SRAM_DRAM_END in components/esp_system/ld/esp32c6/memory.ld.in to the same value.
/mcuboot-latest/boot/espressif/port/esp32h2/ld/
Dbootloader.ld7 /** Simplified memory map for the bootloader.
8 * Make sure the bootloader can load into main memory without overwriting itself.
37 MEMORY
48 * 3. Update SRAM_DRAM_END in components/esp_system/ld/esp32h2/memory.ld.in to the same value.
/mcuboot-latest/boot/cypress/cy_flash_pal/include/flash_map_backend/
Dflash_map_backend.h151 * Retrieve a memory-mapped flash device's base address.
161 /*< Reads `len` bytes of flash memory at `off` to the buffer at `dst` */
164 /*< Writes `len` bytes of flash memory at `off` from the buffer at `src` */
167 /*< Erases `len` bytes of flash memory at `off` */
/mcuboot-latest/boot/mynewt/mcuboot_config/
Dsyscfg.yml143 Store the boot state/measurements in shared memory.
145 the hash of the firmware image in a shared memory area. This data can
152 description: Save application specific data in shared memory (RAM).
/mcuboot-latest/boot/cypress/cy_flash_pal/flash_qspi/
Dflash_qspi.c195 /* The base address the memory slave is mapped to in the PSoC memory map.
196 Valid when the memory-mapped mode is enabled. */
198 /* The size allocated in the PSoC memory map, for the memory slave device.
199 The size is allocated from the base address. Valid when the memory mapped mode is enabled. */
/mcuboot-latest/boot/espressif/port/esp32c3/ld/
Dbootloader.ld7 /* Simplified memory map for the bootloader.
9 * The main purpose is to make sure the bootloader can load into main memory
13 MEMORY
/mcuboot-latest/boot/espressif/port/esp32s2/ld/
Dbootloader.ld7 /* Simplified memory map for the bootloader.
9 * The main purpose is to make sure the bootloader can load into main memory
13 MEMORY
/mcuboot-latest/boot/espressif/port/esp32s3/ld/
Dbootloader.ld7 /* Simplified memory map for the bootloader.
9 * The main purpose is to make sure the bootloader can load into main memory
13 MEMORY
/mcuboot-latest/boot/espressif/port/esp32/ld/
Dbootloader.ld7 /* Simplified memory map for the bootloader.
9 * The main purpose is to make sure the bootloader can load into main memory
13 MEMORY
/mcuboot-latest/boot/zephyr/
DKconfig.serial_recovery67 int "Stack buffer for unaligned memory writes"
74 memory access when data is written to a device with memory alignment
DKconfig456 memory usage; larger values allow it to support larger images.
490 - Retained memory area
491 - Retention partition of retained memory area
521 running application into a shared memory area.
524 bool "Store the boot state/measurements in shared memory area"
529 the hash of the firmware image in a shared memory area. This data can
567 flow, double variables to discover register or memory corruption.
575 flow, double variables to discover register or memory corruption, random

123