Searched refs:as (Results 1 – 25 of 1927) sorted by relevance
12345678910>>...78
/Zephyr-Core-3.6.0/subsys/bindesc/ |
D | Kconfig.version | 14 The kernel version string, such as "3.4.0" 19 The major version number, such as 3 in 3.4.0 24 The minor version number, such as 4 in 3.4.0 29 The patchlevel version number, such as 0 in 3.4.0 34 The kernel version as binary coded decimal, computed as 36 3.4.0 would be represented as 0x30400 41 The app version string, such as "1.0.0" 46 The app major version number, such as 1 in 1.0.0 51 The app minor version number, such as 0 in 1.0.0 56 The app patchlevel version number, such as 0 in 1.0.0 [all …]
|
D | Kconfig.build_time | 28 The year the image was compiled, such as 2023 33 The month the image was compiled, such as 5 (May) 38 The day of the month the image was compiled, such as 9 43 The hour of the day the image was compiled, such as 13 in 13:34:52 48 The minute the image was compiled, such as 34 in 13:34:52 53 The second the image was compiled, such as 52 in 13:34:52 56 bool "Build time as UNIX time" 62 bool "Build date and time as string" 64 The date and time of compilation as a string, such as "2023-09-29T17:43:14+0000" 67 bool "Build date as string" [all …]
|
D | Kconfig.host_info | 19 The C compiler name, such as "GNU" 24 The C compiler version, such as "12.3.0" 29 The C++ compiler name, such as "GNU" 34 The C++ compiler version, such as "12.3.0"
|
/Zephyr-Core-3.6.0/doc/connectivity/networking/conn_mgr/figures/ |
D | integration_diagram_detailed.drawio | 8 <mxGeometry x="516" y="-192" width="465" height="407" as="geometry" /> 11 <mxGeometry x="544" y="260" width="310" height="177" as="geometry" /> 14 <mxGeometry x="646" y="-68" width="164" height="30" as="geometry" /> 17 <mxGeometry x="285" y="-122" width="116" height="559" as="geometry" /> 20 <mxGeometry x="634" y="273" width="208" height="75" as="geometry" /> 23 <mxGeometry x="641" y="289" width="60" height="30" as="geometry" /> 26 <mxGeometry x="775" y="289" width="60" height="30" as="geometry" /> 29 <mxGeometry x="708" y="289" width="60" height="30" as="geometry" /> 32 <mxGeometry x="634" y="361" width="208" height="70" as="geometry" /> 35 <mxGeometry x="641" y="389" width="60" height="30" as="geometry" /> [all …]
|
D | integration_diagram_simplified.drawio | 8 <mxGeometry x="527" y="-207" width="195" height="261" as="geometry" /> 11 <mxGeometry x="574" y="-81" width="164" height="30" as="geometry" /> 14 <mxGeometry x="271" y="-122" width="116" height="348" as="geometry" /> 17 <mxGeometry x="714" y="173" width="108" height="51" as="geometry" /> 20 <mxGeometry x="584" y="22" width="164" height="30" as="geometry" /> 23 <mxGeometry x="596" y="128" width="164" height="30" as="geometry" /> 26 <mxGeometry x="397" y="208" width="164" height="30" as="geometry" /> 29 <mxGeometry relative="1" as="geometry" /> 32 <mxGeometry x="552" y="-35" width="147" height="50" as="geometry" /> 35 <mxGeometry relative="1" as="geometry" /> [all …]
|
/Zephyr-Core-3.6.0/drivers/clock_control/ |
D | Kconfig.stm32 | 64 Use EXT_HSE as source of MCO1 74 Use LSE as source of MCO1 85 Use HSE as source of MCO1 91 Use LSI as source of MCO1 97 Use MSI as source of MCO1 107 Use HSI as source of MCO1 113 Use HSI16 as source of MCO1 121 Use HSI48 as source of MCO1 127 Use PLLCLK as source of MCO1 134 Use PLLQ as source of MCO1 [all …]
|
/Zephyr-Core-3.6.0/dts/arm/silabs/ |
D | efr32bg2x-pinctrl.dtsi | 11 /* configuration for usart0 device, operating as SPI */ 20 /* configuration for usart1 device, default state - operating as UART */ 23 /* configure PA.6 as UART_RX and PA.5 as UART_TX */
|
/Zephyr-Core-3.6.0/samples/net/lwm2m_client/ |
D | Kconfig | 12 This is used as client endpoint name as well as PSK ID. 20 PSK key as a hex string. 36 LwM2M server address. Write as a full URI including optional port number. 38 When DNS resolver is enabled, DNS domain names could be used as well.
|
/Zephyr-Core-3.6.0/samples/drivers/dac/ |
D | README.rst | 24 :ref:`nucleo_l073rz_board` as follows: 35 :ref:`nucleo_l152re_board` as follows: 46 :ref:`nucleo_f767zi_board` as follows: 57 :ref:`stm32f3_disco_board` as follows: 68 :ref:`nucleo_f429zi_board` as follows: 79 :ref:`stm32l562e_dk_board` as follows: 90 :ref:`nucleo_l552ze_q_board` as follows: 100 The sample can be built and executed for the :ref:`twr_ke18f` as 114 The sample can be built and executed for the :ref:`frdm_k64f` as 127 The BL652 DVK PCB contains a footprint for a MCP4725 to use as an external [all …]
|
/Zephyr-Core-3.6.0/doc/hardware/peripherals/audio/ |
D | i2s.rst | 10 as well as common non-standard extensions such as PCM Short/Long Frame Sync
|
/Zephyr-Core-3.6.0/tests/kernel/context/ |
D | README.txt | 5 This test verifies that the kernel CPU and context APIs operate as expected. 53 be tested in the same way as irq_lock() and irq_unlock(). 60 on QEMU as follows: 101 got thread (q order: 2, t/o: 500) as expected 103 got thread (q order: 3, t/o: 750) as expected 105 got thread (q order: 0, t/o: 1000) as expected 107 got thread (q order: 6, t/o: 1250) as expected 109 got thread (q order: 1, t/o: 1500) as expected 111 got thread (q order: 4, t/o: 1750) as expected 113 got thread (q order: 5, t/o: 2000) as expected [all …]
|
/Zephyr-Core-3.6.0/cmake/ |
D | verify-toolchain.cmake | 5 # other tools, such as twister / python scripts. 7 # When invoked as a script with -P: 11 # FORMAT=json: Print the output as a json formatted string, useful for Python 17 "as:\n 'cmake ... -P verify-toolchain.cmake'\n" 23 # all other messages as only the specified output should be printed.
|
/Zephyr-Core-3.6.0/doc/hardware/arch/ |
D | risc-v.rst | 8 Currently, there's support for some boards, as well as Qemu support 9 and support for some FPGA implementations such as neorv32 and 13 ISA extensions as well as :ref:`semihosting<semihost_guide>`.
|
/Zephyr-Core-3.6.0/samples/subsys/portability/cmsis_rtos_v1/philosophers/ |
D | README.rst | 12 threads of differing priorities, as well as mutex/semaphore and thread sleeping 18 are shown as well, such as STARVING when the philosopher is hungry but the 29 on QEMU as follows: 56 priorities, as well as semaphores and thread sleeping.
|
/Zephyr-Core-3.6.0/samples/subsys/portability/cmsis_rtos_v2/philosophers/ |
D | README.rst | 12 threads of differing priorities, as well as mutex/semaphore and thread sleeping 18 are shown as well, such as STARVING when the philosopher is hungry but the 29 on QEMU as follows: 56 priorities, as well as semaphores and thread sleeping.
|
/Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/ |
D | connection_mgmt.rst | 9 (such as the remote address) can be acquired using the 21 define callbacks for connection & disconnection events, as well as other 22 events related to a connection such as a change in the security level or 23 the connection parameters. When acting as a central the application will
|
/Zephyr-Core-3.6.0/tests/posix/eventfd/ |
D | Kconfig | 31 In order to get a true benchmark, there should be as few branches 32 as possible on the hot path. Say 'y' here to add extra assertions 33 on the hot path as well to verify functionality. 38 In order to get a true benchmark, there should be as few branches 39 as possible on the hot path. Say 'y' here to skip reporting.
|
/Zephyr-Core-3.6.0/boards/arm/google_kukui/doc/ |
D | index.rst | 10 Kodama. These are known as the Lenovo Chromebook Duet and 10e Chromebook 48 Other features (such as I2C) are not available in Zephyr. 56 Each of the GPIO pins can be configured by software as output 57 (push-pull or open-drain), as input (with or without pull-up or 58 pull-down), or as peripheral alternate function. 73 Build application as usual for the ``google_kukui`` board, and flash
|
/Zephyr-Core-3.6.0/cmake/linker/ |
D | linker_flags_template.cmake | 7 # Set this flag if the linker supports reporting of memusage as part of link, 8 # such as ls --print-memory-usage flag. 17 # such as, "-no-pie" for LD, and "--no-pie" for LLD. 21 # such as, "-r" or "--relocatable" for LD and LLD.
|
/Zephyr-Core-3.6.0/arch/arm64/core/xen/ |
D | Kconfig | 17 bool "Zephyr as Xen Domain 0" 20 Built binary will be used as Xen privileged domain (Domain 0). 26 Configures Zephyr as DomU, that can be started on Dom0less
|
/Zephyr-Core-3.6.0/tests/kernel/smp/ |
D | Kconfig | 9 int "Run factor for stressing tests, such as 'switch torture', \ 10 as a percentage"
|
/Zephyr-Core-3.6.0/boards/arm/thingy53_nrf5340/doc/ |
D | index.rst | 16 Armv8-M Security Extension, running at up to 128 MHz, referred to as 19 a fixed 64 MHz, referred to as the **network core**. 40 Thingy:53 does not have an on-board J-Link debug IC as some other nRF5 43 debugger. A development board with a Debug out connector such as the 44 :ref:`nrf5340dk_nrf5340` can be used as a debugger with Thingy:53.
|
/Zephyr-Core-3.6.0/samples/application_development/sysbuild/with_mcuboot/ |
D | README.rst | 9 automatically include MCUboot as the bootloader. 16 This sample automatically includes MCUboot as bootloader when built using 25 The :file:`sysbuild/mcuboot.conf` file will be used as an extra fragment that 28 :file:`sysbuild/mcuboot.conf` adjusts the log level in MCUboot, as well as
|
/Zephyr-Core-3.6.0/.github/ISSUE_TEMPLATE/ |
D | 007_ext-source.md | 22 or as a module, and why. If the mode of integration is a module, suggest a 29 choose to identify a single maintainer only or add collaborators as well 34 in the main tree or as a module (pointing to your own fork for now). Make sure 35 the PR is correctly labeled as "DNM" 57 will it be included via an abstraction layer with this component as a 66 Please use an SPDX identifier (https://spdx.org/licenses/), such as
|
/Zephyr-Core-3.6.0/samples/boards/stm32/power_mgmt/serial_wakeup/boards/ |
D | stm32l562e_dk.overlay | 3 /* Comment out these lines to use usart1 as console/shell */ 14 /* Comment out this line to use HSI as clk source */ 37 /* Uncomment out this line to use usart1 as wakeup source */
|
12345678910>>...78