Home
last modified time | relevance | path

Searched refs:can (Results 476 – 500 of 2493) sorted by relevance

1...<<11121314151617181920>>...100

/Zephyr-latest/tests/crypto/tinycrypt/
DREADME.txt10 This project outputs to the console. It can be built and executed
19 Problems caused by out-dated project information can be addressed by
/Zephyr-latest/samples/subsys/input/draw_touch_events/
DREADME.rst9 This sample will draw a small plus in the last touched coordinates, that way you can check
26 board is also supported and can be built as follows:
/Zephyr-latest/tests/drivers/can/timing/
DKconfig10 controllers can meet all of the bitrates listed below, and some board configurations may
11 impose limits on which bitrates can be met due to limitations in the CAN core clock
/Zephyr-latest/samples/bluetooth/direct_adv/
DREADME.rst14 can be done just after connection (no bonding required).
30 This sample can be found under :zephyr_file:`samples/bluetooth/direct_adv` in the
/Zephyr-latest/samples/subsys/console/echo/
DREADME.rst11 :c:func:`console_putchar` functions can be used to echo an input character
23 board. Alternatively you can run this using QEMU, as described in
/Zephyr-latest/samples/application_development/external_lib/
DREADME.rst18 your path. This can be setup using chocolatey or by manually installing it.
34 The pre-built make application can be downloaded from
/Zephyr-latest/tests/lib/c_lib/common/
DREADME.txt14 This project outputs to the console. It can be built and executed
23 Problems caused by out-dated project information can be addressed by
/Zephyr-latest/doc/services/tracing/
Dindex.rst23 An application can use one of the existing formats or define a custom format by
38 Although the user can extend any of the supported serialization formats
43 Users can generate a custom trace event by calling
99 How to serialize and emit fields as well as handling alignment, can be done
104 :kconfig:option:`CONFIG_TRACING_CTF` and can be used with the different transport
187 profiling. However, it can be quite useful for debugging in combination with breakpoints.
188 For example, if you set a breakpoint in an error handler, a snapshot trace can show the sequence
215 The default buffer size can be reduced if you are tight on RAM, or increased if you have RAM to
306 This stream port is designed for Zephyr tracing in QEMU. This can be an easy way to get started
352 Tracealyzer can receive trace streams over various interfaces, including files, sockets,
[all …]
/Zephyr-latest/boards/seeed/lora_e5_dev_board/doc/
Dlora_e5_dev_board.rst56 More information about the board can be found at the `LoRa-E5 Dev Board Wiki`_.
58 More information about LoRa-E5 STM32WLE5JC Module can be found here:
157 Applications for the ``lora_e5_dev_board`` board configuration can be built the
162 So before you can program a zephyr application to the module for the first time
164 In case you use an st-link debugger you can use the STM32CubeProgrammer GUI to
177 But the module can be debugged by connecting an external debug probe to the
180 ``pyocd``, ``blackmagic``, or ``jlink`` runner can be used to flash the board.
184 can be installed by adding "pack" support with the following pyocd command:
216 You can debug an application in the usual way. Here is an example for the
/Zephyr-latest/doc/develop/
Dbeyond-GSG.rst67 You can install the :ref:`Zephyr SDK <toolchain_zephyr_sdk>` to get toolchains for all
72 You can configure the Zephyr build system to use a specific toolchain by
96 you can unset this variable. Otherwise, set it to your chosen install location.
113 repos. We'll use the name ``zephyrproject``, but you can choose any
153 The :ref:`cmake_pkg` can be exported to CMake's user package registry if it has
181 You can build, flash, and run Zephyr applications on real
183 you can also run it in emulation with QEMU, or as a native application with
185 Additional information about building applications can be found in the
195 <reel_board>` here, but you can change the ``reel_board`` build target
229 Most hardware boards supported by Zephyr can be flashed by running
[all …]
/Zephyr-latest/boards/snps/nsim/arc_classic/doc/
Dindex.rst6 This platform can be used to run Zephyr RTOS on the widest possible range of ARC processors in
59 can only be instantiated with help of MDB.
87 there might be exceptions from that, especially for newly added targets. You can check supported
90 I.e. for the ``nsim/nsim_hs5x`` board we can check :zephyr_file:`boards/snps/nsim/arc_classic/nsim_…
92 The supported toolchains are listed in ``toolchain:`` array in ``.yaml`` file, where we can find:
94 * **zephyr** - implies ARC GNU toolchain from Zephyr SDK. You can find more information about
99 SDK yet. You can find more information about its usage here: :ref:`here <other_x_compilers>`.
100 * **arcmwdt** - implies proprietary ARC MWDT toolchain. You can find more information about its
105 samples can be only built with either GNU or MWDT toolchain due to some features limited to a
136 You can get more details about the building process by running build in verbose mode. It can be
[all …]
/Zephyr-latest/samples/boards/espressif/deep_sleep/socs/
Desp32c3.overlay9 /* On ESP32-C3, only GPIO0~5 can be used
Desp32c3_usb.overlay9 /* On ESP32-C3, only GPIO0~5 can be used
/Zephyr-latest/boards/shields/waveshare_epaper/doc/
Dindex.rst10 The shield can be used to drive various Electrophoretic (electronic ink)
15 More information about the shield can be found
76 This shield can only be used with a board that provides a configuration
/Zephyr-latest/boards/we/ophelia1ev/doc/
Dindex.rst28 antenna that can be connected to the available SMA connector.
42 and configure all the necessary software. Further information can be
56 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
/Zephyr-latest/boards/nordic/nrf54l09pdk/doc/
Dindex.rst33 The crystal oscillators can be configured to use either
62 Applications for the ``nrf54l09pdk/nrf54l09/cpuapp`` board target can be
74 and configure all the necessary software. Further information can be
/Zephyr-latest/subsys/mgmt/mcumgr/mgmt/
DKconfig15 With this enabled, applications and parts of code can register for MCUmgr event
21 callback function and events that want to be received. Multiple handlers can be
38 When this config is enabled, a user can use the field `custom_payload` in `mgmt_handler` to
/Zephyr-latest/doc/connectivity/networking/api/
Dhttp_client.rst16 It can be enabled with :kconfig:option:`CONFIG_HTTP_CLIENT` Kconfig option.
19 Therefore, depending on the application's needs, the library can communicate over
49 As the library can provide the response in chunks, the application must be able
/Zephyr-latest/boards/nordic/nrf54l20pdk/doc/
Dindex.rst33 The crystal oscillators can be configured to use either
63 Applications for the ``nrf54l20pdk/nrf54l20/cpuapp`` board target can be
75 and configure all the necessary software. Further information can be
/Zephyr-latest/doc/hardware/peripherals/
Dsmbus.rst16 lines. SMBus peripherals can provide various manufacturer information,
19 Devices on the bus can operate in three roles: as a Controller that
25 SMBus peripheral devices can initiate communication with Controller
Duart.rst22 With the Interrupt-driven API, possibly slow communication can happen in the
24 :ref:`kernel_data_passing_api` features can be used to communicate between
45 the interrupt-driven API or the asynchronous API can be used. Only enable the
/Zephyr-latest/doc/develop/sca/
Dgcc.rst26 GCC static analyzer can be controlled using specific options.
41 These parameters can be passed on the command line, or be set as environment variables.
61 the GCC static analysis can be run with a more recent `GNU Arm embedded toolchain
/Zephyr-latest/samples/modules/cmsis_dsp/moving_average/
DREADME.rst12 It can be run on any board supported in Zephyr, but note that CMSIS-DSP is specifically optimized
15 A **moving average** filter is a common method used for smoothing noisy data. It can be implemented
41 The demo can be built as follows:
/Zephyr-latest/samples/net/sockets/coap_server/
DREADME.rst42 functionality can be verified by using some external tool such as tcpdump
47 This sample can be built and executed on QEMU or native_sim board as
67 The IPv4 Wi-Fi support can be enabled in the sample with
/Zephyr-latest/doc/develop/languages/c/
Dcommon_libc.rst15 relying on the Zephyr function, :c:func:`clock_gettime`. This function can
21 The common dynamic memory management implementation can be enabled by
31 called ``z_malloc_partition``, which can be accessed from the user mode

1...<<11121314151617181920>>...100