Searched refs:flash (Results 426 – 450 of 2906) sorted by relevance
1...<<11121314151617181920>>...117
| /Zephyr-4.1.0/dts/arm/st/f3/ |
| D | stm32f373Xc.dtsi | 16 flash-controller@40022000 {
17 flash0: flash@8000000 {
|
| /Zephyr-4.1.0/boards/sparkfun/pro_micro_rp2040/ |
| D | sparkfun_pro_micro_rp2040.dts | 18 zephyr,flash = &flash0;
19 zephyr,flash-controller = &ssi;
31 /* 16MB of flash minus the 0x100 used for
50 * Usable flash. Starts at 0x100, after the bootloader. The partition
|
| /Zephyr-4.1.0/soc/espressif/common/ |
| D | Kconfig.flash | 36 modules, please don't disable this, otherwise your flash may not work in 4-bit
77 bool "SPI flash ROM driver patched functions"
80 Enable this flag to use patched versions of SPI flash ROM driver functions.
82 to flash on ESP32-D2WD; (2) main SPI flash is connected to non-default pins; (3) main
83 SPI flash chip is manufactured by ISSI.
86 bool "Support flash chips of XMC (READ HELP FIRST)"
101 output 1.9V instead. This helps prevent flash chip from browning out
102 during flash programming operations.
|
| D | Kconfig.spiram | 15 parallel with the main SPI flash chip.
122 If enabled, instructions in flash will be moved into PSRAM on startup.
132 If enabled, rodata in flash will be moved into PSRAM on startup.
155 1.8V flash and 1.8V psram, this value can only be one of 6, 7, 8, 9, 10, 11, 16, 17.
163 1.8V flash and 1.8V psram, this value can only be one of 6, 7, 8, 9, 10, 11, 16, 17.
196 For ESP32-PICO chip, the psram share clock with flash, so user do not need to configure the clock
203 bool "Use custom SPI PSRAM WP(SD3) Pin when flash pins set in eFuse (read help)"
207 This setting is only used if the SPI flash pins have been overridden by setting the eFuses
208 SPI_PAD_CONFIG_xxx, and the SPI flash mode is DIO or DOUT.
211 ESP32 pin "SD_DATA_3" or SPI flash pin "IO2") is not specified in eFuse. The psram only has QPI
[all …]
|
| /Zephyr-4.1.0/boards/atmel/sam/sam4e_xpro/doc/ |
| D | index.rst | 57 (General-Purpose NVM bit 1). The flash procedure will ensure that GPNVM1 is
60 If your chip has a security bit GPNVM0 set you will be unable to program flash
63 contents of the SAM4E flash memory:
67 (flash erasing procedure is started when the erase line is asserted for at
73 For flash the board Zephyr provides two paths. One uses the default OpenOCD
80 debug port. Then build and flash the :zephyr:code-sample:`hello_world` application.
85 :goals: build flash
96 USB port. Then build and flash the :zephyr:code-sample:`hello_world` application.
105 $ west flash -r bossac
|
| /Zephyr-4.1.0/boards/arm/v2m_musca_b1/ |
| D | v2m_musca_b1.dts | 25 zephyr,flash = &flash0;
63 flash0: flash@1a000000 {
64 /* Embedded flash */
|
| /Zephyr-4.1.0/dts/arm/st/wb0/ |
| D | stm32wb07.dtsi | 13 flash: flash-controller@40001000 { label
14 flash0: flash@10040000 {
|
| /Zephyr-4.1.0/samples/subsys/usb/mass/boards/ |
| D | rpi_pico.overlay | 16 * Usable flash. Starts at 0x100, after the bootloader. The partition
34 compatible = "zephyr,flash-disk";
|
| /Zephyr-4.1.0/boards/sipeed/longan_nano/support/ |
| D | openocd.cfg | 24 flash protect 0 0 last off
25 flash write_image erase $file
|
| /Zephyr-4.1.0/dts/arm/st/l0/ |
| D | stm32l010Xb.dtsi | 20 flash-controller@40022000 {
21 flash0: flash@8000000 {
|
| /Zephyr-4.1.0/dts/arm/st/h5/ |
| D | stm32h533Xe.dtsi | 29 flash-controller@40022000 {
30 flash0: flash@8000000 {
|
| /Zephyr-4.1.0/samples/sensor/mcux_acmp/ |
| D | README.rst | 35 :goals: flash
46 :goals: flash
57 :goals: flash
68 :goals: flash
79 :goals: flash
85 :goals: flash
|
| /Zephyr-4.1.0/subsys/dfu/ |
| D | Kconfig | 68 the access alignment required by used flash driver.
71 bool "Erase flash progressively when receiving new firmware"
74 If enabled, flash is erased as necessary when receiving new firmware,
83 If enabled, there will be available the function to check flash
84 integrity. It can be used to verify flash integrity after received
87 server to flash slot are performing properly.
|
| /Zephyr-4.1.0/boards/franzininho/esp32s2_franzininho/doc/ |
| D | index.rst | 12 - AES-XTS-256-based flash encryption
83 The sysbuild makes possible to build and flash all necessary images needed to
117 With ``--sysbuild`` option the bootloader will be re-build and re-flash
125 During the development cycle, it is intended to build & flash as quickly possible.
133 Remember that bootloader (MCUboot) needs to be flash at least once.
135 Build and flash applications as usual (see :ref:`build_an_application` and
143 The usual ``flash`` target will work with the ``esp32s2_franzininho`` board
150 :goals: flash
|
| /Zephyr-4.1.0/boards/gaisler/gr716a_mini/ |
| D | gr716a_mini.dts | 29 /* 256 Mbit SPI flash MX25L25635FZ2I-10G in 8 pin WSON package */
30 flash0: flash@0 {
|
| /Zephyr-4.1.0/samples/subsys/bindesc/read_bindesc/src/ |
| D | main.c | 15 const struct device *flash = DEVICE_DT_GET(DT_CHOSEN(zephyr_flash_controller)); variable
102 flash_read(flash, bindesc_offset, buffer, sizeof(buffer)); in main()
119 bindesc_open_flash(&handle, bindesc_offset, flash); in main()
|
| /Zephyr-4.1.0/boards/arm/v2m_musca_s1/ |
| D | v2m_musca_s1.dts | 25 zephyr,flash = &mram0;
68 flash0: flash@10200000 {
69 /* External QSPI flash */
|
| /Zephyr-4.1.0/drivers/flash/ |
| D | Kconfig.mspi | 4 menu "MSPI flash device driver"
11 MSPI flash drivers are enabled.
14 bool "MSPI flash device emulator"
|
| /Zephyr-4.1.0/boards/nxp/mcxw72_evk/ |
| D | mcxw72_evk_mcxw727c_cpu0.dts | 24 zephyr,flash = &flash;
25 zephyr,flash-controller = &fmu;
92 &flash {
|
| /Zephyr-4.1.0/dts/arm/ti/ |
| D | lm3s6965.dtsi | 30 flash-controller@400fd000 {
31 compatible = "ti,stellaris-flash-controller";
36 flash0: flash@0 {
37 compatible = "soc-nv-flash";
|
| /Zephyr-4.1.0/boards/nxp/frdm_mcxw72/ |
| D | frdm_mcxw72_mcxw727c_cpu0.dts | 24 zephyr,flash = &flash;
25 zephyr,flash-controller = &fmu;
92 &flash {
|
| /Zephyr-4.1.0/boards/m5stack/m5stack_atoms3_lite/doc/ |
| D | index.rst | 47 Build and flash applications as usual (see :ref:`build_an_application` and
55 The usual ``flash`` target will work with the ``m5stack_atoms3_lite`` board
62 :goals: flash
66 ``west flash`` (e.g. ``west flash --esp-baud-rate 115200``).
|
| /Zephyr-4.1.0/boards/m5stack/m5stack_atoms3/doc/ |
| D | index.rst | 49 Build and flash applications as usual (see :ref:`build_an_application` and
57 The usual ``flash`` target will work with the ``m5stack_atoms3`` board
64 :goals: flash
68 ``west flash`` (e.g. ``west flash --esp-baud-rate 115200``).
|
| /Zephyr-4.1.0/boards/m5stack/m5stack_atom_lite/doc/ |
| D | index.rst | 47 Build and flash applications as usual (see :ref:`build_an_application` and
55 The usual ``flash`` target will work with the ``m5stack_atom_lite`` board
62 :goals: flash
66 ``west flash`` (e.g. ``west flash --esp-baud-rate 115200``).
|
| /Zephyr-4.1.0/dts/arm/silabs/ |
| D | efm32_pg_1b.dtsi | 14 zephyr,flash-controller = &msc;
28 msc: flash-controller@400e0000 {
29 compatible = "silabs,gecko-flash-controller";
36 flash0: flash@0 {
37 compatible = "soc-nv-flash";
|
1...<<11121314151617181920>>...117
