Searched refs:can (Results 426 – 450 of 2493) sorted by relevance
1...<<11121314151617181920>>...100
| /Zephyr-latest/soc/nxp/imx/ |
| D | Kconfig | 10 # can override the defaults given here
|
| /Zephyr-latest/samples/subsys/usb/mass/ |
| D | README.rst | 12 into an USB disk. This sample can be found under
23 This sample can be built for multiple boards, customized through overlays found
26 can be chosen passing Kconfig configuration via the -D command-line switch.
46 If more than 96KiB are available, FAT files system can be used
116 If a board with SD card controller is available, the example can be built as
126 In case the board has no support for SD card controller, but the card can
127 be connected to SPI using e.g. a shield, example can be built as follows:
137 Depending on the size of the media it can take time until the file system has
200 While a FAT-based file system can be mounted by many systems automatically,
201 mounting the littlefs file system on a Linux or FreeBSD system can be
[all …]
|
| /Zephyr-latest/boards/96boards/carbon/doc/ |
| D | stm32f401xe.rst | 27 sample application that can be flashed onto the nRF51822
34 After you have flashed your nRF51, you can perform basic validation
69 More information about STM32F401RE can be found here:
101 More details about the board can be found at `96Boards website`_.
103 The default configuration can be found in
196 More detailed information about the connectors can be found in
252 pattern, which can be triggered by using the BOOT0 pin. The ROM bootloader
253 supports flashing via USB (DFU), UART, I2C and SPI. You can read more about
264 debian/ubuntu can be quite old, so you might have to build dfu-util from source.
317 can be found. For example, under Linux, :code:`/dev/ttyUSB0`.
[all …]
|
| /Zephyr-latest/boards/espressif/esp32s3_eye/doc/ |
| D | index.rst | 51 …ixels has a 66.5° field of view and a maximum resolution of 1600x1200. You can change the resoluti…
54 …the USB power is not supplied, or the 5 V to 3.3 V LDO is broken. Software can configure GPIO3 to …
69 …- There are six function buttons on the board. Users can configure any functions as needed except …
87 …- Used for soldering a battery socket to connect an external Li-ion battery that can serve as an a…
113 - Four strapping pins led out from the main board. They can be used as testing points.
119 - LCD_RST testing point. You can use it to reset the LCD display with control signals.
161 User can select the MCUboot bootloader by adding the following line
185 images. But it can be configured to create other kind of images.
214 For that reason, images can be built one at a time using traditional build.
258 Espressif maintains their own fork of the project. The custom OpenOCD can be obtained at
[all …]
|
| /Zephyr-latest/boards/nxp/s32z2xxdc2/doc/ |
| D | index.rst | 18 Information about the hardware and design resources can be found at
51 | CANEXCEL | on-chip | can |
53 | FLEXCAN | on-chip | can |
129 The SoC has 12 LINFlexD instances that can be used in UART mode. The console can
159 can be used.
190 Applications for the ``s32z2xxdc2`` boards can be built in the usual way as
218 Replace ``<port>`` with the port where the board can be found. For example,
224 You can build and debug the :zephyr:code-sample:`hello_world` sample for the board
241 At this point you can do your normal debug session. Set breakpoints and then
276 To imitate a similar behavior using NXP S32 Debug Probe runner, you can run the
[all …]
|
| /Zephyr-latest/boards/st/stm32f4_disco/doc/ |
| D | index.rst | 32 More information about the board can be found at the `STM32F4DISCOVERY website`_.
65 More information about STM32F407VG can be found here:
130 Applications for the ``stm32f4_disco`` board configuration can be built and
140 Alternatively, OpenOCD or JLink can also be used to flash the board using
171 You can debug an application in the usual way. Here is an example for the
193 https://www.skpang.co.uk/products/can-bus-can-fd-breakout-board-5v-supply-and-3-3v-logic
|
| /Zephyr-latest/boards/cdns/xt-sim/doc/ |
| D | index.rst | 7 synthesizable 32-bit RISC processor core. Processor and SOC vendors can select
23 Xtensa cores can be configured to use either internal or external timers.
42 On Debian/Ubuntu systems, you can install ``gcc-multilib`` package as follows:
53 You can use the following code to create that file:
83 Once the ``~/.zephyrrc`` file is created, you can start working. However, each
85 before you can compile anything:
160 The Xtensa executable can be run in the simulator either with a standalone core,
|
| /Zephyr-latest/boards/pimoroni/pico_plus2/doc/ |
| D | index.rst | 20 - 48 multi-function GPIO pins including 8 that can be used for ADC
28 - 3-pin debug connector, this can use with `Raspberry Pi Debug Probe`_.
36 You can use peripherals that are made by using the PIO.
|
| /Zephyr-latest/cmake/compiler/arcmwdt/ |
| D | target.cmake | 39 # The MWDT compiler can replace some code with call to builtin functions.
40 # We can't rely on these functions presence if we don't use MWDT libc.
41 # NOTE: the option name '-fno-builtin' is misleading a bit - we still can
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro-scope-purpose.rst | 26 API, which you can use to get information from your devicetree.
35 All Zephyr and application source code files can include and use
43 messages. You always can tell a generated- from a non-generated macro:
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | semihost.rst | 23 by an application. This can be useful when attempting to validate the behaviour
24 of code across datasets that are larger than what can fit into ROM of an
25 emulated platform. File paths can be either absolute, or relative to the
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/sample_test/ |
| D | CMakeLists.txt | 7 # You can name the project however you like. Having a unique name is encouraged.
36 # "helper" functions can be isolated in their own file, minimizing visual
39 # Common data can live in a header included by multiple roles (e.g. service or
|
| /Zephyr-latest/doc/develop/sca/ |
| D | index.rst | 8 The build setting :makevar:`ZEPHYR_SCA_VARIANT` can be used to specify the SCA
25 You can provide support for out of tree SCA tools by creating the following
50 :makevar:`SCA_TOOL` can be set as a regular CMake setting using
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server_mt/ |
| D | README.rst | 19 The source code for this sample application can be found at:
46 Alternatively, a tool like ``curl`` can be used:
52 Finally, you can run an HTTP profiling/load tool like Apache Bench
|
| /Zephyr-latest/samples/boards/nordic/nrfx/ |
| D | README.rst | 13 so that the nrfx_gpiote driver can use it. Additionally, it shows
14 how the DPPI/PPI subsystem can be used to connect tasks and events of
37 The code can be found in :zephyr_file:`samples/boards/nordic/nrfx`.
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 55 you can build and run all possible tests using the following options:
74 If you want to run tests on one or more specific platforms, you can use
78 you can use ``--platform board@revision`` to test on a specific revision.
80 The list of command line options supported by twister can be viewed using:
130 - can
165 simulation can be selected with ``--simulation <simulation_name>``.
173 The list of supported toolchains that can build this board. This should match
182 A list of features this board supports. This can be specified as a single word
190 This indicates the board does support PCI. You can make a test scenario build or
199 A test scenario can depend on 'eth' to only test ethernet or on 'netif' to run
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | sockets.rst | 85 TLS credentials must be registered in the system before they can be used with
89 numeric value of type :c:type:`sec_tag_t`, called a tag. This value can be used
93 The following TLS credential types can be registered in the system:
109 By default certificates in DER format are supported. PEM support can be enabled
115 A secure socket can be created by specifying secure protocol type, for instance:
121 Once created, it can be configured with socket options. For instance, the
122 CA certificate and hostname can be set:
139 Once configured, socket can be used just like a regular TCP socket.
159 Socket offloading can be enabled with :kconfig:option:`CONFIG_NET_SOCKETS_OFFLOAD`
242 The socket dispatcher can be enabled with :kconfig:option:`CONFIG_NET_SOCKETS_OFFLOAD_DISPATCHER`
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-arch.rst | 45 (HCI) protocol. HCI can be implemented over a range of different physical
47 can send to a Controller and the events that it can expect in return, and also
49 ensures that different Host and Controller implementations can communicate
63 implements all three layers and the application itself. This can also be called a
68 the two can be implementation-specific. This configuration is well suited for
77 Zephyr's very own Bluetooth Host and Controller, users of the Zephyr Controller can
79 the host can be the Linux Bluetooth Host stack (BlueZ) running on any processor
90 the Bluetooth subsystem can be configured in multiple ways during the build process to
93 Bluetooth-enabled builds that can be produced from the Zephyr project codebase:
129 used for Controller-only builds can be built as Host-only
[all …]
|
| /Zephyr-latest/boards/nordic/nrf54h20dk/support/ |
| D | nrf54h20_cpuflpr.JLinkScript | 2 // Base address where DMI registers can be found in the APB address space
|
| D | nrf54h20_cpuppr.JLinkScript | 2 // Base address where DMI registers can be found in the APB address space
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 17 SoC has multiple controllers, they can be used simultaneously. Full and
73 be instantiated. A USB controller device can be assigned to multiple contexts,
74 but only one context can be initialized and used at a time. Context properties
130 can have multiple configurations with different set of functions at different
131 speeds. A function or class can be registered on a USB device before
135 :c:func:`usbd_register_all_classes` can be used to register all available
146 changed. A device can be deinitialized with :c:func:`usbd_shutdown` and all
147 instances can be reused, but the previous steps must be repeated. So it is
164 if the USB device is connected to a USB host controller, the host can start
165 enumerating the device. The application can disable the USB device using
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | controller.rst | 21 CAN controllers can only initialize when the bus is in the idle (recessive)
53 sample point can be moved.
57 Phase_Seg1and Phase_Seg2) are initially set from the device-tree and can be
62 This identifier can either have 11-bit width (Standard or Basic Frame) or
75 Filters can either match exactly or a specified part of the identifier.
85 Error-frames can either be error passive or error active, depending on the state
88 dominant bits, which is a violation of the stuffing rule that all nodes can
91 An initialized node can be in one of the following states:
108 You can read more about CAN bus in this
219 function, it is possible to receive frames synchronously. This function can be
[all …]
|
| /Zephyr-latest/dts/arm/nordic/ |
| D | nrf91_peripherals.dtsi | 152 * This i2c node can be either TWIM or TWIS, for the user to pick:
168 * This i2c node can be either TWIM or TWIS, for the user to pick:
184 * This i2c node can be either TWIM or TWIS, for the user to pick:
200 * This i2c node can be either TWIM or TWIS, for the user to pick:
216 * This spi node can be either SPIM or SPIS, for the user to pick:
232 * This spi node can be either SPIM or SPIS, for the user to pick:
248 * This spi node can be either SPIM or SPIS, for the user to pick:
264 * This spi node can be either SPIM or SPIS, for the user to pick:
|
| /Zephyr-latest/boards/weact/mini_stm32h743/doc/ |
| D | index.rst | 27 More information about the board can be found on the `Mini_STM32H743 website`_.
65 More information about STM32H743 can be found here:
100 The STM32H743VI System Clock can be driven by an internal or external oscillator,
116 pins for the Serial Wire Debug (SWD) interface, which can be used to connect
129 bootloader mode and present itself as a USB DFU Mode device. You can program
161 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
180 You can build and flash the examples to make sure Zephyr is running correctly on
181 your board. The LED definitions can be found in
|
| /Zephyr-latest/boards/u-blox/ubx_evkninab4/doc/ |
| D | index.rst | 33 More information about the NINA-B4 module and the EVK-NINA-B4 can be
105 modules share the same pinout and can be interchanged, see
111 Applications for the ``ubx_evkninab4/nrf52833`` board configuration can be
154 You can build and flash the examples to make sure Zephyr is running
155 correctly on your board. The button and LED definitions can be found in
165 The following approach can be used when an application needs to use
211 Pins can be configured in the board pinctrl file. To see the available mappings,
214 can only be used in under-10KHz applications. They are not suitable for 115200 speed of UART.
|
1...<<11121314151617181920>>...100
