Searched refs:flash (Results 401 – 425 of 2906) sorted by relevance
1...<<11121314151617181920>>...117
/Zephyr-4.1.0/boards/nxp/frdm_mcxw71/ |
D | frdm_mcxw71.dts | 24 zephyr,flash = &flash; 25 zephyr,flash-controller = &fmu; 113 mx25r6435fm2il0: flash@0 { 126 /* this is the default (reset) mode for this flash */ 133 &flash {
|
/Zephyr-4.1.0/dts/arm/nuvoton/ |
D | m55m1h2l.dtsi | 29 fmc: flash-controller@40044000 { 30 flash0: flash@100000 {
|
/Zephyr-4.1.0/boards/quicklogic/qomu/ |
D | qomu_defconfig | 15 # EOS S3 Configuration Manager copies software from external flash to MCU 17 # Thus we do not use flash directly.
|
/Zephyr-4.1.0/dts/arm/ti/ |
D | msp432p4xx.dtsi | 20 flash0: serial-flash@0 { 21 compatible = "serial-flash";
|
/Zephyr-4.1.0/boards/nxp/s32z2xxdc2/ |
D | s32z2xxdc2_s32z270_rtu0.dts | 17 zephyr,flash = &cram0; 19 zephyr,flash-controller = &s26hs512t;
|
D | s32z2xxdc2_s32z270_rtu1.dts | 17 zephyr,flash = &cram1; 19 zephyr,flash-controller = &s26hs512t;
|
/Zephyr-4.1.0/dts/arm/st/f1/ |
D | stm32f100Xe.dtsi | 18 flash-controller@40022000 { 19 flash0: flash@8000000 {
|
D | stm32f103Xg.dtsi | 18 flash-controller@40022000 { 19 flash0: flash@8000000 { 21 * flash (512KB each) and two flash controllers. 23 * flash programming and you need the
|
D | stm32f103Xb.dtsi | 15 flash-controller@40022000 { 16 flash0: flash@8000000 {
|
/Zephyr-4.1.0/samples/subsys/nvs/ |
D | README.rst | 5 Store and retrieve data from flash using the NVS API. 11 module for non-volatile (flash) storage. In this application, 12 a counter is incremented on every reboot and stored in flash, 18 * A board with flash support 31 :goals: build flash
|
/Zephyr-4.1.0/drivers/flash/ |
D | flash_stm32wbx.c | 63 volatile uint32_t *flash = (uint32_t *)(offset + FLASH_STM32_BASE_ADDRESS); in write_dword() local 81 if ((flash[0] != 0xFFFFFFFFUL || in write_dword() 82 flash[1] != 0xFFFFFFFFUL) && val != 0UL) { in write_dword() 168 flash[0] = (uint32_t)val; in write_dword() 169 flash[1] = (uint32_t)(val >> 32); in write_dword()
|
/Zephyr-4.1.0/dts/riscv/wch/ch32v208/ |
D | ch32v208.dtsi | 51 flash: flash-controller@40022000 { label 52 compatible = "wch,ch32v20x_30x-flash-controller"; 57 flash0: flash@0 { 58 compatible = "soc-nv-flash";
|
/Zephyr-4.1.0/soc/espressif/common/ |
D | Kconfig.esptool | 13 bool "Choose flash mode automatically (please read help)" 16 This config option helps decide whether flash is Quad or Octal, but please note some limitations: 18 1. If the flash chip is an Octal one, even if one of "QIO", "QOUT", "DIO", "DOUT" options is 21 …2. If the flash chip is a Quad one, even if "OPI" is selected in `ESPTOOLPY_FLASHMODE`, our code w… 23 3. Please do not rely on this option when you are pretty sure that you are using Octal flash, 27 If your IRAM space is insufficient and you're aware of your flash type, 28 disable this option and select corresponding flash type options. 35 Mode the flash chip is flashed in, as well as the default mode for the 77 # fasted (see ESPTOOL-274), using dout instead. In ROM the flash mode 137 SPI flash size, in megabytes [all …]
|
/Zephyr-4.1.0/soc/altr/zephyr_nios2f/cpu/ |
D | README | 7 You will need the Quartus SDK in order to modify this CPU or flash it onto 13 To flash this CPU, use the nios2-configure-sof tool: 17 The 'make flash' target will also package up the kernel and CPU into a single
|
/Zephyr-4.1.0/boards/pjrc/teensy4/ |
D | teensy41.dts | 13 zephyr,flash-controller = &w25q64jvxgim; 14 zephyr,flash = &w25q64jvxgim; 23 /* WINBOND flash memory*/
|
/Zephyr-4.1.0/dts/arm/nxp/ |
D | nxp_lpc55S0x_common.dtsi | 78 iap: flash-controller@34000 { 85 flash0: flash@0 { 86 compatible = "soc-nv-flash"; 92 flash_reserved: flash@3d800 { 93 compatible = "soc-nv-flash"; 98 uuid: flash@3fc70 { 103 boot_rom: flash@3000000 { 104 compatible = "soc-nv-flash";
|
/Zephyr-4.1.0/boards/lilygo/ttgo_t7v1_5/doc/ |
D | index.rst | 18 This board is based on the ESP32-WROVER-E module with 4MB of flash (there 83 must be build (and flash) at least once. 102 The sysbuild makes possible to build and flash all necessary images needed to 136 With ``--sysbuild`` option the bootloader will be re-build and re-flash 144 During the development cycle, it is intended to build & flash as quickly possible. 152 Remember that bootloader (MCUboot) needs to be flash at least once. 154 Build and flash applications as usual (see :ref:`build_an_application` and 162 The usual ``flash`` target will work with the ``ttgo_t7v1_5`` board 169 :goals: flash 173 ``west flash`` (e.g. ``west flash --esp-baud-rate 115200``).
|
/Zephyr-4.1.0/soc/ti/simplelink/cc32xx/ |
D | Kconfig | 19 bool "Prepend debug header, disabling flash verification" if XIP 24 bool "Prepend debug header, disabling flash verification" if XIP
|
/Zephyr-4.1.0/boards/st/nucleo_f303k8/ |
D | board.cmake | 7 board_runner_args(pyocd "--flash-opt=-O reset_type=hw") 8 board_runner_args(pyocd "--flash-opt=-O connect_mode=under-reset")
|
/Zephyr-4.1.0/boards/st/nucleo_f334r8/ |
D | board.cmake | 7 board_runner_args(pyocd "--flash-opt=-O reset_type=hw") 8 board_runner_args(pyocd "--flash-opt=-O connect_mode=under-reset")
|
/Zephyr-4.1.0/boards/st/nucleo_g0b1re/ |
D | board.cmake | 7 board_runner_args(pyocd "--flash-opt=-O reset_type=hw") 8 board_runner_args(pyocd "--flash-opt=-O connect_mode=under-reset")
|
/Zephyr-4.1.0/boards/st/nucleo_g071rb/ |
D | board.cmake | 6 board_runner_args(pyocd "--flash-opt=-O reset_type=hw") 7 board_runner_args(pyocd "--flash-opt=-O connect_mode=under-reset")
|
/Zephyr-4.1.0/boards/st/stm32f429i_disc1/ |
D | board.cmake | 7 board_runner_args(pyocd "--flash-opt=-O reset_type=hw") 8 board_runner_args(pyocd "--flash-opt=-O connect_mode=under-reset")
|
/Zephyr-4.1.0/boards/st/nucleo_g070rb/ |
D | board.cmake | 6 board_runner_args(pyocd "--flash-opt=-O reset_type=hw") 7 board_runner_args(pyocd "--flash-opt=-O connect_mode=under-reset")
|
/Zephyr-4.1.0/dts/arm/st/f3/ |
D | stm32f334X8.dtsi | 22 flash-controller@40022000 { 23 flash0: flash@8000000 {
|
1...<<11121314151617181920>>...117