Searched refs:can (Results 101 – 125 of 2493) sorted by relevance
12345678910>>...100
| /Zephyr-latest/drivers/wifi/infineon/ |
| D | Kconfig.airoc | 66 More information about CYW4343W device you can find on
73 More information about CYW4373 device you can find on
80 More information about CYW43012 device you can find on
87 More information about CYW43438 device you can find on
94 More information about CYW43439 device you can find on
110 Detailed information about Murata Type 1LV module you can find on
126 Detailed information about Type 1DX module you can find on
140 Detailed information about Type Sterling LWB5+ module you can find on
156 Detailed information about Murata Type 1YN module you can find on
|
| /Zephyr-latest/boards/ezurio/bl653_dvk/doc/ |
| D | bl653_dvk.rst | 27 More information about the board can be found at the
64 Applications for the ``bl653_dvk`` board configuration can be built, flashed,
72 and configure all the necessary software. Further information can be
88 can be found. For example, under Linux, :code:`/dev/ttyUSB0`.
122 You can build and flash the examples to make sure Zephyr is running correctly on
123 your board. The button and LED definitions can be found in
129 The following approach can be used when an application needs to use
171 Pins can be configured in the board pinctrl file. To see the available mappings,
174 'General purpose I/O'. Note that pins marked as 'low frequency I/O only' can only be used
|
| /Zephyr-latest/doc/develop/sca/ |
| D | eclair.rst | 37 The configure of the ECLAIR SCA environment can either be done via a cmake options file or with
40 To invoke a cmake options file into the ECLAIR call, you can define the ``ECLAIR_OPTIONS_FILE``
51 file, that can be achived by giving the argument ``-DOption=ON|OFF``.
67 * STU: Selection of the projects coding guidelines, which can be verified by analysing the single
89 rulesets. You can do so by setting :code:`ECLAIR_RULESET_USER=ON`.
93 If the ruleset file is not in the application source directory, you can define the path to the
106 ECLAIR can generate additional report formats (e.g. DOC, ODT, XLSX) and
108 default ecd file. Following additional reports and report formats can be generated:
143 The detail level of the txt and doc full reports can also be adapted by a configuration.
|
| /Zephyr-latest/samples/subsys/logging/ble_backend/ |
| D | README.rst | 26 This sample can be found under :zephyr_file:`samples/subsys/logging/ble_backend` in the
29 The Bluetooth logger can be tested with the NRF Toolbox app or any similar app that can connect over
|
| /Zephyr-latest/soc/atmel/sam0/common/ |
| D | Kconfig.saml2x | 11 These can be mitigated by inserting a small delay during the early boot
22 This can then be selected as the main clock reference for the SOC.
28 This can then be selected as the main clock reference for the SOC.
42 This can then be selected as the main clock reference for the SOC.
58 Note, this mode can only be used with an LDO regulator.
82 further reduce power consumption, radio can be kept in reset state by
|
| /Zephyr-latest/boards/shields/ls0xx_generic/doc/ |
| D | index.rst | 14 contents or show all white pixels, this can be connected
17 high during driver initialization. Display blanking apis can be used
22 and `datasheet`_. The DC bias can damage the LCD and reduce the life.
48 | EXTCOMIN | VCOM Inversion Polarity Input (VCOM can be controlled |
62 for LS013B7DH03. Other shields can be added by using the LS013B7DH03 as
84 This shield can only be used with a board that provides a configuration
|
| /Zephyr-latest/doc/build/dts/ |
| D | zephyr-user-node.rst | 8 you can put essentially arbitrary properties inside it and retrieve their
20 You can store numeric or array values in ``/zephyr,user`` if you want them to
38 You can get the above property values in C/C++ code like this:
54 You can store :ref:`phandles <dt-phandles>` in ``/zephyr,user`` if you want to
69 You can convert the phandles in the ``handle`` and ``handles`` properties to
112 You can convert the pin defined in ``signal-gpios`` to a ``struct
|
| /Zephyr-latest/tests/bluetooth/classic/sdp_c/ |
| D | README.rst | 21 The HCI transport for ``bumble`` can be configured as follows:
23 * A specific configuration context can be provided along with the ``usb_hci`` fixture separated by
26 * The configuration context can be overridden using the `hci transport`_ can be provided using the
45 If the HCI transport is ``usb:0`` and debug console port is ``COM4``, the test suite can be
57 The test suite can be launched using Twister. Below is an example for running on the
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server/ |
| D | README.rst | 17 application which can be accessed via a conventional web browser, or to
21 The source code for this sample application can be found at:
46 Alternatively, a tool like ``curl`` can be used:
52 Finally, you can run an HTTP profiling/load tool like Apache Bench
63 The same application source code can be built for a POSIX system, e.g.
82 As can be seen, the behavior of the application is the same as the Zephyr
|
| /Zephyr-latest/samples/net/sockets/echo_async/ |
| D | README.rst | 17 The source code for this sample application can be found at:
47 supports multiple concurrent client connections. You can open
49 The sample supports up to three connected clients, but this can be adjusted
55 The IPv4 Wi-Fi support can be enabled in the sample with
61 The same application source code can be built for a POSIX system, e.g.
85 As can be seen, the behavior of the application is the same as the Zephyr
|
| /Zephyr-latest/boards/enjoydigital/litex_vexriscv/doc/ |
| D | index.rst | 5 and additional peripherals. This setup can be generated using
9 and can be used on various FPGA chips.
10 The bitstream (FPGA configuration file) can be obtained using both
26 More information about the LiteX project can be found on
34 that can be used to customize the design (JTAG, MMU, MUL/DIV extensions).
36 More information about the project can be found on
40 bitstream for the FPGA on a Digilent Arty A7-35 Board or SDI-MIPI Video Converter. This can be achi…
43 reference platform. You can also use the official LiteX SoC Builder.
68 …or the Digilent Arty A7-35 Board requires F4PGA toolchain installation. It can be done by followin…
118 You can also generate the bitstream using the `official LiteX repository <https://github.com/enjoy-…
[all …]
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | ring_buffers.rst | 16 * **Byte mode**: raw bytes can be enqueued and dequeued.
19 can be enqueued and dequeued from the ring buffer in
38 Any number of ring buffers can be defined (limited only by available RAM). Each
49 buffer can hold.
51 A ring buffer must be initialized before it can be used. This sets its
81 can be used to receive those bytes, along with a size of the
83 user can then copy data into that region at a later time without
85 :c:func:`ring_buf_put_finish` can be used to signal the buffer that the
87 transferred. At this point a new transfer can be initiated.
89 buffer data from which the user can read without making a verbatim
[all …]
|
| /Zephyr-latest/boards/shields/lcd_par_s035/doc/ |
| D | index.rst | 10 and 5-point capacitive touch functionality. The LCD module can be controlled
12 More information about the shield can be found
18 This shield can only be used with FRDM-X evaluation kits with a parallel LCD
|
| /Zephyr-latest/subsys/emul/ |
| D | Kconfig | 16 can be used just like a real hardware device.
21 yet been completed. This allows for testing that high-level code can
22 handle these situations correctly. Test coverage can therefore
|
| /Zephyr-latest/tests/kernel/pending/ |
| D | README.txt | 5 This test verifies that preemptible threads can pend on the following
12 This project outputs to the console. It can be built and executed
21 Problems caused by out-dated project information can be addressed by
|
| /Zephyr-latest/samples/sensor/ina219/ |
| D | README.rst | 12 The calibration/configuration parameters can be set in the devicetree file.
22 The supply voltage of the INA219 can be in the 3V to 5.5V range.
23 The common mode voltage of the measured bus can be in the 0V to 26V range.
|
| /Zephyr-latest/samples/bluetooth/hci_vs_scan_req/ |
| D | README.rst | 14 to the central role, where the RAM saving can be bigger.
16 connection can also be added, depending on configuration choices.
28 This sample can be found under :zephyr_file:`samples/bluetooth/hci_vs_scan_req`
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | charger.rst | 10 The charger device can exist as a module, an integrated circuit, or as a functional block in a power
16 manufacturer. On charger devices with a control port, the charge profile can be configured by the
17 host controller by setting the relevant properties, and can be adjusted at runtime to respond to
31 Fundamentally, a property is a configurable setting, state, or quantity that a charger device can
|
| /Zephyr-latest/doc/kernel/iterable_sections/ |
| D | index.rst | 7 which can be used for defining iterable areas of equally-sized data structures,
8 that can be iterated on using :c:macro:`STRUCT_SECTION_FOREACH`.
14 associated initializer in a common header file, so that they can be
53 The data can then be accessed using :c:macro:`STRUCT_SECTION_FOREACH`.
|
| /Zephyr-latest/drivers/can/ |
| D | Kconfig.stm32 | 23 that can be added by the application.
39 that can be added by the application.
66 that can be added by the application.
74 that can be added by the application.
|
| /Zephyr-latest/samples/shields/npm1300_ek/doc/ |
| D | index.rst | 26 The sample is designed so that it can run on any platform. For example, when
27 building for the nRF52 DK, the following command can be used:
37 provided to test the PMIC. Below you can find details for each subcommand.
43 the regulators embedded in the PMIC. Below you can find some command examples.
|
| /Zephyr-latest/soc/microchip/mec/mec15xx/ |
| D | Kconfig | 56 pin is ignored. All other JTAG pins can be used as GPIOs
62 JTAG port in SWD mode. UART2 and ADC00-03 can be used.
68 to see if ADC00-03 can be used or not.
83 UART2 can be used, but ADC00-03 cannot.
89 UART2 cannot be used. ADC00-03 can be used.
|
| /Zephyr-latest/boards/wch/ch32v003evt/doc/ |
| D | index.rst | 38 Applications for the ``ch32v003evt`` board target can be built and flashed
53 You can use ``minichlink`` to flash the board. Once ``minichlink`` has been set
67 This board can be debugged via OpenOCD or ``minichlink``.
79 You can build and flash the examples to make sure Zephyr is running
80 correctly on your board. The button and LED definitions can be found
|
| /Zephyr-latest/boards/others/stm32f030_demo/doc/ |
| D | index.rst | 11 More information about the board can be found at the `stm32-base.org website`_.
13 More information about STM32F030F4P6 can be found here:
48 Applications for the ``stm32f030_demo`` board configuration can be built and
55 The board can be flashed by using ST-LINKV2 in-circuit debugger and programmer.
73 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/samples/net/sockets/echo/ |
| D | README.rst | 16 The source code for this sample application can be found at:
45 sockets, and thus can serve only one client connection at time. After the
46 current client disconnects, the next connection can proceed.
51 The same application source code can be built for a POSIX system, e.g.
73 As can be seen, the behavior of the application is the same as the Zephyr
|
12345678910>>...100
