Searched refs:can (Results 226 – 250 of 2493) sorted by relevance
12345678910>>...100
| /Zephyr-latest/subsys/net/l2/dummy/any/ |
| D | Kconfig | 10 itself. It can be used for example to hook virtual interfaces
11 on top of it that can act as a network packet capture handlers.
|
| /Zephyr-latest/samples/modules/compression/lz4/ |
| D | README.rst | 9 A simple sample that can be used with any :ref:`supported board <boards>` and
22 The sample can be built and executed on nrf52840dk/nrf52840 as follows:
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | can.h | 540 STATS_SECT_START(can)
551 STATS_NAME_START(can)
552 STATS_NAME(can, bit_error)
553 STATS_NAME(can, bit0_error)
554 STATS_NAME(can, bit1_error)
555 STATS_NAME(can, stuff_error)
556 STATS_NAME(can, crc_error)
557 STATS_NAME(can, form_error)
558 STATS_NAME(can, ack_error)
559 STATS_NAME(can, rx_overrun)
[all …]
|
| /Zephyr-latest/doc/develop/api/ |
| D | terminology.rst | 13 if executing the function can cause the invoking thread to sleep
15 if a parameter to the function can prevent the invoking thread from
18 if the function can be safely called and will have its specified
21 if the function can be safely called before the kernel has been fully
40 The reschedule attribute is used on a function that can reach a
69 The sleep attribute is used on a function that can cause the invoking
83 suspend, wait, or invoke :c:func:`k_yield` before it can complete
99 indicate that a parameter to the function can force an execution path
106 timeout, to which :c:macro:`K_NO_WAIT` can be passed. The semantics of
108 long as it can be completed immediately, and to return an error code
[all …]
|
| /Zephyr-latest/boards/panasonic/panb511evb/doc/ |
| D | index.rst | 10 More information about the PAN B511 Module Variants and Evaluation Board can be found
16 You can find the `panb511evb user guide`_ for the PAN B511 Evaluation Board in the
35 Applications for the ``panb511evb/nrf54l15/cpuapp`` board target can
|
| /Zephyr-latest/doc/services/ |
| D | formatted_output.rst | 22 use of ``s*printf()`` C libraries in Zephyr can be converted to
35 :kconfig:option:`CONFIG_CBPRINTF_LIBC_SUBSTS` can be used to provide functions
39 In addition :kconfig:option:`CONFIG_CBPRINTF_NANO` can be used to revert back to
60 Package can have following variants:
62 * **Self-contained** - non read-only strings appended to the package. String can be
65 within the package. That information can be used to convert packet to fully
67 * **Fully self-contained** - all strings are appended to the package. String can be
71 it may contain read-only string location information. String can be formatted
73 strings are accessible. Alternatively, package can be converted to **self-contained**
77 Package can be created using two methods:
[all …]
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | menuconfig.rst | 13 The configuration can also be changed by editing :file:`zephyr/.config` in
28 inspecting it can be handy when making settings permanent. The minimal
105 :guilabel:`( )` brackets. Symbol values that can't be changed are shown as
110 You can also press :kbd:`Y` or :kbd:`N` to set a boolean configuration
148 Finding a symbol in the menu tree and navigating to it can be tedious. To jump
150 ``guiconfig``). This brings up the following dialog, where you can search for
151 symbols by name and jump to them. In ``guiconfig``, you can also change symbol
168 Show-all mode can't be turned off if there are no visible items in the
174 symbol depends on another symbol that isn't enabled, you can jump to that
175 symbol in turn to see if it can be enabled.
[all …]
|
| /Zephyr-latest/boards/nordic/nrf21540dk/doc/ |
| D | index.rst | 34 More information about the board can be found at the `nRF21540 website`_.
125 Applications for the ``nrf21540dk/nrf52840`` board configuration can be built,
133 and configure all the necessary software. Further information can be
147 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
174 You can build and flash the examples to make sure Zephyr is running correctly on
175 your board. The button and LED definitions can be found in
181 The following approach can be used when an application needs to use another set
221 Pins can be configured in the board pinctrl file. To see the available mappings,
224 'General purpose I/O'. Note that pins marked as 'low frequency I/O only' can only be used
|
| /Zephyr-latest/boards/seeed/lora_e5_mini/doc/ |
| D | index.rst | 46 More information about the board can be found at the `LoRa-E5 mini Wiki`_.
48 More information about LoRa-E5 STM32WLE5JC Module can be found here:
94 Applications for the ``lora_e5_mini`` board configuration can be built the
99 So before you can program a Zephyr application to the module for the first time
101 In case you use an st-link debugger you can use the STM32CubeProgrammer GUI to
114 But the module can be debugged by connecting an external debug probe to the
117 ``pyocd``, ``blackmagic``, or ``jlink`` runner can be used to flash the board.
121 can be installed by adding "pack" support with the following pyocd command:
153 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/renesas/ek_ra6e2/doc/ |
| D | index.rst | 9 and e2 studio IDE. The users can use rich on-board features along with
63 Detailed hardware features for the RA6E2 MCU group can be found at `RA6E2 Group User's Manual Hardw…
72 Detailed hardware features for the EK-RA6E2 MCU can be found at `EK-RA6E2 - User's Manual`_
82 Applications for the ``ek_ra6e2`` board target configuration can be
90 Program can be flashed to EK-RA6E2 via the on-board SEGGER J-Link debugger.
108 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
119 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
| /Zephyr-latest/boards/renesas/ek_ra6m5/doc/ |
| D | index.rst | 64 Detailed hardware features for the RA6M5 MCU group can be found at `RA6M5 Group User's Manual Hardw…
73 Detailed hardware features for the EK-RA6M5 MCU can be found at `EK-RA6M5 - User's Manual`_
83 Applications for the ``ek_ra6m5`` board target configuration can be
91 Program can be flashed to EK-RA6M5 via the on-board SEGGER J-Link debugger.
109 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
120 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
132 …sors/ra-cortex-m-mcus/ra6m5-200mhz-arm-cortex-m33-trustzone-highest-integration-ethernet-and-can-fd
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | stacks.rst | 17 Any number of stacks can be defined (limited only by available RAM). Each stack
28 * A **maximum quantity** of data values that can be queued in the array.
30 A stack must be initialized before it can be used. This sets its queue to empty.
32 A data value can be **added** to a stack by a thread or an ISR.
76 Alternatively, a stack can be defined and initialized at compile time
92 can create a pool of data structures by saving their memory addresses
115 can dynamically allocate an unused data structure.
|
| /Zephyr-latest/samples/subsys/zbus/remote_mock/ |
| D | README.rst | 10 This application demonstrates how a host script can publish to the zbus in an embedded device using…
13 …can implement tests using any language on a computer to talk directly via channels with threads ru…
18 This project outputs to the console. It can be built and executed
59 The :file:`remote_mock.py` script can be executed using the following command:
69 It can be different in your case. If you are using a board, read the documentation to get the
|
| /Zephyr-latest/boards/shields/x_nucleo_idb05a1/doc/ |
| D | index.rst | 14 connector layout (the user can mount the ST Morpho connectors, if required). The
16 the user can change the default SPI clock, the SPI chip select and SPI IRQ by
27 More information about the board can be found at the
36 otherwise shield configuration can be changed (see below).
69 More information about X-NUCLEO-IDB05A1 can be found here:
75 You can use the X-NUCLEO-IDB05A1 as a Bluetooth Low-Energy controller
|
| /Zephyr-latest/boards/st/nucleo_f031k6/doc/ |
| D | index.rst | 16 More information about the board can be found at the `Nucleo F031K6 website`_.
36 More information about STM32F031K6 can be found here:
49 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
75 Applications for the ``nucleo_f031k6`` board configuration can be built and
85 Alternatively, OpenOCD or JLink can also be used to flash the board using
108 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/st/nucleo_f042k6/doc/ |
| D | index.rst | 16 More information about the board can be found at the `Nucleo F042K6 website`_.
36 More information about STM32F042K6 can be found here:
49 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
75 Applications for the ``nucleo_f042k6`` board configuration can be built and
85 Alternatively, OpenOCD or JLink can also be used to flash the board using
108 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | coap_client.rst | 14 The library can be enabled with :kconfig:option:`CONFIG_COAP_CLIENT` Kconfig option.
45 Before any requests can be sent, the CoAP client needs to be initialized.
46 After initialization, the application can send a CoAP request and wait for the response.
47 Currently only one request can be sent for a single CoAP client at a time. There can be multiple
62 As the response can be a blockwise transfer and the client calls the callback once per each
|
| /Zephyr-latest/drivers/sensor/ti/tmp112/ |
| D | Kconfig | 24 When set extended mode can be selected using tmp112_attr_set
31 When set conversion rate can be set at runtime using sensor_attr_set
|
| /Zephyr-latest/tests/kernel/mutex/sys_mutex/ |
| D | README.txt | 11 This project outputs to the console. It can be built and executed
20 Problems caused by out-dated project information can be addressed by
|
| /Zephyr-latest/samples/net/syslog_net/ |
| D | Kconfig | 21 app defore the backend is initialized. This can be
23 number can be configured here too.
|
| /Zephyr-latest/samples/basic/sys_heap/ |
| D | README.rst | 9 A simple sample that can be used with any :ref:`supported board <boards>` and
15 This application can be built on :ref:`native_sim <native_sim>` as follows:
|
| /Zephyr-latest/tests/lib/sprintf/ |
| D | README.txt | 11 This project outputs to the console. It can be built and executed
20 Problems caused by out-dated project information can be addressed by
|
| /Zephyr-latest/doc/services/logging/ |
| D | index.rst | 13 Custom frontend and backends can be used if needed.
21 - Custom frontend support. It can work together with backends.
25 - Timestamping with user provided function. Timestamp can have 32 or 64 bits.
30 - Printk support - printk message can be redirected to the logging.
37 Kconfig options (see :ref:`logging_kconfig`) logs can be gradually removed from
39 During compilation logs can be filtered out on module basis and severity level.
41 Logs can also be compiled in but filtered on run time using dedicate API. Run
43 Source of log messages can be a module or specific instance of the module.
64 modules can disable logging locally. Every module can specify its own logging
67 The global override can only increase the logging level. It cannot be used to
[all …]
|
| /Zephyr-latest/boards/shields/x_nucleo_bnrg2a1/doc/ |
| D | index.rst | 14 connector layout (the user can mount the ST Morpho connectors, if required). The
16 the user can change the default SPI clock, the SPI chip select and SPI IRQ by
27 More information about the board can be found at the
59 More information about X-NUCLEO-BNRG2A1 can be found here:
65 You can use the X-NUCLEO-BNRG2A1 as a Bluetooth Low-Energy controller
|
| /Zephyr-latest/boards/contextualelectronics/abc/doc/ |
| D | index.rst | 21 More information about the board can be found at the `ABC Board website`_.
47 Applications for the ``contextualelectronics_abc`` board configuration can be
80 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
91 Pins can be configured in the board pinctrl file. To see the available mappings,
94 'General purpose I/O'. Note that pins marked as 'low frequency I/O only' can only be used
|
12345678910>>...100
