Searched full:look (Results 1 – 25 of 305) sorted by relevance
12345678910>>...13
| /Zephyr-latest/modules/trusted-firmware-m/ |
| D | Kconfig.tfm.partitions | 16 to be passed to the TF-M build system. Look at 'config_default.cmake'
27 to be passed to the TF-M build system. Look at 'config_default.cmake'
38 to be passed to the TF-M build system. Look at 'config_default.cmake'
50 to be passed to the TF-M build system. Look at 'config_default.cmake'
61 to be passed to the TF-M build system. Look at 'config_default.cmake'
73 to be passed to the TF-M build system. Look at 'config_default.cmake'
|
| /Zephyr-latest/include/zephyr/sys/ |
| D | sys_io.h | 94 * @param port the port address from where to look for the bit
104 * @param port the port address from where to look for the bit
115 * @param port the port address from where to look for the bit
128 * @param port the port address from where to look for the bit
141 * @param port the port address from where to look for the bit
244 * @param addr the memory address from where to look for the bit
254 * @param addr the memory address from where to look for the bits
264 * @param addr the memory address from where to look for the bits
274 * @param addr the memory address from where to look for the bit
285 * @param addr the memory address from where to look for the bit
[all …]
|
| /Zephyr-latest/doc/services/debugging/ |
| D | symtab.rst | 10 Currently, this is being used to look up the function names during a stack trace in supported archi…
18 function to look-up the symbol name and offset of an address. More advanced functionalities and be
|
| /Zephyr-latest/doc/build/dts/ |
| D | troubleshooting.rst | 68 linker error. Look for this number in the list of nodes at the top of
91 Now look for this node in :file:`<build>/zephyr/zephyr.dts`, which is the final
138 - Look in :zephyr_file:`drivers` for the appropriate subdirectory that
140 - Look inside that directory for relevant files until you figure out what the
146 example, if your node's compatible is ``vnd,foo-device``, look for a file with this
171 Then you would look inside of :zephyr_file:`drivers/i2c` for the driver file
259 Look at the preprocessor output
351 source file, ``compatible`` should look like ``"vnd,some-device"`` --
|
| /Zephyr-latest/subsys/net/lib/wifi_credentials/ |
| D | wifi_credentials_shell.c | 187 /* look for bssid */ in cmd_add_network()
198 /* look for band */ in cmd_add_network()
212 /* look for channel */ in cmd_add_network()
222 /* look for favorite flag */ in cmd_add_network()
230 /* look for mfp_disabled flag */ in cmd_add_network()
241 /* look for timeout */ in cmd_add_network()
|
| /Zephyr-latest/scripts/kconfig/ |
| D | kconfigfunctions.py | 61 to an EDT node. If it finds an EDT node, it will look to see if that node
213 This function takes a 'node' and will look to see if that 'node' has a
241 This function takes a 'node' and will look to see if that 'node' has a
267 a cell ('cell') and it will look to see if that node has a property
295 to an EDT node. If it finds an EDT node, it will look to see if that
319 to an EDT node. If it finds an EDT node, it will look to see if that node
358 to an EDT node. If it finds an EDT node, it will look to see if that
400 finds an EDT node, it will look to see if that node has a register at the
426 finds an EDT node, it will look to see if that node has a register at the
514 finds an EDT node, it will look to see if that node has a boolean property
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | zperf.rst | 37 For TCP testing, the command line would look like this:
51 For TCP the zperf command would look like this:
|
| /Zephyr-latest/.github/workflows/ |
| D | greet_first_time_contributor.yml | 34 …Please take a look at [our commit message guidelines](https://docs.zephyrproject.org/latest/contri…
57 Thank you for your valuable input, and we look forward to seeing more of your
|
| /Zephyr-latest/drivers/watchdog/ |
| D | wdt_iwdg_stm32.h | 17 * an appropriate reference manual and look for chapter called:
|
| D | wdt_wwdg_stm32.h | 18 * an appropriate reference manual and look for chapter called:
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_handlers.rst | 44 file would look similar to:
64 file would look similar to:
83 look similar to:
104 to the functionality of the handler being implemented. An example file would look similar to:
114 source files if the Kconfig options are enabled. An example file would look similar to:
|
| /Zephyr-latest/dts/bindings/i3c/ |
| D | i3c-controller.yaml | 30 and there are I2C devices attached to the bus, look at the Legacy
|
| /Zephyr-latest/dts/bindings/watchdog/ |
| D | adi,max32-watchdog.yaml | 29 The target device might not support all option please take a look on
|
| /Zephyr-latest/drivers/memc/ |
| D | memc_nxp_s32_qspi.h | 13 * @brief Build a QSPI Look-up Table (LUT) sequence entry.
|
| /Zephyr-latest/dts/bindings/arm/ |
| D | atmel,sam-ssc.yaml | 29 For example dmas for TX, RX would look like
|
| /Zephyr-latest/dts/bindings/pinctrl/ |
| D | snps,emsdp-pinctrl.yaml | 11 For example, setting PmodA to SPI would look like this:
|
| /Zephyr-latest/dts/bindings/bluetooth/ |
| D | zephyr,bt-hci-spi-slave.yaml | 8 A node defined via devicetree overlay should look like this:
|
| /Zephyr-latest/include/zephyr/net/ |
| D | wifi_credentials.h | 93 * @param[in] ssid SSID to look for
119 * @param[in] ssid SSID to look for
143 * @param[in] ssid SSID to look for
170 * @param[in] ssid SSID to look for
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 59 Your SoC directory should look like this:
158 In general, :file:`<soc>.dtsi` should look like this:
199 :file:`<soc>_<cluster>.dtsi`. A :file:`<soc>_<cluster>.dtsi` file will look
230 A :file:`Kconfig.soc` may look like this:
292 will look like:
|
| /Zephyr-latest/share/sysbuild/ |
| D | Kconfig.v2 | 12 if not found we look for the linker file in
|
| /Zephyr-latest/dts/bindings/spi/ |
| D | atmel,sam-spi.yaml | 35 For example dmas for TX and RX may look like
|
| /Zephyr-latest/doc/develop/languages/rust/ |
| D | index.rst | 40 to copy from a sample, but this will look something like:
98 application itself. Look for the 'zephyr' crate on the left side bar, and this will take you to the
|
| /Zephyr-latest/scripts/west_commands/zspdx/ |
| D | cmakecache.py | 18 # walk through and look for non-comment, non-empty lines
|
| /Zephyr-latest/snippets/cdc-acm-console/ |
| D | README.rst | 28 device node with driver support. This should look roughly like this in
|
| /Zephyr-latest/dts/bindings/timer/ |
| D | adi,max32-timer.yaml | 31 The target device might not support every option please take a look on
|
12345678910>>...13
