Searched full:build (Results 2176 – 2200 of 2206) sorted by relevance
1...<<818283848586878889
| /Zephyr-latest/boards/nxp/mimxrt1060_evk/doc/ |
| D | index.rst | 363 Once the host tool and board are configured, build and flash applications
|
| /Zephyr-latest/drivers/espi/ |
| D | espi_mchp_xec_v2.c | 1506 /* Configure the channels and its capabilities based on build config */ in espi_xec_init()
|
| /Zephyr-latest/drivers/flash/ |
| D | spi_nor.c | 72 /* Build-time data associated with the device. */
|
| /Zephyr-latest/doc/build/cmake/ |
| D | build-config-phase.svg | 11 sodipodi:docname="build-config-phase.svg"
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_1.rst | 316 | | whereby it will compare build numbers too. Should only be present when "off" |
|
| /Zephyr-latest/lib/os/ |
| D | cbprintf_complete.c | 102 * build errors, otherwise we can use the base type. We can tell that
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | test_testplan.py | 1736 instance_build_dir = os.path.join('some', 'far', 'off', 'build', 'dir')
|
| /Zephyr-latest/drivers/usb_c/tcpc/ |
| D | ucpd_numaker.c | 2439 * 3. Build assert will check the above rules.
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 534 When FPU support is enabled in the build
|
| /Zephyr-latest/drivers/ethernet/ |
| D | eth_sam_gmac.c | 1087 /* Build assert at top of file should catch this case */ in gmac_init()
|
| /Zephyr-latest/tests/net/conn_mgr_conn/src/ |
| D | main.c | 163 * a few milliseconds of delay are miniscule compared to the time it takes to build the suite,
|
| /Zephyr-latest/scripts/kconfig/ |
| D | guiconfig.py | 212 # Build the initial tree
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | i3c.h | 2314 * @retval -ENOMEM No memory to build the payload.
|
| /Zephyr-latest/boards/adi/max78000evkit/doc/ |
| D | index.rst | 5 …valuation kit (EV kit) provides a platform for leveraging the capabilities of the MAX78000 to build
|
| /Zephyr-latest/doc/develop/test/figures/ |
| D | twister_test_project.svg | 4 …build &amp;amp; run" style="rounded=1;whiteSpace=wrap;html=1;arcSize=40;fontColor=#0…
|
| /Zephyr-latest/tests/net/socket/tcp/src/ |
| D | main.c | 23 "from across the industry to build a best-in-breed small, scalable, " \
|
| /Zephyr-latest/boards/nxp/vmu_rt1170/doc/ |
| D | index.rst | 472 Build and flash applications as usual (see :ref:`build_an_application` and
|
| /Zephyr-latest/subsys/bluetooth/controller/hci/ |
| D | hci.c | 5042 /* Write BD_ADDR, Read Build Info */
5216 /* The alias for convenience of Controller HCI implementation. Controller is build for
5219 * all CPU data types for supported architectures should be available during build, hence
|
| /Zephyr-latest/tests/net/socket/udp/src/ |
| D | main.c | 38 "from across the industry to build a best-in-breed small, scalable, " \
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | shell.rst | 1547 * ``BuildNum``: Build number.
|
| /Zephyr-latest/subsys/bluetooth/controller/ticker/ |
| D | ticker.c | 819 * 5) If using ticks slot window under yield (build time configuration),
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | hci_core.c | 3936 LOG_INF("Firmware: %s (0x%02x) Version %u.%u Build %u", vs_fw_variant(rp.info->fw_variant), in hci_vs_init()
|
| /Zephyr-latest/boards/adi/max78002evkit/doc/ |
| D | index.rst | 5 …aluation kit (EV kit) provides a platform and tools for leveraging device capabilities to build new
|
| /Zephyr-latest/tests/lib/devicetree/api/src/ |
| D | main.c | 274 * understand build errors if this guarantee is not met due to in ZTEST()
|
| /Zephyr-latest/doc/ |
| D | zephyr.doxyfile.in | 521 # Build related configuration options
|
1...<<818283848586878889
