Searched refs:can (Results 501 – 525 of 2493) sorted by relevance
1...<<21222324252627282930>>...100
| /Zephyr-latest/samples/net/vlan/ |
| D | README.rst | 13 The source code for this sample application can be found at:
25 :ref:`networking_with_eth_qemu`. You can use :file:`zeth-vlan.conf` configuration
54 can be executed on the Linux host. It creates two VLAN interfaces ``vlan.100``
|
| /Zephyr-latest/samples/drivers/adc/adc_dt/ |
| D | README.rst | 13 and prints the readings on the console. If voltage of the used reference can
28 the ``nucleo_l073rz`` board can be easily adjusted for other boards.
40 The sample can be built and executed for the
|
| /Zephyr-latest/samples/boards/st/i2c_timing/ |
| D | README.rst | 10 The I2C peripheral configuration is checked regarding the I2C bitrate which can be:
20 The calculation of that TIMING value can be given by the `STM32CubeMX`_ application
27 User can then configure timing in his application by adapting the following dts
|
| /Zephyr-latest/samples/subsys/modbus/rtu_client/ |
| D | README.rst | 25 can be used. This example uses DE signal, which is controlled by pin D9
32 Alternatively UART RX,TX signals of two boards can be connected crosswise.
37 This sample can be found under
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 18 Using these, a Zephyr application can be compiled together with
69 you can also just use the ``native_sim/native/64``
82 can and cannot be done.
87 You can imagine the code executes in a simulated CPU
102 - There can **not** be busy wait loops in the application code that wait for
148 stalled in it. To find the loop, you can run the binary in a debugger and
243 executes just as fast as it possibly can.
256 Your code can be debugged, instrumented, or analyzed with all normal native
259 Execution is fully reproducible, you can pause it without side-effects.
269 and, in some cases, can expose host HW as emulated target peripherals.
[all …]
|
| /Zephyr-latest/soc/nxp/mcx/mcxa/ |
| D | Kconfig.defconfig | 14 # Set to the minimal size of data which can be written.
|
| /Zephyr-latest/boards/shields/mikroe_ble_tiny_click/doc/ |
| D | index.rst | 21 This shield can only be used with a board that provides a mikroBUS |trade|
31 can be overcome by removing resistor R3 on the BLE TINY Click board, see
38 The `Renesas SmartBond Flash Programmer`_ tool can be used to download a
41 press the "Search Online" button. The required binary file can be selected
|
| /Zephyr-latest/samples/subsys/zbus/work_queue/ |
| D | README.rst | 9 … observer can react "instantaneously" by using a listener callback. It can schedule a job, pushing…
14 This project outputs to the console. It can be built and executed
|
| /Zephyr-latest/boards/mikroe/mini_m4_for_stm32/doc/ |
| D | mikroe_mini_m4_for_stm32.rst | 10 a 32.768KHz crystal which can be used for the internal RTCC module.
27 The board can be flashed by using STLinkV2 with the following connections.
62 Applications for the ``mikroe_mini_m4_for_stm32`` board configuration can
100 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/olimex/stm32_h405/doc/ |
| D | index.rst | 12 Information about the board can be found at the
122 is 8 MHz. The processor can setup HSE to drive the master clock,
123 which can be set as high as 168 MHz.
163 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 18 The channel data most recently fetched can then be obtained as a
31 Using fetch and get sensor can be read in a polling manner from software threads.
52 (:ref:`workqueues_v2`) or a dedicated thread. A great example can be found in
71 (GLOBAL_THREAD) case the work queue itself can be the source of variable
|
| /Zephyr-latest/samples/subsys/modbus/tcp_gateway/ |
| D | README.rst | 24 The user can of course try out other client implementations with this sample.
28 Alternatively UART RX,TX signals of two boards can be connected crosswise.
33 This sample can be found under
74 To read LED0, LED1, LED2 state FC05 command (read_coils) can be used.
|
| /Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/ |
| D | README.rst | 19 it should support a clock source alternative to Cortex Systick that can be used
26 that can be requested dynamically by device on activity detection (HSI on STM32WB).
53 are enabled, but user can also deactivate both or former to see each configuration in play.
87 With all these conditions matched, one can reach 10uA on stm32l562e_dk with this sample.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | tftp.rst | 6 Zephyr provides a simple TFTP client library that can enabled with
|
| /Zephyr-latest/boards/others/promicro_nrf52840/ |
| D | Kconfig | 10 If selected, applications are linked so that they can be loaded by Nordic
|
| /Zephyr-latest/boards/wiznet/w5500_evb_pico2/doc/ |
| D | index.rst | 39 The peripherals of the RP2350A SoC can be routed to various pins on the board.
40 The configuration of these routes can be modified through DTS. Please refer to
101 If you don't have an SWD adapter, you can flash the Raspberry Pi Pico with
110 The SWD interface can also be used to debug the board. To achieve this, you can
|
| /Zephyr-latest/boards/ezurio/rm1xx_dvk/doc/ |
| D | index.rst | 34 More information about the module can be found on the
77 of infrequently updated data and small datasets and can be used with
87 A Semtech SX1272 transceiver chip is present in the module which can be
100 and configure all the necessary software. Further information can be
114 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
|
| /Zephyr-latest/boards/electronut/nrf52840_blip/doc/ |
| D | index.rst | 53 * Reset = SW5 = P0.18 (can be used as GPIO also)
83 Applications for the ``nrf52840_blip`` board configuration can be
89 GDB can directly connect to this port without requiring a GDB server by specifying
136 You can build and flash the examples to make sure Zephyr is running correctly on
137 your board. The button and LED definitions can be found in
|
| /Zephyr-latest/boards/st/stm32h735g_disco/doc/ |
| D | index.rst | 27 More information about the board can be found at the `STM32H735G-DISCO website`_.
28 More information about STM32H735 can be found here:
56 The STM32H735G System Clock can be driven by an internal or external oscillator,
82 Alternatively, OpenOCD or JLink can also be used to flash the board using
96 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/olimex/stm32_h103/doc/ |
| D | index.rst | 13 Information about the board can be found at the
56 PC4 can be configured as a GPIO input to detect power on the USB port. It is
59 PC11 can be used to disconnect the pull-up resistor on the USB-DP line by
168 The ``blackmagicprobe`` can also be used to program the device.
183 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/renesas/fpb_ra4e1/doc/ |
| D | index.rst | 53 Detailed hardware features can be found at:
66 Applications for the ``fpb_ra4e1`` board can be
74 Program can be flashed to FPB-RA4E1 via the on-board SEGGER J-Link debugger.
92 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
103 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | extensions.rst | 11 - Default values can be applied to existing symbols without
34 however they can be wrapped in ``if`` statements. The two statements below
108 ``rsource`` can be used to create :file:`Kconfig` "subtrees" that can be
113 A drawback of ``rsource`` is that it can make it harder to figure out where a
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | semaphores.rst | 16 Any number of semaphores can be defined (limited only by available RAM). Each
21 * A **count** that indicates the number of times the semaphore can be taken.
25 can reach.
27 A semaphore must be initialized before it can be used. Its count must be set
69 Alternatively, a semaphore can be defined and initialized at compile time
|
| /Zephyr-latest/boards/makerbase/mks_canable_v20/doc/ |
| D | index.rst | 21 More information about the board can be found at the `MKS CANable V2.0 website`_.
25 More information about STM32G431KB can be found here:
73 Applications for the ``mks_canable_v20`` board target can be built and
101 If option ``-S rtt-console`` is selected, the connection to the target can be established as follow…
120 You can debug an application in the usual way. Here is an example for the
|
| /Zephyr-latest/boards/ezurio/bl652_dvk/doc/ |
| D | bl652_dvk.rst | 37 More information about the board can be found at the
169 and configure all the necessary software. Further information can be
185 can be found. For example, under Linux, :code:`/dev/ttyUSB0`.
218 You can build and flash the examples to make sure Zephyr is running correctly on
219 your board. The button and LED definitions can be found in
|
1...<<21222324252627282930>>...100
