Home
last modified time | relevance | path

Searched refs:flash (Results 351 – 375 of 2906) sorted by relevance

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

/Zephyr-4.1.0/dts/arm/st/l1/
Dstm32l151Xb.dtsi16 flash-controller@40023c00 {
17 flash0: flash@8000000 {
/Zephyr-4.1.0/dts/arm/st/u5/
Dstm32u5a9Xj.dtsi22 flash-controller@40022000 {
23 flash0: flash@8000000 {
/Zephyr-4.1.0/dts/arm/nxp/
Dnxp_kv5xf1m0vlx24.dtsi20 flash0: flash@10000000 {
21 compatible = "soc-nv-flash";
/Zephyr-4.1.0/dts/arm/st/f4/
Dstm32f405Xg.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
Dstm32f407Xe.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
Dstm32f407Xg.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
Dstm32f417Xe.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
Dstm32f427Xi.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
Dstm32f427vi.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
Dstm32f429Xi.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
Dstm32f429vi.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
Dstm32f469Xi.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
Dstm32f415Rg.dtsi22 flash-controller@40023c00 {
23 flash0: flash@8000000 {
/Zephyr-4.1.0/boards/sifive/hifive1/support/
Dopenocd.cfg16 flash bank onboard_spi_flash fespi 0x20000000 0 0 0 $_TARGETNAME
19 flash protect 0 64 last off
20 flash write_image erase $file
/Zephyr-4.1.0/boards/nxp/mimxrt1180_evk/
DCMakeLists.txt15 "update your flash configuration or device configuration data blocks")
20 # Include flash configuration block for RT1180 EVK from NXP's HAL.
21 # This configuration block may need modification if another flash chip is
/Zephyr-4.1.0/boards/nxp/mimxrt595_evk/
DCMakeLists.txt17 "update your flash configuration block data")
19 # Include flash configuration block for R595 EVK from NXP's HAL.
20 # This configuration block may need modification if another flash chip is
/Zephyr-4.1.0/doc/services/device_mgmt/
Ddfu.rst26 The flash image API as part of the Device Firmware Upgrade (DFU) subsystem
28 image chunks to flash.
65 1. You will need to define the flash partitions required by MCUboot; see
67 2. You will have to specify your flash partition as the chosen code partition
80 4. You need to build and flash MCUboot itself on your device
81 5. You might need to take precautions to avoid mass erasing the flash and also
82 to flash the Zephyr application image at the correct offset (right after the
/Zephyr-4.1.0/dts/arm/st/h7/
Dstm32h745.dtsi14 flash-controller@52002000 {
15 flash0: flash@8000000 {
16 compatible = "st,stm32-nv-flash", "soc-nv-flash";
22 flash1: flash@8100000 {
23 compatible = "st,stm32-nv-flash", "soc-nv-flash";
Dstm32h757Xi_m7.dtsi24 flash-controller@52002000 {
25 flash0: flash@8000000 {
/Zephyr-4.1.0/soc/ti/simplelink/cc32xx/
DREADME8 * Text must start at 0x800 offset in flash. The first 0x800 bytes are
9 reserved for the flash header.
/Zephyr-4.1.0/dts/arm/st/f1/
Dstm32f103Xe.dtsi15 flash-controller@40022000 {
16 flash0: flash@8000000 {
Dstm32f103Xd.dtsi19 flash-controller@40022000 {
20 flash0: flash@8000000 {
/Zephyr-4.1.0/samples/bluetooth/ibeacon/
DREADME.rst35 For other boards, build and flash the application as follows:
40 :goals: flash
44 flash instructions if your board doesn't support the ``flash`` target.
/Zephyr-4.1.0/tests/subsys/storage/flash_map/
Dapp.overlay7 * Test compilation with disabled flash nodes.
12 compatible = "vnd,flash";
/Zephyr-4.1.0/boards/seeed/xiao_ble/doc/
Dindex.rst8 flash, battery charger, and range of I/O broken out into 14 pins.
62 can use an :ref:`External Debug Probe <debug-probes>`. To flash and debug Zephyr
74 BlackMagic Probe). Then build and flash applications as
89 Then build and flash the application in the usual way. Just add
100 :goals: build flash
108 :goals: build flash
132 :goals: build flash
139 :goals: build flash
141 You can build and flash the examples to make sure Zephyr is running correctly on
158 :goals: build flash
[all …]

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