/Zephyr-4.1.0/samples/sensor/tmp112/ |
D | README.rst | 21 To build and flash the sample for the :zephyr:board:`frdm_k64f`: 26 :goals: build flash
|
/Zephyr-4.1.0/drivers/flash/ |
D | Kconfig.nrf_mram | 8 bool "Nordic Semiconductor flash driver for MRAM" 16 Enables Nordic Semiconductor flash driver for MRAM in direct write mode.
|
D | flash_stm32l4x.c | 72 volatile uint32_t *flash = (uint32_t *)(offset + FLASH_STM32_BASE_ADDRESS); in write_dword() local 96 if ((flash[0] != 0xFFFFFFFFUL || in write_dword() 97 flash[1] != 0xFFFFFFFFUL) && val != 0UL) { in write_dword() 120 flash[0] = (uint32_t)val; in write_dword() 121 flash[1] = (uint32_t)(val >> 32); in write_dword()
|
D | Kconfig.nor | 24 bool "Fixed flash configuration" 39 bool "Read flash parameters at runtime" 41 Read all flash device characteristics from the device at runtime. 62 bool "Sleep while waiting for flash operations to complete" 68 result in significant flash savings if this driver is the only user 76 The delay between polling while waiting for the flash to finish
|
/Zephyr-4.1.0/dts/common/nordic/ |
D | nrf52840_partition.dtsi | 10 zephyr,flash = &flash0; 37 * The flash starting at 0x000f8000 and ending at
|
D | nrf52840_partition_uf2_sdv7.dtsi | 11 zephyr,flash = &flash0; 18 * Default flash layout for nrf52840 using UF2 and SoftDevice s140 v7
|
/Zephyr-4.1.0/boards/atmel/sam/sam_e70_xplained/doc/ |
D | index.rst | 59 (General-Purpose NVM bit 1). The flash procedure will ensure that GPNVM1 is 62 If your chip has a security bit GPNVM0 set you will be unable to program flash 65 contents of the SAM E70 flash memory: 69 (flash erasing procedure is started when the erase line is asserted for at 91 USB debug port. Then build and flash the :zephyr:code-sample:`hello_world` 97 :goals: build flash 106 :goals: build flash 110 You can flash the image using an external debug adapter such as J-Link
|
/Zephyr-4.1.0/boards/atmel/sam/sam_v71_xult/doc/ |
D | index.rst | 62 of GPNVM1 (General-Purpose NVM bit 1). The flash procedure will ensure that 65 If your chip has a security bit GPNVM0 set you will be unable to program flash 68 full contents of the SAM V71 flash memory: 72 on (flash erasing procedure is started when the erase line is asserted for 94 USB debug port. Then build and flash the :zephyr:code-sample:`hello_world` 100 :goals: build flash 109 :goals: build flash 113 You can flash the image using an external debug adapter such as J-Link
|
/Zephyr-4.1.0/soc/espressif/esp32/ |
D | Kconfig | 39 When ESP32 exits deep sleep, the CPU and the flash chip are powered on 41 proceed to load code from flash. Some flash chips need sufficient 44 some flash chip types need more than that. 49 If you are seeing "flash read err, 1000" message printed to the
|
/Zephyr-4.1.0/drivers/hwinfo/ |
D | hwinfo_sam.c | 37 uint8_t *flash = (uint8_t *)CONFIG_FLASH_BASE_ADDRESS; in hwinfo_sam_read_device_id() local 53 sam_uid[i] = flash[i]; in hwinfo_sam_read_device_id()
|
/Zephyr-4.1.0/boards/st/nucleo_l053r8/support/ |
D | openocd.cfg | 11 # Add the second flash bank. 13 flash bank $_FLASHNAME stm32lx 0 0 0 0 $_TARGETNAME
|
/Zephyr-4.1.0/boards/st/nucleo_l073rz/support/ |
D | openocd.cfg | 11 # Add the second flash bank. 13 flash bank $_FLASHNAME stm32lx 0 0 0 0 $_TARGETNAME
|
/Zephyr-4.1.0/boards/nxp/vmu_rt1170/ |
D | CMakeLists.txt | 12 # Include flash configuration block for RT1170 EVK from NXP's HAL. 13 # This configuration block may need modification if another flash chip is
|
/Zephyr-4.1.0/boards/st/stm32l562e_dk/ |
D | stm32l562e_dk.dts | 21 zephyr,flash = &flash0; 52 /* 2KB at the end of 512KB flash is set for storage */
|
/Zephyr-4.1.0/dts/arm/st/f3/ |
D | stm32f302Xc.dtsi | 16 flash-controller@40022000 { 17 flash0: flash@8000000 {
|
/Zephyr-4.1.0/boards/ambiq/apollo3_evb/doc/ |
D | index.rst | 11 - Up to 1 MB of flash memory for code/data 34 Build the Zephyr kernel and application, then flash it to the device: 39 :goals: flash 42 ``west flash`` requires `SEGGER J-Link software`_ and `pylink`_ Python module
|
/Zephyr-4.1.0/boards/peregrine/sam4l_wm400_cape/doc/ |
D | index.rst | 57 came with a SAM-BA bootloader that only can be used to flash the software. 80 USB debug port. Then build and flash the :zephyr:code-sample:`hello_world` 86 :goals: build flash 93 USB debug port pressing the S1 button. Then build and flash the 100 :goals: build flash 101 :flash-args: -r bossac
|
/Zephyr-4.1.0/boards/others/promicro_nrf52840/doc/ |
D | index.rst | 76 west flash 85 PyOCD and openOCD can be used to flash and debug this board. 91 it is possible to flash anything directly using openOCD: 111 #. Erase flash: 129 flash write_image erase nice_nano_bootloader-0.9.2_s140_6.1.1.hex 135 mon flash write_image erase nice_nano_bootloader-0.9.2_s140_6.1.1.hex
|
/Zephyr-4.1.0/samples/sensor/bme280/ |
D | README.rst | 44 :goals: build flash 51 flash with: 55 :goals: build flash 66 flash with: 70 :goals: build flash 82 flash with: 86 :goals: build flash 92 Build and flash with: 96 :goals: build flash 121 :goals: build flash
|
/Zephyr-4.1.0/boards/seeed/xiao_esp32c6/doc/ |
D | index.rst | 9 It has a 320KB ROM, a 512KB SRAM, and works with external flash. 16 This board is based on the ESP32-C6 with 4MB of flash, integrating 2.4 GHz Wi-Fi 6, 87 The sysbuild makes possible to build and flash all necessary images needed to 121 With ``--sysbuild`` option the bootloader will be re-build and re-flash 129 During the development cycle, it is intended to build & flash as quickly possible. 137 Remember that bootloader (MCUboot) needs to be flash at least once. 139 Build and flash applications as usual (see :ref:`build_an_application` and 147 The usual ``flash`` target will work with the ``xiao_esp32c6`` board 154 :goals: flash 187 :goals: build flash
|
/Zephyr-4.1.0/boards/lilygo/ttgo_t8s3/doc/ |
D | index.rst | 20 This board is based on the ESP32-S3 with 16MB of flash, WiFi and BLE support. It 123 The sysbuild makes possible to build and flash all necessary images needed to 157 With ``--sysbuild`` option the bootloader will be re-build and re-flash 165 During the development cycle, it is intended to build & flash as quickly possible. 173 Remember that bootloader (MCUboot) needs to be flash at least once. 175 Build and flash applications as usual (see :ref:`build_an_application` and 183 The usual ``flash`` target will work with the ``ttgo_t8s3`` board target 190 :goals: flash 194 ``west flash`` (e.g. ``west flash --esp-baud-rate 115200``).
|
/Zephyr-4.1.0/boards/lilygo/ttgo_t8c3/doc/ |
D | index.rst | 19 This board is based on the ESP32-C3 with 4MB of flash, WiFi and BLE support. It 110 The sysbuild makes possible to build and flash all necessary images needed to 144 With ``--sysbuild`` option the bootloader will be re-build and re-flash 152 During the development cycle, it is intended to build & flash as quickly possible. 160 Remember that bootloader (MCUboot) needs to be flash at least once. 162 Build and flash applications as usual (see :ref:`build_an_application` and 170 The usual ``flash`` target will work with the ``ttgo_t8c3`` board target. 176 :goals: flash 180 ``west flash`` (e.g. ``west flash --esp-baud-rate 115200``).
|
/Zephyr-4.1.0/dts/arm/st/l0/ |
D | stm32l0.dtsi | 22 zephyr,flash-controller = &flash; 111 flash: flash-controller@40022000 { label 112 compatible = "st,stm32-flash-controller", "st,stm32f1-flash-controller"; 119 flash0: flash@8000000 { 120 compatible = "st,stm32l0-nv-flash", "st,stm32-nv-flash", 121 "soc-nv-flash";
|
/Zephyr-4.1.0/soc/nxp/kinetis/ |
D | Kconfig | 91 bool "Kinetis flash configuration field" 94 Include the 16-byte flash configuration field that stores default 101 hex "Kinetis flash configuration field offset" 110 backdoor key access, mass erase, factory access, and flash security 127 devices. For program flash only devices, this byte is reserved. 130 hex "Data flash protection byte (FDPROT)" 135 devices. For program flash only devices, this byte is reserved.
|
/Zephyr-4.1.0/boards/gd/gd32a503v_eval/doc/ |
D | index.rst | 10 to 120-MHz with flash accesses zero wait states, 384kiB of Flash, 48kiB of 70 allow flash programming and debug over USB. There are also program and debug 96 #. To flash an image: 101 :goals: flash 118 The GD32A503 MCU have a ROM bootloader which allow flash programming. User 135 #. To flash an image: 139 west flash -r gd32isp [--port=/dev/ttyUSB0]
|