Searched refs:boot (Results 1 – 25 of 553) sorted by relevance
12345678910>>...23
| /Zephyr-latest/soc/nxp/rw/ |
| D | Kconfig | 27 bool "Create boot header"
30 Create data structures required by the boot ROM to boot the
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
49 The Image Vector Table (IVT) provides the boot ROM with pointers to
50 the application entry point and device configuration data. The boot
51 ROM requires a fixed IVT offset for each type of boot device.
|
| /Zephyr-latest/boards/intel/ehl/doc/ |
| D | index.rst | 68 To enable PXE boot for Elkhart Lake CRB board do the following:
70 #. Enable boot from PXE. Go to EFI shell and make sure that the first boot
75 Shell> bcfg boot dump
82 #. If UEFI PXEv4 is not the first boot option use ``bcfg boot mv`` command to
83 change boot order
87 Shell> bcfg boot mv 7 0
|
| /Zephyr-latest/tests/drivers/regulator/api/ |
| D | app.overlay | 17 regulator-boot-on;
31 regulator-boot-off;
35 regulator-boot-off;
|
| /Zephyr-latest/soc/nxp/mcx/mcxc/ |
| D | Kconfig | 41 bool "Keep watchdog timer enabled at boot"
43 Leave SOC watchdog timer enabled at boot. The specific timeout
44 and clock configuration of the watchdog at boot is SOC dependent.
45 Note: if the watchdog timer is enabled at boot, the user will
49 # Enable watchdog configuration function if watchdog is left enabled at boot
|
| /Zephyr-latest/soc/nxp/imxrt/ |
| D | Kconfig.sysbuild | 5 bool "Load minimal application to primary core to boot secondary one"
9 Load a minimal application to the primary core to boot the secondary
12 boot the secondary core during startup.
|
| D | Kconfig | 23 # requires the boot header is SOC specific.
29 Enable data structures required by the boot ROM to boot the
72 sequence (optional), etc. The boot ROM expects FlexSPI configuration
85 sequence (optional), etc. The boot ROM expects XSPI configuration
95 The Image Vector Table (IVT) provides the boot ROM with pointers to
96 the application entry point and device configuration data. The boot
97 ROM requires a fixed IVT offset for each type of boot device.
103 the boot ROM to initialize components such as an SDRAM. This is
105 initialized at boot time.
113 at the boot time. This sequence allows to configure
[all …]
|
| /Zephyr-latest/boards/digilent/zybo/doc/ |
| D | index.rst | 68 git clone -b v2022.04 https://source.denx.de/u-boot/u-boot.git
69 cd u-boot
82 Ensure the board is configured for JTAG boot, open a serial terminal, turn on/reset the board (press
101 ``u-boot/spl/boot.bin``, ``u-boot/u-boot.img``, and ``zephyr/zephyr.bin`` to a FAT32 formatted
103 configured for ``SD`` boot, and turn on the board.
105 Once U-boot is done initializing, load an run the Zephyr application:
121 Ensure the board is configured for JTAG boot, open a serial terminal, turn on/reset the board (press
|
| /Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/support/ |
| D | preloader_dl_cmd.txt | 6 restore boards/intel/socfpga_std/cyclonev_socdk/support/u-boot-spl
7 symbol-file -readnow boards/intel/socfpga_std/cyclonev_socdk/support/u-boot-spl
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | dfu.rst | 13 * :zephyr_file:`subsys/dfu/boot/`: Interface code to bootloaders
40 The MCUboot API is provided to get version information and boot status of
41 application images. It allows to select application image and boot type
42 for the next boot.
58 `MCUboot boot loader`_. It interfaces with MCUboot and is aware of the image
60 is the boot loader used with Zephyr. The source code itself is hosted in the
88 .. _MCUboot boot loader: https://mcuboot.com/
|
| /Zephyr-latest/boards/intel/common/ |
| D | net_boot.rst | 29 dhcp-boot=zephyr.efi
55 Prepare the board for network boot
60 #. Make network boot as the first boot option.
91 #. When the boot process completes, you have finished booting the
|
| D | efi_boot.rst | 8 Prepare a USB flash drive to boot the Zephyr application image on
38 #. Insert the prepared boot device (USB flash drive) into the board.
58 #. From the EFI shell select Zephyr EFI image to boot.
64 #. When the boot process completes, you have finished booting the
|
| /Zephyr-latest/arch/arm/ |
| D | Kconfig | 41 Relocates the rom_start region containing the boot-vector data and
46 such that it is able to load the correct boot-vector (contained in rom_start)
50 Most SOCs include an alias for the boot-vector at address 0x00000000
55 is not placed into the boot-vector memory area.
58 effect of enlarging the bin file. If the zephyr.bin file is used to boot the
63 for code location. But the boot-vector must be placed into OCRAM_S for the
64 CORTEX-M to boot (alias 0, real 0x00180000/32K available).
76 to the right memory region of the boot-vector.
79 -IMX7D the boot-vector is OCRAM_S (0x00180000, aliased at 0x0).
80 -IMX6SX the boot-vector is TCML (0x007F8000, aliased at 0x0).
[all …]
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.stellaris | 21 This tells the driver to configure the UART port at boot, depending on
29 This tells the driver to configure the UART port at boot, depending on
37 This tells the driver to configure the UART port at boot, depending on
|
| /Zephyr-latest/boards/arduino/portenta_h7/ |
| D | arduino_portenta_h7_stm32h747xx_m7.dts | 29 regulator-boot-on;
37 regulator-boot-on;
100 regulator-boot-on;
104 regulator-boot-on;
109 regulator-boot-on;
113 regulator-boot-on;
117 regulator-boot-on;
121 regulator-boot-on;
|
| /Zephyr-latest/snippets/nordic-ppr-xip/ |
| D | README.rst | 3 Nordic boot PPR snippet with execution in place (nordic-ppr-xip)
9 This snippet allows users to build Zephyr with the capability to boot Nordic PPR
|
| /Zephyr-latest/boards/raspberrypi/rpi_4b/doc/ |
| D | index.rst | 26 …* `bcm2711-rpi-4-b.dtb <https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/bcm2711…
27 …* `bootcode.bin <https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/bootcode.bin>`_
28 * `start4.elf <https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/start4.elf>`_
|
| /Zephyr-latest/drivers/watchdog/ |
| D | Kconfig.renesas_ra | 24 bool "Start WDT in boot time"
28 Start watchdog in boot time
|
| /Zephyr-latest/boards/acrn/acrn/doc/ |
| D | index.rst | 75 the boot filesystem. Under currently tested configurations, Zephyr
153 and Zephyr application will not boot successfully without this change.
201 ACRN will boot on the hardware via the GNU GRUB bootloader, which is
220 Now attach your boot media (e.g. a USB stick on /dev/sdb, your
221 hardware may differ!) to a Linux system and create an EFI boot
222 partition (type code 0xEF) large enough to store your boot artifacts.
247 "/efi/boot" directory of the boot media. Note that GRUB must be named
252 # mkdir -p /mnt/acrn/efi/boot
253 # cp $PATH_TO_GRUB_BINARY /mnt/acrn/efi/boot/bootx64.efi
254 # cp $ZEPHYR_BASE/build/zephyr/zephyr.bin /mnt/acrn/efi/boot/
[all …]
|
| /Zephyr-latest/soc/intel/intel_adsp/common/ |
| D | CMakeLists.txt | 16 boot.c
57 DEPENDS ${CMAKE_BINARY_DIR}/zephyr/boot.mod ${CMAKE_BINARY_DIR}/zephyr/main.mod
61 OUTPUT ${CMAKE_BINARY_DIR}/zephyr/boot.mod ${CMAKE_BINARY_DIR}/zephyr/main.mod
80 --only-section .module.boot
81 --set-section-flags .module.boot=noload,readonly
82 --rename-section .module.boot=.module
83 ${KERNEL_REMAPPED} ${CMAKE_BINARY_DIR}/zephyr/boot.mod 2>${NULL_FILE}
99 --remove-section .module.boot
159 ${CMAKE_BINARY_DIR}/zephyr/boot.mod ${CMAKE_BINARY_DIR}/zephyr/main.mod
|
| /Zephyr-latest/soc/nxp/kinetis/ke1xf/ |
| D | Kconfig | 47 bool "Keep watchdog timer enabled at boot"
49 Keep the watchdog timer enabled at boot with the internal
52 watchdog timer after boot and install a different timeout,
|
| /Zephyr-latest/boards/ti/sk_am62/doc/ |
| D | index.rst | 61 onto an SD-card. This will boot Linux on the A53 application cores of the EVM.
94 The SD card can now be used for booting. The binary will now be loaded onto the M4F core on boot.
96 To allow the board to boot using the SD card, set the boot pins to the SD Card boot mode. Refer to …
98 After changing the boot mode, the board should go through the boot sequence on powering up.
135 https://docs.u-boot.org/en/latest/board/ti/k3.html#building-openocd-from-source
|
| /Zephyr-latest/samples/drivers/eeprom/ |
| D | README.rst | 5 Store a boot count value in EEPROM.
10 This sample demonstrates the :ref:`EEPROM driver API <eeprom_api>` in a simple boot counter
55 Reset the MCU to see the increasing boot counter.
|
| /Zephyr-latest/boards/phytec/phyboard_lyra/doc/ |
| D | phyboard_lyra_am62xx_m4.rst | 87 an etching software onto an SD-card. This will boot Linux on the A53 application
121 The SD card can now be used for booting. The binary will now be loaded onto the M4F core on boot.
123 To allow the board to boot using the SD card, set the boot pins to the SD Card boot mode. Refer to …
125 After changing the boot mode, stop in U-Boot to enable the M4F co-processor.
132 boot
134 The board should boot into Linux and the binary will run and print Hello world to the MCU_UART0
168 https://docs.u-boot.org/en/latest/board/ti/k3.html#building-openocd-from-source
|
| /Zephyr-latest/soc/native/inf_clock/ |
| D | Kconfig | 36 the first one to boot, or even that it will boot automatically.
51 Automatically start the MCU this Zephyr image is built for during HW boot,
54 If that MCU was, by HW design, going to start at HW boot anyhow, this option does nothing.
|
| /Zephyr-latest/subsys/dfu/ |
| D | CMakeLists.txt | 3 add_subdirectory(boot)
|
12345678910>>...23
