Searched refs:created (Results 126 – 150 of 278) sorted by relevance
12345678910>>...12
/Zephyr-latest/cmake/modules/ |
D | FindDeprecated.cmake | 7 # corresponding COMPONENTS should be created with name identifying the deprecated code.
|
/Zephyr-latest/subsys/logging/ |
D | Kconfig.processing | 58 When enabled thread is created by the logger subsystem. Thread is
|
/Zephyr-latest/doc/connectivity/bluetooth/autopts/ |
D | autopts-linux.rst | 77 Open virtual machine network settings. On adapter 1 you will have created by default NAT. 139 Open virtual machine network settings. On adapter 1 you will have created by default NAT.
|
/Zephyr-latest/doc/develop/west/ |
D | zephyr-cmds.rst | 95 #. Build your application using this pre-created build directory, like so: 120 SPDX Relationships are created to indicate dependencies between
|
D | west-apis.rst | 65 The argument parser created by calling ``WestCommand.add_parser()``. 512 The *abspath* attribute is created using ``os.path.abspath()``
|
/Zephyr-latest/boards/native/native_sim/doc/ |
D | index.rst | 239 is created by the clock and timer model. 314 With this driver, Zephyr UART devices can be created. These 315 can be connected to the Linux process stdin/stdout or a newly created 371 network interface can be created by the ``net-setup.sh`` script found in 374 network interfaces can be created if needed. The IP address configuration 532 When a UART is connected to a new PTY, the name of the newly created UART pseudo-terminal will be
|
/Zephyr-latest/doc/project/ |
D | release_process.rst | 128 created. 320 Each release is created with the above products to document the quality and the 351 auditable code bases shall be kept in sync after the audit branch is created, 420 created.
|
/Zephyr-latest/doc/services/shell/ |
D | index.rst | 252 Commands can be created in any file in the system that includes 253 :zephyr_file:`include/zephyr/shell/shell.h`. All created commands are available for all 289 Let's use an example. Suppose you created a command to set an ADC gain. 353 /* Function returning command dynamically created 494 The help for commands and subcommands can be created with respective macros:
|
/Zephyr-latest/doc/contribute/ |
D | guidelines.rst | 143 (a) The contribution was created in whole or in part by me and I 150 submit that work with modifications, whether created in whole 189 - If you are altering an existing commit created by someone else, you must add 530 PR is created, and again every time the PR is modified with a commit. 619 issues are automatically created for any issues detected by static analysis 670 created when you :ref:`obtained the code <get_the_code>`:: 680 Let Git know about the fork you just created, naming it ``origin``::
|
/Zephyr-latest/boards/ite/it8xxx2_evb/doc/ |
D | index.rst | 107 #. The file :file:`zephyr.bin` will be created by west.
|
/Zephyr-latest/boards/arm/fvp_baser_aemv8r/doc/ |
D | debug-with-arm-ds.rst | 94 A new configuration named ``New_configuration`` will be created.
|
/Zephyr-latest/boards/ite/it82xx2_evb/doc/ |
D | index.rst | 104 #. The file :file:`zephyr.bin` will be created by west.
|
/Zephyr-latest/boards/seeed/xiao_esp32c3/doc/ |
D | index.rst | 101 Build directory structure created by Sysbuild is different from traditional
|
/Zephyr-latest/doc/build/signing/ |
D | index.rst | 20 from the :file:`zephyrproject` workspace you created in the :ref:`getting_started`.
|
/Zephyr-latest/boards/m5stack/stamp_c3/doc/ |
D | index.rst | 82 Build directory structure created by sysbuild is different from traditional
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | rtc.rst | 36 RTCs have been supported before this API was created, using the
|
/Zephyr-latest/doc/connectivity/networking/ |
D | native_sim_setup.rst | 49 should be created.
|
D | networking_with_multiple_instances.rst | 48 Zephyr instance should be created in the host system. The default setup for
|
D | eth_bridge_native_sim_setup.rst | 18 First create the host interfaces. In this example two interfaces are created.
|
/Zephyr-latest/samples/net/cloud/aws_iot_mqtt/ |
D | README.rst | 49 - :kconfig:option:`CONFIG_AWS_THING_NAME`: The name of the thing created in AWS IoT Core. Associated
|
/Zephyr-latest/subsys/net/lib/lwm2m/ |
D | lwm2m_rw_oma_tlv.c | 840 uint8_t created = 0U; in do_write_op_tlv_item() local 843 ret = lwm2m_get_or_create_engine_obj(msg, &obj_inst, &created); in do_write_op_tlv_item()
|
/Zephyr-latest/arch/ |
D | Kconfig | 305 When enabled, threads may be created or dropped down to user mode, 393 be created in the system. 452 bool "ISR tables created locally and placed by linker" 500 needs an interrupt vector table created. Only disable this if the 541 needs a software ISR table table created. This is an array of struct 563 created by gen_isr_tables.py. When creating these tables, this value
|
/Zephyr-latest/scripts/ci/es_upload/ |
D | README.md | 13 An alternative way is to have index files created at the ElasticSearch server
|
/Zephyr-latest/boards/hardkernel/odroid_go/doc/ |
D | index.rst | 125 Build directory structure created by sysbuild is different from traditional
|
/Zephyr-latest/boards/xen/xenvm/doc/ |
D | index.rst | 76 at build time. So there are chances, that Zephyr image created with default
|
12345678910>>...12