Home
last modified time | relevance | path

Searched +full:flash +full:- +full:specific (Results 1 – 25 of 269) sorted by relevance

1234567891011

/Zephyr-latest/include/zephyr/drivers/flash/
Dnpcx_flash_api_ex.h4 * SPDX-License-Identifier: Apache-2.0
14 #include <zephyr/drivers/flash.h>
22 * configuration such as status registers of nor flash, power on/off,
27 * NPCX Configure specific operation for Quad-SPI nor flash.
29 * It configures specific operation for Quad-SPI nor flash such as lock
30 * or unlock UMA mode, set write protection pin of internal flash, and
35 * NPCX Get specific operation for Quad-SPI nor flash.
37 * It returns current specific operation for Quad-SPI nor flash.
67 /* Specific NPCX QSPI devices control bits */
69 #define NPCX_EX_OP_INT_FLASH_WP BIT(1) /* Issue write protection of internal flash */
Dflash_simulator.h4 * SPDX-License-Identifier: Apache-2.0
15 * @brief Flash simulator specific API.
17 * Extension for flash simulator.
24 * in which the flash simulator emulates its flash memory content.
26 * @param[in] dev flash simulator device pointer.
/Zephyr-latest/boards/nxp/frdm_rw612/
DCMakeLists.txt2 # Copyright 2022-2023 NXP
4 # SPDX-License-Identifier: Apache-2.0
10 # This FCB is specific to the flash on this board, it won't work
11 # for boards with different flash chips. If you flash this FCB
12 # onto a board with a different flash chip you may break it.
/Zephyr-latest/doc/hardware/peripherals/
Dflash.rst3 Flash chapter
9 **Flash offset concept**
12 the flash memory beginning address. This rule shall be applied to
13 all flash controller regular memory that layout is accessible via
16 An exception from the rule may be applied to a vendor-specific flash
17 dedicated-purpose region (such a region obviously can't be covered under
/Zephyr-latest/dts/arm/st/f1/
Dstm32f103Xe.dtsi2 * Copyright (c) 2017 I-SENSE group of ICCS
5 * where 'x' is replaced for specific SoCs like {R,V,Z}
7 * SPDX-License-Identifier: Apache-2.0
15 flash-controller@40022000 {
16 flash0: flash@8000000 {
18 erase-block-size = <DT_SIZE_K(2)>;
Dstm32f103Xd.dtsi5 * where 'x' is replaced for specific SoCs like {R,V,Z}
7 * SPDX-License-Identifier: Apache-2.0
19 flash-controller@40022000 {
20 flash0: flash@8000000 {
22 erase-block-size = <DT_SIZE_K(2)>;
Dstm32f103Xb.dtsi2 * Copyright (c) 2017 I-SENSE group of ICCS
5 * where 'x' is replaced for specific SoCs like {C,R,T,V}
7 * SPDX-License-Identifier: Apache-2.0
15 flash-controller@40022000 {
16 flash0: flash@8000000 {
18 erase-block-size = <DT_SIZE_K(1)>;
/Zephyr-latest/soc/nxp/imxrt/
DKconfig2 # SPDX-License-Identifier: Apache-2.0
15 # Note- When SECOND_CORE_MCUX is set, the dependencies for this Kconfig
17 # requires the boot header is SOC specific.
24 application from an external flash device.
57 FlexSPI configuration block consists of parameters regarding specific
58 flash devices including read command sequence, quad mode enablement
60 parameter to be presented in serial nor flash.
97 placed in a specific address location to be pointed by the boot ROM.
122 by booting an image targeting the Cortex-M4 from the Cortex-M7 CPU.
123 The M4 image will be loaded from flash into RAM based off a
[all …]
/Zephyr-latest/soc/nxp/mcx/mcxc/
DKconfig2 # SPDX-License-Identifier: Apache-2.0
25 bool "MCXC flash configuration field"
28 Include the 16-byte flash configuration field that stores default
36 default $(dt_node_int_prop_hex,/soc/flash-controller@40020000,config-field-offset)
43 Leave SOC watchdog timer enabled at boot. The specific timeout
/Zephyr-latest/drivers/flash/
DKconfig.simulator1 # Flash simulator config
4 # SPDX-License-Identifier: Apache-2.0
7 bool "Flash simulator"
13 Enable the flash simulator.
23 a specific FLASH interface that requires aligned read access.
26 bool "Program-erase device"
30 Explicit erase (non-erase-on-write) Flash, which is device that requires erase
31 to erase-value prior to write as it only allows to change bits from erase-value
45 …If selected, writing to a non-erased program unit will succeed, otherwise, it will return an error.
46 Keep in mind that write operations can only change value of a bit from erase-value to the
[all …]
/Zephyr-latest/samples/sensor/mcux_lpcmp/
DREADME.rst1 .. zephyr:code-sample:: mcux_lpcmp
2 :name: NXP MCUX Low-power Analog Comparator (LPCMP)
3 :relevant-api: sensor_interface
5 Get analog comparator data from an NXP MCUX Low-power Analog Comparator (LPCMP).
10 This sample show how to use the NXP MCUX Low-power Analog Comparator (LPCMP) driver.
14 voltage of the DAC is set to 0 (for the specific chip, the user needs to
19 manual and board schematic to confirm which specific port is used and can
28 Building and Running for NXP FRDM-MCXN947
31 LPCMP positive input port voltage by changing the voltage input to J2-17.
33 .. zephyr-app-commands::
[all …]
/Zephyr-latest/samples/sysbuild/with_mcuboot/
DREADME.rst1 .. zephyr:code-sample:: with_mcuboot
11 creating a image specific Kconfig fragment.
13 Sysbuild specific settings
19 This is achieved with a sysbuild specific Kconfig configuration,
29 configures MCUboot to prevent downgrades and operate in upgrade-only mode.
33 .. zephyr-app-commands::
35 :zephyr-app: samples/sysbuild/with_mcuboot
38 :west-args: --sysbuild
43 .. code-block:: console
45 *** Booting Zephyr OS build v3.2.0-rc3-209-gdcf4201d3573 ***
[all …]
/Zephyr-latest/doc/hardware/emulator/
Dindex.rst13 These device emulators/simulators can be built for any target which has sufficient RAM and flash,
26 Drivers which are specific to some platform, like for example the
27 :ref:`native_sim specific drivers <native_sim_peripherals>` which
35 * A fake driver which pretends to be actual ADC, and can be used for testing higher-level API
38 * DT binding: :dtcompatible:`zephyr,adc-emul`
43 * DT binding: :dtcompatible:`zephyr,dma-emul`
46 * Emulate an EEPROM on a flash partition
48 * DT binding: :dtcompatible:`zephyr,emu-eeprom`
55 * DT binding: :dtcompatible:`zephyr,sim-eeprom`
65 **Flash simulator**
[all …]
/Zephyr-latest/samples/sensor/ds18b20/
DREADME.rst1 .. zephyr:code-sample:: ds18b20
2 :name: DS18B20 1-Wire Temperature Sensor
3 :relevant-api: sensor_interface w1_sensor
11 `DS18B20`_ 1-Wire temperature sensor.
31 https://www.analog.com/media/en/technical-documentation/data-sheets/ds18b20.pdf
33 Boards with a built-in DS18B20 or a board-specific overlay
37 or a board specific overlay file with an DS18B20 node is available.
40 .. zephyr-app-commands::
41 :zephyr-app: samples/sensor/ds18b20
42 :goals: build flash
[all …]
/Zephyr-latest/samples/bluetooth/hci_spi/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_spi
3 :relevant-api: hci_raw bluetooth spi_interface
21 You then need to ensure that your :ref:`devicetree <dt-guide>` defines a node
23 :dtcompatible:`zephyr,bt-hci-spi-slave`. This node sets an interrupt line to
30 You can then build this application and flash it onto your board in
31 the usual way; see :ref:`boards` for board-specific building and
39 Refer to :zephyr:code-sample-category:`bluetooth` for general Bluetooth information, and
40 to :ref:`96b_carbon_nrf51_bluetooth` for instructions specific to the
/Zephyr-latest/scripts/west_commands/runners/
Dhifive1.py3 # SPDX-License-Identifier: Apache-2.0
5 '''HiFive1-specific (flash only) runner.'''
13 '''Runner front-end for the HiFive1 board, using openocd.'''
25 return RunnerCaps(commands={'flash'})
34 raise ValueError('--gdb not provided at command line')
41 openocd_cmd = ([self.cfg.openocd, '-f', self.openocd_config])
42 gdb_cmd = ([self.cfg.gdb, self.cfg.elf_file, '--batch',
43 '-ex', 'set remotetimeout 240',
44 '-ex', 'target extended-remote localhost:3333',
45 '-ex', 'load',
[all …]
Dminichlink.py3 # SPDX-License-Identifier: Apache-2.0
5 """WCH CH32V00x specific runner."""
37 def capabilities(cls) -> RunnerCaps:
38 return RunnerCaps(commands={"flash"}, flash_addr=True, erase=True, reset=True)
43 "--minichlink", default="minichlink", help="path to the minichlink binary"
46 "--terminal",
49 help="open the terminal after flashing. Implies --reset.",
67 if command == "flash":
68 self.flash()
72 def flash(self): member in MiniChLinkBinaryRunner
[all …]
/Zephyr-latest/samples/sensor/magn_polling/
DREADME.rst1 .. zephyr:code-sample:: magn_polling
3 :relevant-api: sensor_interface
14 Board-specific overlays
21 that supports 32-bit SPI_WORD_SIZE. On the :zephyr:board:`rpi_pico`, the
22 :dtcompatible:`raspberrypi,pico-spi-pio` SPI driver provides this support,
31 With the sensor wired to the desired pins, build and flash with:
33 .. zephyr-app-commands::
34 :zephyr-app: samples/sensor/magn_polling
35 :goals: build flash
/Zephyr-latest/boards/intel/adsp/doc/
Dintel_adsp_generic.rst8 the Audio and Context Engine (ACE). These Xtensa-based ADSPs can be integrated
12 +----------+-----------------------------+
16 +----------+-----------------------------+
18 +----------+-----------------------------+
20 +----------+-----------------------------+
22 +----------+-----------------------------+
24 Intel open-sources firmware for its ADSP hardware under the Sound Open Firmware
26 Xtensa OS (XTOS) and run on a variety of Intel and non-Intel platforms.
30 `UP Xtreme i11-0001 series`_ (:ref:`intel_adsp_cavs25`) board as an example.
32 otherwise stated. You will be referred to the documentation for your specific
[all …]
/Zephyr-latest/dts/bindings/mtd/
Djedec,jesd216.yaml2 # Copyright (c) 2019-2020 Nordic Semiconductor ASA
3 # SPDX-License-Identifier: Apache-2.0
5 # Common properties used by nodes describing serial flash devices that
6 # are compatible with the JESD216 Serial Flash Discoverable Parameters
21 jedec-id:
22 type: uint8-array
27 description: flash capacity in bits
29 sfdp-bfp:
30 type: uint8-array
32 Contains the 32-bit words in little-endian byte order from the
[all …]
/Zephyr-latest/scripts/west_commands/
DREADME.txt2 tightly coupled to the zephyr tree. This includes the build, flash,
7 on the multi-repo need to be in upstream west, not here. Try to limit
8 what goes in here to Zephyr-specific features.
15 py -3 run_tests.py
/Zephyr-latest/doc/hardware/porting/
Dboard_porting.rst21 - Support for multi-core, multi-arch AMP (Asymmetrical Multi Processing) SoCs
22 - Support for multi-SoC boards
23 - Support for reusing the SoC and board Kconfig trees outside of the Zephyr
25 - Support for advanced use cases with :ref:`sysbuild`
26 - Removal of all existing arbitrary and inconsistent uses of Kconfig and folder
38 Some non-critical features, enhancements and improvements of the new hardware
47 with two options if they have an out-of-tree board (or SoC):
49 #. Convert the out-of-tree board to the current hardware model (recommended)
57 can then use the `example-application conversion Pull Request`_ as an example on
59 and works reliably in many cases (though multi-core SoCs may not be handled
[all …]
/Zephyr-latest/soc/nxp/kinetis/
DKconfig4 # SPDX-License-Identifier: Apache-2.0
35 Set this option to use the oscillator in low-power mode.
40 Set this option to use the oscillator in high-gain mode.
91 bool "Kinetis flash configuration field"
94 Include the 16-byte flash configuration field that stores default
101 hex "Kinetis flash configuration field offset"
105 hex "Flash security byte (FSEC)"
110 backdoor key access, mass erase, factory access, and flash security
114 hex "Flash nonvolatile option byte (FOPT)"
127 devices. For program flash only devices, this byte is reserved.
[all …]
/Zephyr-latest/samples/basic/custom_dts_binding/
DREADME.rst1 .. zephyr:code-sample:: gpio-custom-dts-binding
3 :relevant-api: gpio_interface devicetree-generic-id devicetree-generic-exist
10 In Zephyr, all hardware-specific configuration is described in the devicetree.
12 Consequently, also GPIO pins are configured in the devicetree and assigned to a specific purpose
18 For typical use cases like LEDs or buttons, the existing :dtcompatible:`gpio-leds` or
19 :dtcompatible:`gpio-keys` compatibles can be used.
25 :zephyr_file:`samples/basic/custom_dts_binding/dts/bindings/power-switch.yaml`. The gate driver for
37 .. zephyr-app-commands::
38 :zephyr-app: samples/basic/custom_dts_binding
40 :goals: build flash
[all …]
/Zephyr-latest/doc/services/file_system/
Dindex.rst11 specific API or internal functions by introducing file system registration
17 :c:enumerator:`FS_TYPE_EXTERNAL_BASE` to avoid clashes with in-tree identifiers.
19 .. code-block:: c
31 .. code-block:: c
41 - ``FS_FATFS`` is the file system type like FATFS or LittleFS.
42 - ``FATFS_MNTP`` is the mount point where the file system will be mounted.
43 - ``fat_fs`` is the file system data which will be used by fs_mount() API.
54 - ``samples/subsys/fs/fat_fs`` is an example of FAT file system usage with SDHC media;
55 - ``samples/subsys/shell/fs`` is an example of Shell fs subsystem, using internal flash partition
57 - ``samples/subsys/usb/mass/`` example of USB Mass Storage device that uses FAT FS driver with RAM
[all …]

1234567891011