Searched refs:need (Results 101 – 125 of 733) sorted by relevance
12345678910>>...30
| /Zephyr-latest/boards/shields/npm1300_ek/doc/ |
| D | index.rst | 17 Arduino shield connectors. For example, the I2C lines need to be connected to
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | efi.ld | 20 * need to be page-aligned and can be immediately after text/rodata */
|
| /Zephyr-latest/soc/nxp/mcx/mcxw/ |
| D | Kconfig.defconfig | 43 # need to be queued and processed by a dedicated thread
|
| /Zephyr-latest/doc/build/dts/ |
| D | troubleshooting.rst | 48 To fix it, you need to make sure that:
67 To find the devicetree node you need to check, use the number ``<N>`` from the
95 If the node has ``status = "disabled";`` in :file:`zephyr.dts`, then you need
121 your devicetree node and allocating devices for it. To do this, you need to
157 If you find a driver, you next need to make sure the Kconfig option that
159 compatible property is correct, then you need to write a driver. Writing
177 Once you know the driver you want to enable, you need to make sure its Kconfig
190 If your driver's Kconfig is not set to ``y``, you need to figure out what you
191 need to do to make that happen. Often, this will happen automatically as soon
354 If your binding file is not under :file:`zephyr/dts`, you may need to set
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.xtensa | 24 need synchronization, like the timer subsystem!). In
|
| /Zephyr-latest/boards/nordic/nrf9160dk/ |
| D | nrf9160dk_nrf52840_0_14_0.overlay | 44 /* No need to drive P0.12 together with P1.12 in this board revision. */
|
| /Zephyr-latest/samples/subsys/fs/fs_sample/boards/ |
| D | nrf52840dk_nrf52840.overlay | 8 * storage_partition is 32kiB for that board, we need to reorgatnize
|
| /Zephyr-latest/boards/silabs/radio_boards/slwrb4321a/ |
| D | slwrb4321a.dts | 50 /* gpio flags need validation */
56 /* gpio flags need validation */
|
| /Zephyr-latest/soc/silabs/silabs_s2/ |
| D | Kconfig.defconfig | 25 # need to activate Zero Latency IRQ in Zephyr by default. The level (2) depends on the
|
| /Zephyr-latest/tests/boards/mec15xxevb_assy6853/i2c_api/ |
| D | README.txt | 15 We need to change to use I2C01 port by making some jumpers setting as below:
|
| /Zephyr-latest/samples/drivers/ipm/ipm_esp32/ |
| D | sysbuild.cmake | 22 # This is required because some primary cores need information from the
|
| /Zephyr-latest/samples/boards/nordic/clock_control/ |
| D | Kconfig | 31 The distributed clock domains may need time to initialize
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_setup.rst | 44 For the steps below, you will need at least 4 terminal windows:
73 For applications requiring DNS, you may need to restart the host's DNS server
143 (you need to stop both ``loop-slip-tap.sh`` and ``loop-socat.sh``).
177 Additionally, IPv4 forwarding should be enabled on the host, and you may need to
207 samples), you will need two terminal windows, set up for Zephyr development.
240 sample application, which do not need to talk to each other, use the
|
| /Zephyr-latest/boards/shields/npm6001_ek/doc/ |
| D | index.rst | 23 Arduino shield connectors. For example, the I2C lines need to be connected to
|
| /Zephyr-latest/tests/drivers/gpio/gpio_basic_api/ |
| D | README.txt | 10 For some boards `src/main.c` may also need to be extended to configure
|
| /Zephyr-latest/samples/sensor/proximity_polling/ |
| D | README.rst | 16 automatically detected from the devicetree, you only need to set aliases from
|
| /Zephyr-latest/soc/espressif/esp32/ |
| D | Kconfig | 41 proceed to load code from flash. Some flash chips need sufficient
44 some flash chip types need more than that.
|
| /Zephyr-latest/boards/sifive/hifive1/doc/ |
| D | index.rst | 57 In order to upload the application to the device, you'll need OpenOCD with
76 debug the board, you'll need to install the
|
| /Zephyr-latest/boards/silabs/starter_kits/slstk3701a/ |
| D | slstk3701a.dts | 48 /* gpio flags need validation */
54 /* gpio flags need validation */
|
| /Zephyr-latest/cmake/modules/ |
| D | FindGnuLd.cmake | 41 # Since GNULD_LINKER already exists, there is no need to find it again (below).
85 # own version scheme so we need to account for that.
|
| /Zephyr-latest/lib/libc/newlib/ |
| D | Kconfig | 42 and user mode threads need to access this heap, then this is necessary
71 may need to use the remaining RAM for also other purposes than heap.
|
| /Zephyr-latest/boards/openisa/rv32m1_vega/doc/ |
| D | index.rst | 292 To use this board, you will need:
314 Before programming and debugging, you first need to get a GNU
373 - If you put the toolchain somewhere else, you will need to change
375 - If you put OpenOCD somewhere else, you will need to change the
412 Next, you'll need to make sure your board boots the RI5CY or ZERO-RISCY core.
413 **You only need to do this once.**
423 Linux users: to run these commands as a normal user, you will need
517 You need to make sure this happens every time you use this board.
525 Due to a toolchain `linker issue`_, you need to add an option setting
567 Linux users: to run these commands as a normal user, you will need
[all …]
|
| /Zephyr-latest/drivers/pm_cpu_ops/ |
| D | Kconfig | 37 Say Y here if you need to enable PSCI interface shell commands
|
| /Zephyr-latest/scripts/west_commands/ |
| D | README.txt | 7 on the multi-repo need to be in upstream west, not here. Try to limit
|
| /Zephyr-latest/soc/altr/zephyr_nios2f/cpu/ |
| D | README | 7 You will need the Quartus SDK in order to modify this CPU or flash it onto
|
12345678910>>...30
