Searched refs:can (Results 126 – 150 of 2493) sorted by relevance
12345678910>>...100
| /Zephyr-latest/samples/net/sockets/echo_async_select/ |
| D | README.rst | 15 The source code for this sample application can be found at:
45 supports multiple concurrent client connections. You can open
47 The sample supports up to three connected clients, but this can be adjusted
53 The same application source code can be built for a POSIX system, e.g.
77 As can be seen, the behavior of the application is the same as the Zephyr
|
| /Zephyr-latest/samples/bluetooth/bap_broadcast_sink/ |
| D | README.rst | 14 This sample can be found under
39 You can build both the application core image and an appropriate controller image for the network
48 If you prefer to only build the application core image, you can do so by doing instead:
55 In that case you can pair this application core image with the
62 Similarly to how you would for real HW, you can do:
|
| /Zephyr-latest/samples/bluetooth/bap_broadcast_source/ |
| D | README.rst | 17 This sample can be found under
40 You can build both the application core image and an appropriate controller image for the network
49 If you prefer to only build the application core image, you can do so by doing instead:
56 In that case you can pair this application core image with the
63 Similarly to how you would for real HW, you can do:
|
| /Zephyr-latest/samples/bluetooth/ccp_call_control_client/ |
| D | README.rst | 17 This sample can be found under :zephyr_file:`samples/bluetooth/ccp_call_control_client`
37 You can build both the application core image and an appropriate controller image for the network
46 If you prefer to only build the application core image, you can do so by doing instead:
53 In that case you can pair this application core image with the
60 Similarly to how you would for real HW, you can do:
|
| /Zephyr-latest/samples/bluetooth/ccp_call_control_server/ |
| D | README.rst | 17 This sample can be found under :zephyr_file:`samples/bluetooth/ccp_call_control_server` in the Zeph…
36 You can build both the application core image and an appropriate controller image for the network
45 If you prefer to only build the application core image, you can do so by doing instead:
52 In that case you can pair this application core image with the
59 Similarly to how you would for real HW, you can do:
|
| /Zephyr-latest/boards/shields/x_nucleo_eeprma2/doc/ |
| D | index.rst | 9 The ST X-NUCLEO-EEPRMA2 expansion board can be used to evaluate M24xx series I2C
13 and ST morpho connectors can be mounted if required.
22 More information about the board can be found at the
28 This shield can only be used with a development board that provides a
32 The SPI EEPROM devices can write protect complete memory blocks by setting
53 The :zephyr:code-sample:`eeprom` sample can be used to demonstrate the expansion boards
56 which can be overwritten to use the other EEPROM devices instead.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | proxy.rst | 9 and the initial value can be set with :c:member:`bt_mesh_cfg_srv.gatt_proxy`.
11 Nodes with the Proxy feature enabled can advertise with Network Identity and Node Identity,
19 A node supporting the Proxy feature and the :ref:`bluetooth_mesh_models_priv_beacon_srv` model can
33 To solicit the node, the legacy device can send a Solicitation PDU by calling the
51 node that supports the Solicitation PDU RPL Configuration Client model can clear a section of the
54 therefore, the Solicitation PDU RPL Configuration Client can be instantiated on any device in the
59 advertisement can be configured by the On-Demand Private Proxy Client model.
|
| D | statistic.rst | 12 parameters can be easily extended by customer values.
14 An application can read out and clean up statistics at any time.
|
| D | lcd_srv.rst | 25 metadata that can be read by the Large Composition Data Client model. The metadata list can be
29 metadata, and a pointer to the raw data. Entries can be created using the
32 helper macro :c:macro:`BT_MESH_MODELS_METADATA_NONE` can be used instead.
|
| /Zephyr-latest/boards/96boards/argonkey/doc/ |
| D | index.rst | 13 family products. It can also be used as a standalone board.
77 More information about the board can be found at the
80 The default board configuration can be found in
101 96Boards Argonkey can be driven by an internal oscillator as well as the main
124 I2C3 goes to the P2 connector and can be used to attach external sensors.
158 96Boards Argonkey can be flashed by two methods, one using the ROM
163 which can be triggered by using the BOOT0 pin. The ROM bootloader supports
165 UART case only. You can read more about how to enable and use the ROM
176 FTDI chip. The UART pins on ArgonKey can be found on the P3 low speed
206 device with mass storage capability. The device can be then mounted in linux
[all …]
|
| /Zephyr-latest/soc/nxp/common/ |
| D | Kconfig.rom_loader | 5 bool "Create output image that NXP ROM can load from FlexSPI to ram"
9 Builds an output image that the BootROM can load from the
|
| /Zephyr-latest/boards/we/proteus2ev/doc/ |
| D | index.rst | 25 More information about the radio module can be found the Würth Elektronik web page https://www.we-o…
57 Applications for the ``we_proteus2ev/nrf52832`` board configuration can be
66 and configure all the necessary software. Further information can be
80 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
107 You can build and flash the examples to make sure Zephyr is running correctly on
108 your board. The button and LED definitions can be found in
|
| /Zephyr-latest/doc/services/storage/fcb/ |
| D | fcb.rst | 6 Flash circular buffer provides an abstraction through which you can treat
27 Entries can be appended to the end of the area until storage space is
43 - Call :c:func:`fcb_append` to get the location where data can be written. If
44 this fails due to lack of space, you can call :c:func:`fcb_rotate` to erase
55 :c:func:`flash_area_read`. You can tell when all data from within a sector
57 can call :c:func:`fcb_rotate`, if you're done with that data.
|
| /Zephyr-latest/doc/services/crypto/random/ |
| D | index.rst | 14 generators (RNG) can be used on platforms with appropriate hardware support.
17 The algorithm can be provided by `TinyCrypt <https://01.org/tinycrypt>`_
31 These options can be found in the following path :zephyr_file:`subsys/random/Kconfig`.
39 An override of the default value can be specified in the SOC or board
64 override of the default value can be specified in the SOC or board
83 Personalization data can be provided in addition to the entropy source
|
| /Zephyr-latest/boards/vcc-gnd/yd_stm32h750vb/doc/ |
| D | index.rst | 10 More information about STM32H750 can be found here:
38 The STM32H750VB System Clock can be driven by an internal or external oscillator,
48 pattern, which can be triggered by using the BOOT0 button.
54 debian/ubuntu can be quite old, so you might have to build dfu-util from source.
65 The dfu-util runner is supported on this board and so a sample can be built and
80 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/shields/tcan4550evm/ |
| D | tcan4550evm.overlay | 19 tcan4x5x_tcan4550evm: can@0 {
33 can-transceiver {
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | message_queues.rst | 17 Any number of message queues can be defined (limited only by available RAM).
26 * A **maximum quantity** of data items that can be queued in the ring buffer.
28 A message queue must be initialized before it can be used.
31 A data item can be **sent** to a message queue by a thread or an ISR.
43 A data item can be **received** from a message queue by a thread.
53 A thread can also **peek** at the message on the head of a message queue without
92 Alternatively, a message queue can be defined and initialized at compile time
109 If the message queue fills up because the consumers can't keep up, the
110 producing thread throws away all existing data so the newer data can be saved.
141 can be returned due to :c:func:`k_msgq_purge`.
[all …]
|
| /Zephyr-latest/boards/renode/cortex_r8_virtual/doc/ |
| D | index.rst | 6 The Cortex-R8 Virtual board is a virtual platform that can be emulated with Renode.
18 Applications for the ``cortex_r8_virtual`` board target can be built
29 but you can use this configuration to run Zephyr applications
58 Renode can serve as a GDB server. For more information, refer to the
|
| /Zephyr-latest/doc/services/tfm/ |
| D | testsuites.rst | 9 These test suites can be run from Zephyr via an appropriate sample application
15 The regression test suite can be run via the :ref:`tfm_regression_test` sample.
26 test suites that can be used to validate that PSA API specifications are
30 Only one of these suites can be run at a time, with the available test suites
|
| /Zephyr-latest/samples/net/ptp/ |
| D | README.rst | 12 The source code for this sample application can be found at:
18 For generic host connectivity, that can be used for debugging purposes, see
43 One can enable debug prints by setting
66 When the Zephyr image is build, you can start it like this:
|
| /Zephyr-latest/tests/bluetooth/tester/ |
| D | README | 11 BTP specification can be found in auto-pts project repository:
29 The btproxy tool from BlueZ can be used to give access to a Bluetooth controller
38 CONF_FILE=qemu.conf. After this qemu can be started through the "run"
44 'bt-stack-tester' UNIX socket (previously set in Makefile) can be used for now
|
| /Zephyr-latest/samples/net/sockets/echo_service/ |
| D | README.rst | 14 The socket service is a concept where many blocking sockets can be listened by
15 one thread, and which can then trigger a callback if there is activity in the set
20 The source code for this sample application can be found at:
51 at time. After the current client disconnects, the next connection can proceed.
|
| /Zephyr-latest/samples/drivers/i2s/echo/ |
| D | README.rst | 18 The sample uses the WM8731 audio CODEC that can be found, for example,
19 on the Audio Codec Shield, but it can be easily adapted to use other
29 More information about the used shield and the CODEC itself can be found here:
37 The code can be found in :zephyr_file:`samples/drivers/i2s/echo`.
|
| /Zephyr-latest/boards/sparkfun/micromod/doc/ |
| D | index.rst | 12 and can insert into any MicroMod carrier board. More information can be found in
45 in the MicroMod form-factor. More information can be found in
127 Applications for the ``micromod/nrf52840`` board target can be
136 and configure all the necessary software. Further information can be
154 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
181 You can build and flash the example to make sure Zephyr is running correctly on
182 your board. The button and LED definitions can be found in
189 to the qspi interface. It can be tested with the samples/drivers/jesd216 app.
|
| /Zephyr-latest/boards/renesas/rcar_salvator_x/doc/ |
| D | rcar_salvator_x.rst | 14 like USB, Ethernet, HDMI and can work standalone or can be adapted to other boards,
21 More information about the board can be found at `Renesas R-Car Development Support website`_.
26 Hardware capabilities for the H3 Salvator-X for can be found on the `eLinux H3 Salvator-X page`_
35 More information about the SoC that equips the board can be found here:
57 | CAN | can | normal mode |
77 'SW21', 'SW22' can be used as input, and the software contollable LEDs 'LED4',
78 'LED5', 'LED6' can be used as output.
130 Applications for the ``rcar_salvator_x`` board configuration can be built
|
12345678910>>...100
