Home
last modified time | relevance | path

Searched refs:flash (Results 326 – 350 of 2906) sorted by relevance

1...<<11121314151617181920>>...117

/Zephyr-4.1.0/dts/xtensa/espressif/esp32/
Desp32_wrover_e_n4r2.dtsi11 gpio-reserved-ranges = <6 6>, <16 2>, // flash&psram
19 /* 4MB flash */
Desp32_wrover_e_n4r8.dtsi11 gpio-reserved-ranges = <6 6>, <16 2>, // flash&psram
19 /* 4MB flash */
Desp32_wrover_e_n8r2.dtsi11 gpio-reserved-ranges = <6 6>, <16 2>, // flash&psram
19 /* 8MB flash */
/Zephyr-4.1.0/dts/arm/silabs/
Defr32fg13p233f512gm48.dtsi20 flash-controller@400e0000 {
21 flash0: flash@0 {
Dsim3u167.dtsi21 flash-controller@4002e000 {
22 flash0: flash@0 {
/Zephyr-4.1.0/doc/build/flashing/
Dconfiguration.rst6 Zephyr supports setting up configuration for flash runners (invoked from
7 :ref:`west flash<west-flashing>`) which allows for customising how commands are used when
11 which would prevent multiple erase tasks running in a single ``west flash`` invocation, which
27 child, this then contains a map of commands as they would be provided to the flash runner e.g.
29 are grouped by flash runner, and by qualifiers/boards). Commands have associated runners that
39 targets, or to ``last`` which will be ran once for the final image flash per set of board targets.
71 # flash runners
85 Commands that are supported by flash runners can be used as normal when flashing non-sysbuild
87 multiple images, the flash runner run once configuration will be applied.
97 Once built with an nrf5340dk connected, the following command can be used to flash the board with
[all …]
/Zephyr-4.1.0/doc/develop/west/
Dwithout-west.rst81 Running build system targets like ``ninja flash``, ``ninja debug``,
83 <west-build-flash-debug>`. For example, ``ninja flash`` calls ``west
84 flash``\ [#wbninja]_. If you don't have west installed on your system, running
85 those targets will fail. You can of course still flash and debug using
86 any :ref:`flash-debug-host-tools` which work for your board (and which those
109 to flash and debug, you must specify the west directory. This can be
121 invoke ``ninja flash``, ``debug``, etc. The one exception is if you
123 line like ``west build -t flash``. In that case, west is run twice:
125 flash``. Even in this case, ``ninja`` is only run once, as ``ninja
126 flash``. This is because these build system targets depend on an
[all …]
/Zephyr-4.1.0/dts/arm/nuvoton/
Dnpcx9mfp.dtsi15 flash0: flash@10058000 {
19 flash1: flash@64000000 {
55 /* quad spi bus configuration of nor flash device */
/Zephyr-4.1.0/boards/arm/v2m_musca_b1/
Dv2m_musca_b1_musca_b1_ns.dts22 zephyr,flash = &flash0;
44 flash0: flash@a070000 {
45 /* Embedded flash */
/Zephyr-4.1.0/boards/nxp/mimxrt685_evk/
DCMakeLists.txt16 "update your flash configuration block data")
18 # Include flash configuration block for R685 EVK from NXP's HAL.
19 # This configuration block may need modification if another flash chip is
/Zephyr-4.1.0/boards/nxp/mimxrt700_evk/
DCMakeLists.txt17 "update your flash configuration block data")
19 # Include flash configuration block for RT7xx EVK from NXP's HAL.
20 # This configuration block may need modification if another flash chip is
/Zephyr-4.1.0/soc/nxp/rw/
DKconfig31 application from an external flash device.
41 The flash config offset provides the boot ROM with the on-board
42 flash type and parameters. The boot ROM requires a fixed flash conifg
/Zephyr-4.1.0/tests/subsys/llext/boards/
Dqemu_arc_qemu_arc_em.overlay3 compatible = "zephyr,sim-flash";
10 compatible = "soc-nv-flash";
Dqemu_cortex_a9.overlay3 compatible = "zephyr,sim-flash";
10 compatible = "soc-nv-flash";
Dqemu_cortex_r5.overlay3 compatible = "zephyr,sim-flash";
10 compatible = "soc-nv-flash";
/Zephyr-4.1.0/drivers/flash/
DKconfig.smartbond5 bool "Renesas SmartBond(tm) flash driver"
13 Enable flash driver for Renesas SmartBond(tm) MCU family.
DKconfig.cc13xx_cc26xx5 bool "TI SimpleLink CC13xx/CC26xx flash controller driver"
13 Enables TI SimpleLink CC13xx/CC26xx flash controller driver.
DKconfig.cc23x07 bool "TI SimpleLink CC23x0 flash controller driver"
14 Enables TI SimpleLink CC23x0 flash controller driver.
Dflash_stm32g0x.c59 volatile uint32_t *flash = (uint32_t *)(offset + FLASH_STM32_BASE_ADDRESS); in write_dword() local
80 if ((flash[0] != 0xFFFFFFFFUL || in write_dword()
81 flash[1] != 0xFFFFFFFFUL) && val != 0UL) { in write_dword()
93 flash[0] = (uint32_t)val; in write_dword()
94 flash[1] = (uint32_t)(val >> 32); in write_dword()
/Zephyr-4.1.0/tests/bsim/bluetooth/host/privacy/peripheral/test_scripts/
Drun_test_rpa_expired.sh20 -RealEncryption=1 -flash="${simulation_id}.central.log.bin" -flash_erase
24 -RealEncryption=1 -flash="${simulation_id}.peripheral.log.bin" -flash_erase
/Zephyr-4.1.0/tests/drivers/flash/stm32/boards/
Ddisco_l475_iot1.overlay7 /* Do not use the storage-partition of the external qspi-NOR flash */
16 /* Reserve 4KiB of flash for storage_partition. */
/Zephyr-4.1.0/dts/arm/st/f3/
Dstm32f302X8.dtsi16 flash-controller@40022000 {
17 flash0: flash@8000000 {
/Zephyr-4.1.0/dts/arm/nxp/
Dnxp_kv5xf512vlx24.dtsi20 flash0: flash@10000000 {
21 compatible = "soc-nv-flash";
/Zephyr-4.1.0/dts/arm/st/f4/
Dstm32f417Xg.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
/Zephyr-4.1.0/dts/arm/st/l1/
Dstm32l151Xb-a.dtsi16 flash-controller@40023c00 {
17 flash0: flash@8000000 {

1...<<11121314151617181920>>...117