Home
last modified time | relevance | path

Searched refs:main (Results 2001 – 2025 of 2048) sorted by relevance

1...<<8182

/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-le-host.rst8 applications. The following diagram depicts the main protocol & profile
/Zephyr-latest/doc/build/dts/
Dphandles.rst42 Here are the main ways you will use phandles.
/Zephyr-latest/modules/
DKconfig.mcuboot252 MCUboot will only boot slot0_partition for the main application but has
/Zephyr-latest/samples/bluetooth/iso_connected_benchmark/src/
Dmain.c1380 int main(void) in main() function
/Zephyr-latest/doc/services/tfm/
Doverview.rst8 that aim to address some of the main security concerns in IoT products.
/Zephyr-latest/doc/security/
Dsecure-coding.rst29 .. todo: Reference main document here
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_pkt.rst13 Network packets are the main data the networking stack manipulates.
/Zephyr-latest/boards/st/steval_stwinbx1/doc/
Dindex.rst211 as well as the main PLL clock. By default the System clock is driven by the PLL clock at 160MHz,
/Zephyr-latest/doc/contribute/
Dbin_blobs.rst109 and is generally copied into RAM or flash memory by the main CPU. An example
/Zephyr-latest/boards/nxp/imx93_evk/doc/
Dindex.rst340 * **Root cell**: refers to the cell in which Linux is running. This is the main cell which
/Zephyr-latest/doc/contribute/coding_guidelines/
Dindex.rst1121 - - ``{primary,main} / {secondary,replica}``
1144 .. _Code of Conduct: https://github.com/zephyrproject-rtos/zephyr/blob/main/CODE_OF_CONDUCT.md
1242 considered the central or main project, it should implement the non-namespaced versions of the
1377 to the `main Zephyr repository`_, except the Zephyr kernel as defined by the
/Zephyr-latest/doc/build/kconfig/
Dsetting.rst166 after the main project configuration has been applied and before any board overlay
/Zephyr-latest/doc/develop/
Dbeyond-GSG.rst213 The main build products will be in :file:`build/zephyr`;
/Zephyr-latest/boards/snps/hsdk/doc/
Dindex.rst471 (gdb) b main
/Zephyr-latest/boards/snps/hsdk4xd/doc/
Dindex.rst467 (gdb) b main
/Zephyr-latest/doc/connectivity/bluetooth/shell/host/
Dgap.rst4 The GAP shell is the "main" shell of Bluetooth and handles connection management, scanning,
/Zephyr-latest/doc/connectivity/networking/conn_mgr/
Dmain.rst385 int main()
/Zephyr-latest/tests/bsim/bluetooth/ll/advx/src/
Dmain.c1866 int main(void) in main() function
/Zephyr-latest/modules/trusted-firmware-m/
DKconfig.tfm221 The main one is the TF-M secure firmware. Optionally the TF-M
/Zephyr-latest/doc/releases/
Drelease-notes-3.3.rst324 * Added support for defining application main() in C++ code
2068 * Introduced :kconfig:option:`CONFIG_CPP_MAIN` to support defining ``main()``
2070 invoke ``int main(void)``, which is required by the ISO C++ standards, as
2071 opposed to the Zephyr default ``void main(void)``.
2859 * :github:`54730` - intel_adsp_ace15_mtpm: cpp.main.minimal test failing
2876 * :github:`54575` - Automatic termination with return code from a native_posix main function
2902 * :github:`54472` - How to enable a node in main.
3231 * :github:`52376` - Cannot build apps with main in a .cpp file
3389 * :github:`51368` - tests: tests/subsys/cpp/cxx/cpp.main.picolibc: build failure
3401 * :github:`51294` - ztest: Broken tests in main branch due to API-breaking change ``ZTEST_FAIL_ON_A…
/Zephyr-latest/doc/services/logging/
Dindex.rst327 int main(void)
380 Logging consists of 3 main parts:
/Zephyr-latest/boards/intel/adsp/doc/
Dchromebooks_adsp.rst199 and seems to have been backporting upstream drivers such that its main
/Zephyr-latest/doc/project/
Dproject_roles.rst51 (https://github.com/zephyrproject-rtos/zephyr/blob/main/CODE_OF_CONDUCT.md)
/Zephyr-latest/arch/xtensa/core/
DREADME_MMU.txt249 the refill will be served from the data cache and not main memory.
/Zephyr-latest/boards/espressif/esp_wrover_kit/doc/
Dindex.rst31 The block diagram below shows the main components of ESP-WROVER-KIT and their interconnections.

1...<<8182