Home
last modified time | relevance | path

Searched refs:load (Results 251 – 275 of 379) sorted by relevance

1...<<111213141516

/Zephyr-latest/scripts/generate_usb_vif/
Dgenerate_vif.py264 edt = pickle.load(f)
/Zephyr-latest/drivers/serial/
DKconfig.nrfx_uart_instance62 that with higher speeds and/or high cpu load some data can be lost.
/Zephyr-latest/scripts/build/
Dcheck_init_priorities.py237 edt = pickle.load(f)
Dgen_syscalls.py472 syscalls = json.load(fd)
/Zephyr-latest/doc/hardware/peripherals/
Dbc12.rst32 Unit load current IUNIT 100 mA
/Zephyr-latest/samples/drivers/ethernet/eth_ivshmem/
DREADME.rst87 jailhouse cell load qemu-arm64-zephyr-demo zephyr.bin --address 0x70000000
/Zephyr-latest/scripts/
Dzephyr_module.py186 schema = yaml.load(METADATA_SCHEMA, Loader=SafeLoader)
210 meta = yaml.load(f.read(), Loader=SafeLoader)
/Zephyr-latest/boards/toradex/verdin_imx8mm/doc/
Dindex.rst136 to be started by the A53 core. The A53 core is responsible to load the M4 binary
218 To load and start a firmware use these commands:
/Zephyr-latest/boards/96boards/meerkat96/doc/
Dindex.rst153 to be started by the A7 core. The A7 core is responsible to load the M4 binary
204 Below you will find the instructions to load and run Zephyr on M4 from
/Zephyr-latest/boards/toradex/colibri_imx7d/doc/
Dindex.rst129 the A7 core. The A7 core is responsible to load the M4 binary application into the
185 Below you will find the instructions to load and run Zephyr on M4 from A7 using u-boot.
382 #Request RPROC to load the M4 image
/Zephyr-latest/scripts/tests/twister_blackbox/
Dtest_coverage.py246 json_content = json.load(json_file)
/Zephyr-latest/subsys/net/ip/
DKconfig.mgmt80 on the load of the system, planned for the usage.
/Zephyr-latest/soc/nxp/imxrt/
DKconfig125 to load
/Zephyr-latest/samples/net/sockets/big_http_download/
DREADME.rst15 transferred. Thus, it can serve as a "load testing" application for
/Zephyr-latest/boards/ti/msp_exp432p401r_launchxl/doc/
Dindex.rst104 This will load the image into flash.
/Zephyr-latest/drivers/ethernet/
DKconfig.stm32_hal57 especially under high load.
/Zephyr-latest/boards/pine64/pinetime_devkit0/doc/
Dindex.rst168 Simply load the .elf file containing the final firmware and
/Zephyr-latest/soc/espressif/esp32s3/
Ddefault_appcpu.ld82 /* Image load table */
85 /* 0. Magic byte for load header */
/Zephyr-latest/boards/ti/cc3220sf_launchxl/doc/
Dindex.rst82 Note that zephyr.bin produced by the Zephyr SDK may not load via
176 This will load the image into flash.
/Zephyr-latest/include/zephyr/arch/x86/ia32/
Dlinker.ld20 * load address for the DATA section which means it doesn't have to be copied
23 * For builds using XIP, there is a different load memory address (LMA) and
/Zephyr-latest/boards/nxp/s32z2xxdc2/doc/
Dindex.rst179 Currently is only possible to load and execute a Zephyr application binary on
260 load the application to SRAM. The difference is that ``flash`` hides the
/Zephyr-latest/boards/element14/warp7/doc/
Dindex.rst140 the A7 core. The A7 core is responsible to load the M4 binary application into
197 Below you will find the instructions to load and run Zephyr on M4 from A7 using
/Zephyr-latest/doc/develop/getting_started/
Dindex.rst261 automatically load boilerplate code required for building Zephyr
313 automatically load boilerplate code required for building Zephyr
368 automatically load boilerplate code required for building Zephyr
/Zephyr-latest/boards/snps/hsdk/doc/
Dindex.rst470 (gdb) load
485 This command still uses openocd and gdb to load the application elf file to
486 HS Development Kit, but it will load the application and immediately run. If
/Zephyr-latest/boards/snps/hsdk4xd/doc/
Dindex.rst466 (gdb) load
481 This command still uses openocd and gdb to load the application elf file to
482 HS4x/HS4xD Development Kit, but it will load the application and immediately run. If

1...<<111213141516