| /Zephyr-latest/drivers/crypto/ |
| D | Kconfig | 37 int "Maximum of sessions TinyCrypt shim driver can handle"
41 This can be used to tweak the amount of sessions the driver
42 can handle in parallel.
70 int "Maximum of sessions mbedTLS shim driver can handle"
74 This can be used to tweak the amount of sessions the driver
75 can handle in parallel.
|
| /Zephyr-latest/drivers/can/ |
| D | can_xmc4xxx.c | 80 CAN_NODE_TypeDef *can; member
105 XMC_CAN_NODE_SetAnalyzerMode(dev_cfg->can); in can_xmc4xxx_set_mode()
107 XMC_CAN_NODE_ReSetAnalyzerMode(dev_cfg->can); in can_xmc4xxx_set_mode()
137 dev_cfg->can->NBTR = reg; in can_xmc4xxx_set_timing()
295 CAN_XMC4XXX_REG_TO_NODE_IND(dev_cfg->can), mo_index); in can_xmc4xxx_init_fifo()
331 CAN_XMC4XXX_REG_TO_NODE_IND(dev_cfg->can), mo_index); in can_xmc4xxx_init_fifo()
455 uint8_t tec = XMC_CAN_NODE_GetTransmitErrorCounter(dev_cfg->can); in can_xmc4xxx_get_state_from_status()
456 uint8_t rec = XMC_CAN_NODE_GetTransmitErrorCounter(dev_cfg->can); in can_xmc4xxx_get_state_from_status()
489 status = XMC_CAN_NODE_GetStatus(dev_cfg->can); in can_xmc4xxx_get_state()
676 XMC_CAN_NODE_ResetInitBit(dev_cfg->can); in can_xmc4xxx_state_change_handler()
[all …]
|
| /Zephyr-latest/tests/kernel/fatal/message_capture/ |
| D | README | 1 This test case verifies that kernel fatal error logging message can be captured.
4 the system can capture the print information.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | video.rst | 15 which can produce, process, consume or transform video data. The video API is
22 Each video device can have one or more endpoints. Output endpoints configure
31 defined by the endpoint format. A video buffer can be queued to a device
33 the operation is achieved, buffer can be dequeued for post-processing,
41 controls available which can be generic, related to a device class or vendor
|
| /Zephyr-latest/tests/drivers/audio/dmic_api/ |
| D | README.txt | 9 * Verify the DMIC can sample from one left channel
11 * Verify the DMIC can sample from a stereo L/R pair
16 * Verify that the DMIC can restart sampling after being paused and resumed
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | heartbeat.rst | 17 the active features on the node. Through this, a receiving node can determine
31 Heartbeat publication is controlled through the Configuration models, and can
36 publication can be configured to stop after a certain number of messages, or
41 set of features that can trigger the publication is configurable.
43 The two publication types can be combined.
48 A node can be configured to subscribe to Heartbeat messages from one node at
|
| /Zephyr-latest/samples/bluetooth/cap_acceptor/ |
| D | README.rst | 12 It can also be configured to start scanning for broadcast audio streams by itself.
14 This sample can be found under :zephyr_file:`samples/bluetooth/cap_acceptor` in the Zephyr tree.
34 You can build both the application core image and an appropriate controller image for the network
43 If you prefer to only build the application core image, you can do so by doing instead:
50 In that case you can pair this application core image with the
57 Similarly to how you would for real HW, you can do:
|
| /Zephyr-latest/boards/snps/em_starterkit/doc/ |
| D | index.rst | 9 EM5D, EM7D, EM9D, and EM11D cores. The Zephyr RTOS can be used with the
14 Documentation for this board can be found at `embARC website`_.
19 The latest version of EM Starter Kit is 2.3, developer can upgrade from
21 The default configuration for EM Starter Kit boards can be found in
30 If you have a larger program, you can select the EM7D or EM11D, which gives
41 The ARC EM Starter Kit main board has 6 Pmod connectors. These can be configured
45 3 buttons, and 4 dip switches that can be used with GPIO.
47 The Xilinx Spartan(R)-6 LX150 FPGA can auto-load one of 3 FPGA SoC bit files
50 Documentation and general information for the board can be found at the
69 sensors, displays, etc. With the Pmod interface, you can prototype your
[all …]
|
| /Zephyr-latest/subsys/net/lib/lwm2m/ |
| D | Kconfig.ucifi | 49 device that can be stored in this object.
57 device that can be stored in this object.
65 to a device that can be stored in this object.
73 communicate with the device on the LPWAN network assigned that can be
82 that can be stored in this object.
91 that can be stored in this object.
99 be shared with other members to be part of a multicast group that can
|
| /Zephyr-latest/boards/shields/mcp2515/ |
| D | adafruit_can_picowbell.overlay | 11 mcp2515_adafruit_can_picowbell: can@0 {
19 can-transceiver {
|
| D | dfrobot_can_bus_v2_0.overlay | 11 mcp2515_dfrobot_can_bus_v2_0: can@0 {
19 can-transceiver {
|
| D | keyestudio_can_bus_ks0411.overlay | 11 mcp2515_keyestudio_can_bus_ks0411: can@0 {
19 can-transceiver {
|
| /Zephyr-latest/subsys/usb/host/ |
| D | Kconfig.usbip | 29 Number of submit commands that can be stored in the backlog.
32 int "Number of devices that can be exported"
36 Number of devices that can be exported.
|
| /Zephyr-latest/soc/espressif/common/ |
| D | Kconfig.spiram | 72 only lower 4MB can be allocated using k_malloc().
124 can forgo being placed in IRAM, thus optimizing RAM usage (see External RAM documentation
134 can forgo being placed in IRAM, thus optimizing RAM usage (see External RAM documentation
154 …The PSRAM CLOCK IO can be any unused GPIO, user can config it based on hardware design. If user use
155 1.8V flash and 1.8V psram, this value can only be one of 6, 7, 8, 9, 10, 11, 16, 17.
162 The PSRAM CS IO can be any unused GPIO, user can config it based on hardware design. If user use
163 1.8V flash and 1.8V psram, this value can only be one of 6, 7, 8, 9, 10, 11, 16, 17.
174 …User can config it based on hardware design. For ESP32-D2WD chip, the psram can only be 1.8V psram,
175 so this value can only be one of 6, 7, 8, 9, 10, 11, 16, 17.
182 …User can config it based on hardware design. For ESP32-D2WD chip, the psram can only be 1.8V psram,
[all …]
|
| /Zephyr-latest/samples/net/sockets/http_server/ |
| D | README.rst | 12 The server supports the HTTP/1.1 protocol which can also be upgraded to HTTP/2,
32 - This overlay config can be added for IEEE 802.15.4 support.
35 - This overlay config can be added for connecting via network USB.
38 - This overlay config can be added to build the HTTPS variant.
52 When the server is up, we can make requests to the server using either HTTP/1.1 or
100 The server sample contains several parameters that can be customized based on
106 clients that the server can handle simultaneously.
109 streams that can be established per client.
116 URL that the server can process.
122 To customize these options, we can run ``west build -t menuconfig``, which provides
[all …]
|
| /Zephyr-latest/dts/arm/infineon/cat3/xmc/ |
| D | xmc4700_F144x2048.dtsi | 100 &can {
103 compatible = "infineon,xmc4xxx-can-node";
110 compatible = "infineon,xmc4xxx-can-node";
117 compatible = "infineon,xmc4xxx-can-node";
|
| /Zephyr-latest/samples/subsys/usb/hid-keyboard/ |
| D | README.rst | 18 or keys defined at the board level that can generate input events.
19 At least one key is required and up to four can be used. The first three keys
23 The example can use up to three LEDs, configured via the devicetree alias such
29 This sample can be built for multiple boards, in this example we will build it
|
| /Zephyr-latest/drivers/dma/ |
| D | Kconfig.mcux_lpc | 17 Each DMA descriptor can be used to transfer (1024*width) bytes of data.
25 The MCUX LPC DMA driver can save memory by not allocating static data
26 depending on this value. So, the application can save some data memory
31 in any DMA controller hardware. About 1 KB per 3-4 channels unused can
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | network_monitoring.rst | 26 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
35 interface so that we can transfer monitoring data from Zephyr to host.
56 You can then use Wireshark to monitor the proper network interface.
58 After the tunneling interfaces have been created, you can use for example
61 it can print the captured data to screen and optionally can also save the
93 Instead of the ``net-capture.py`` script, you can for example use ``netcat``
101 The IP address above is the inner tunnel endpoint, and can be changed and
111 In this example, we use the ``native_sim`` board. You can also use any other board
130 Any other application can be used too, just make sure that suitable
134 The network capture can be configured automatically if needed, but
[all …]
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | README.md | 17 The testcases can be executed from the root directory using
25 The coverage for all the tests can be run using the command below. This will collect all the tests …
31 Then we can generate the coverage report for just twister script using
43 The html coverage report for twister can be generated using
49 If needed,the full coverage html report can be generated in every run of "pytest" in the tests dire…
|
| /Zephyr-latest/samples/net/sockets/txtime/ |
| D | README.rst | 17 User can control how long the application should wait between packets sent by
19 Also the TXTIME value can be specified in the config file by setting the
26 When the application is run, it starts to send UDP packets. You can start
28 send the data back to this application. Optionally you can set
33 This sample can be built and executed on qemu_x86 board as
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | atomic.rst | 6 An :dfn:`atomic variable` is one that can be read and modified
17 Any number of atomic variables can be defined (limited only by available RAM).
34 By default an atomic variable is initialized to zero. However, it can be given
47 The following code shows how an atomic variable can be used to keep track
69 An array of 32-bit atomic variables can be defined in the conventional manner.
70 However, you can also define an N-bit array of atomic variables using
73 A single bit in array of atomic variables can be manipulated using
76 The following code shows how a set of 200 flag bits can be implemented
129 All atomic services APIs can be used by both threads and ISRs.
|
| /Zephyr-latest/samples/userspace/hello_world_user/ |
| D | README.rst | 8 A simple Hello World example that can be used with any supported board and
13 This application can be built into modes:
22 It can be built and executed on QEMU as follows:
|
| /Zephyr-latest/boards/native/native_sim/doc/ |
| D | index.rst | 15 With it, a Zephyr application can be compiled together with
84 You can run it with the ``--help`` command line switch to get a list of
107 Since the Zephyr executable is a native application, it can be debugged and
109 information, so it can be run directly in, for example, ``gdb`` or instrumented
113 (there are no asynchronous or random components), you can execute the
127 You can also build Zephyr with the `Address Sanitizer`_. To do this, set
140 You can also build Zephyr with the `Undefined Behavior Sanitizer`_. To do this, set
171 You can use this target if you cannot compile or run 32 bit binaries.
180 but you can also select to build it with :kconfig:option:`CONFIG_MINIMAL_LIBC` or with
200 It does not intend to model any particular HW, and as such can only be used
[all …]
|
| /Zephyr-latest/soc/microchip/mec/mec172x/ |
| D | Kconfig | 32 pin is ignored. All other JTAG pins can be used as GPIOs
38 JTAG port in SWD mode. I2C09 and ADC00-03 can be used.
44 to see if ADC00-03 can be used or not.
58 I2C09 can be used, but ADC00-03 cannot.
64 I2C09 cannot be used. ADC00-03 can be used.
|
