Searched refs:looks (Results 26 – 50 of 58) sorted by relevance
123
| /Zephyr-latest/doc/develop/toolchains/ |
| D | zephyr_sdk.rst | 36 If no toolchain is selected, the build system looks for Zephyr SDK and uses the toolchain
|
| /Zephyr-latest/doc/develop/west/ |
| D | basics.rst | 22 :file:`zephyrproject` as well as all its subfolders, looks like this:
|
| D | manifest.rst | 22 history, looks like the following figure (though some parts of this example are
1330 In other words, the west workspace you want looks like this:
2021 sections. The general case looks like this:
|
| D | release-notes.rst | 213 - A bug in the way west looks for the zephyr repository was fixed. The bug
|
| /Zephyr-latest/doc/kernel/drivers/ |
| D | index.rst | 133 A subsystem API definition typically looks like this:
196 A device-specific API definition typically looks like this:
|
| /Zephyr-latest/cmake/modules/ |
| D | boards.cmake | 134 # Check that the board root looks reasonable.
|
| /Zephyr-latest/drivers/console/ |
| D | Kconfig | 55 server looks at characters received and decides to handle them itself if
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | sockets.rst | 102 array) looks like this:
|
| /Zephyr-latest/doc/develop/test/ |
| D | pytest.rst | 43 through a CLI command. When pytest is done, twister looks for a pytest report (results.xml) and
|
| /Zephyr-latest/boards/nxp/lpcxpresso55s69/doc/ |
| D | index.rst | 188 MCUboot partitioning which looks like the table below
|
| /Zephyr-latest/boards/udoo/udoo_neo_full/doc/ |
| D | index.rst | 225 If the output looks like below, the mqx_upload_on_m4SoloX could not read
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | controller.rst | 26 The bit-timing as defined in ISO 11898-1:2003 looks as following:
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-tools.rst | 188 The output looks like this::
|
| /Zephyr-latest/doc/develop/debug/ |
| D | index.rst | 297 The sample output of the dump looks like this::
|
| /Zephyr-latest/samples/modules/canopennode/ |
| D | README.rst | 139 configuration file. On GNU/Linux, the configuration looks similar to
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 65 The build system looks for :file:`app.overlay` by default, but you can add
76 The build system looks for :file:`prj.conf` by default, but you can add more
862 When using the Ninja generator a build directory looks like this:
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 525 relationship between the symbols harder to understand, even if code never looks
597 should be avoided, because it looks identical to a symbol with all children
|
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | Kconfig.tfm | 283 How many images the bootloader sees when it looks at TFM and the app.
|
| /Zephyr-latest/doc/build/dts/ |
| D | macros.bnf | 246 ; looks like this:
|
| D | howtos.rst | 543 your driver supports. The resulting devicetree usually looks something like
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_0.rst | 880 | | with no restrictions how the query looks like |
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 148 By default ZMS looks for the last data with the same ID by browsing through all stored ATEs from
|
| /Zephyr-latest/doc/connectivity/usb/device/ |
| D | usb_device.rst | 102 and looks like this:
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-4.1.rst | 980 three sections and looks like: ``<test_scenario_name>.<ztest_suite_name>.<ztest_name>``.
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 373 configuration files. By default, sysbuild looks for a configuration file named
|
123
