Searched refs:can (Results 51 – 75 of 2493) sorted by relevance
12345678910>>...100
| /Zephyr-latest/drivers/i2c/ |
| D | Kconfig.it8xxx2 | 20 This is an option to enable FIFO mode which can reduce
25 I2C FIFO mode of it8xxx2 can support I2C APIs including:
36 This option can enable the enhance I2C
46 This is an option to enable command queue mode which can
49 I2C command queue mode of it8xxx2 can support I2C APIs
|
| /Zephyr-latest/samples/boards/st/power_mgmt/blinky/ |
| D | README.rst | 13 When setting a prescaler to decrease the lptimer input clock frequency, the system can sleep
16 prescaler of <32>, then the kernel sleep period can reach 65536 * 32/32768 = 64 seconds
25 it should support a clock source alternative to Cortex Systick that can be used
41 of low power can be tested.
48 enabled, but user can also deactivate one or the other to see each configuration
|
| /Zephyr-latest/boards/ezurio/bl654_sensor_board/doc/ |
| D | bl654_sensor_board.rst | 33 More information about the BL654 module can be found on the `BL654 website`_,
34 more information about the USB-SWD Programmer can be found on the
67 More information about the Bosch BME280 sensor can be found on the
73 The sensor can be powered directly from a coin cell or from a voltage supplied
86 Applications for the ``bl654_sensor_board`` board configuration can be built,
89 debugger/programmer is required which can be connected to using a Tag-Connect
91 programmer can be used to program and debug the BL654 sensor board.
98 can be found in :ref:`nordic_segger_flashing`. Then build and flash applications
108 can be plugged in to the UART header. An FTDI cable can also be used - the
135 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
[all …]
|
| /Zephyr-latest/dts/arm/atmel/ |
| D | samc21.dtsi | 57 can0: can@42001c00 {
58 compatible = "atmel,sam0-can";
72 can1: can@42002000 {
73 compatible = "atmel,sam0-can";
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | index.rst | 6 The Zephyr kernel and subsystems can be configured at build time to adapt them
13 configurations are valid. Symbols can be grouped into menus and sub-menus to
17 can be tested at build time. Code for unused features can be compiled out to
|
| /Zephyr-latest/samples/arch/smp/pi/ |
| D | README.rst | 10 when compute-intensive tasks can be run in parallel, with
14 can see that using more cores takes almost linearly less time
17 You can also edit the sample source code to change the
25 required for all the calculation to be done. It can be built and executed
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | ptp_time.rst | 14 The PTP time struct can store time information in high precision
15 format (nanoseconds). The extended timestamp format can store the
|
| /Zephyr-latest/boards/96boards/neonkey/doc/ |
| D | index.rst | 19 family products. It can also be used as a standalone board.
75 More details about the board can be found at `96Boards website`_.
77 The default board configuration can be found in
100 96Boards Neonkey can be driven by an internal oscillator as well as the main
148 96Boards Neonkey can be flashed by two methods, one using the ROM
155 ROM bootloader can be triggered by the following pattern:
161 More detailed information on activating the ROM bootloader can be found in
165 For flashing, `stm32flash`_ command line utility can be used. The following
183 Use the `Black Magic Debug Probe`_ as an SWD programmer, which can
191 ARM Embedded, can be used as well.
[all …]
|
| /Zephyr-latest/doc/services/pm/ |
| D | power_domain.rst | 52 Most of the devices in an SoC have independent power control that can
54 significant amount of static current leakage that can't be controlled
57 are generally used together, so that an unused region can be
59 called "power domains", can be present in a hierarchy and can be
65 Devices external to a SoC can be powered from sources other than the main power
67 or a dedicated power IC. Multiple devices can be powered from the same source,
70 Placing devices on power domains can be done for a variety of reasons,
125 Devices belonging to this device can be declared referring it in the
145 callback and can be used by them to do any additional work required.
146 They can safely be ignored though.
|
| /Zephyr-latest/boards/96boards/wistrio/doc/ |
| D | 96b_wistrio.rst | 73 The default board configuration can be found in
106 I2C1 also goes to the J22 connector and can be used to attach external
126 96Boards WisTrio can be flashed by two methods, one using the ROM
131 which can be triggered by using the BOOT0 pin. The ROM bootloader supports
133 You can read more about how to enable and use the ROM bootloader by
142 2. ROM bootloader can be triggered by the following pattern:
147 More detailed information on activating the ROM bootloader can be found in
161 Use the `Black Magic Debug Probe`_ as an SWD programmer, which can
169 ARM Embedded, can be used as well.
184 After flashing 96Boards WisTrio, it can be debugged using the same
[all …]
|
| /Zephyr-latest/drivers/watchdog/ |
| D | Kconfig.smartbond | 22 reset at <= -16. Timer can be frozen/resumed using
26 reset at value 0 and can not be frozen by Software.
27 Note that this bit can only be set to 1 by SW and
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | cfg.rst | 12 Configuration Client can communicate with to change the node configuration. In some
13 cases, the mesh node can't rely on the Configuration Client to detect or determine
15 scenarios, this API can be used to change the configuration locally.
|
| /Zephyr-latest/tests/arch/arm/arm_irq_vector_table/ |
| D | README.txt | 5 Verify a project can install ISRs directly in the vector table. Only for
12 This project outputs to the console. It can be built and executed on QEMU as
21 Problems caused by out-dated project information can be addressed by
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
| D | gap.rst | 16 can then use it by selecting it with its ID :code:`bt id-select <id>`. Finally, you can list all the
26 Here is an example of what you can expect:
43 As you can see, this can lead to a high number of results. To reduce that number and easily find a
44 specific device, you can enable scan filters. There are four types of filters: by name, by RSSI, by
46 command followed by the type of filters. You can add multiple filters by using the commands again.
67 You can use the command :code:`bt scan on` to create an *active* scanner, meaning that the scanner
69 can create a *passive scanner* by using the :code:`bt scan passive` command, so the scanner will not
91 You can list the active connections of the shell using the :code:`bt connections` command. The shell
92 maximum number of connections is defined by :kconfig:option:`CONFIG_BT_MAX_CONN`. You can disconnect
98 If you were scanning just before, you can connect to the last scanned device by
[all …]
|
| /Zephyr-latest/doc/services/debugging/ |
| D | mipi_stp_decoder.rst | 6 The MIPI System Trace Protocol (MIPI STP) was developed as a generic base protocol that can
17 This module can be used to perform on-chip decoding of the data stream. STP v2 is used.
23 Decoder has internal state since there are dependency between opcodes (e.g. timestamp can be
24 relative). Decoder can be in synchronization or not. Initial state is configurable.
26 Loss of synchronization can be indicated to the decoder by calling
|
| /Zephyr-latest/doc/develop/manifest/external/ |
| D | cannectivity.rst | 14 `python-can`_, and by many other software packages.
41 Once CANnectivity is added as a Zephyr module, the "gs_usb" implementation can be reused outside of
54 …https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/can/usb/gs_usb…
56 .. _python-can:
57 https://python-can.readthedocs.io/en/stable/interfaces/gs_usb.html
|
| /Zephyr-latest/samples/drivers/can/babbling/ |
| D | README.rst | 1 .. zephyr:code-sample:: can-babbling
21 The source code for this sample application can be found at:
22 :zephyr_file:`samples/drivers/can/babbling`.
40 :zephyr-app: samples/drivers/can/babbling
50 babbling on can@40024000 with standard (11-bit) CAN ID 0x010, RTR 0, CAN FD 0
|
| /Zephyr-latest/boards/others/candlelightfd/ |
| D | candlelightfd_stm32g0b1xx_dual.dts | 15 transceiver1: can-phy1 {
16 compatible = "nxp,tja1051", "can-transceiver-gpio";
|
| /Zephyr-latest/boards/shields/x_nucleo_eeprma2/ |
| D | x_nucleo_eeprma2.overlay | 30 /* if solder-bridge closed: arduino A1 pin on CN8 can wp */
43 /* if solder-bridge closed: arduino A1 pin on CN8 can wp */
56 /* if solder-bridge closed: arduino A1 pin on CN8 can wp */
78 * resistor. Where they can either be torn to VCC or GND.
93 /* if solder-bridge closed: arduino A0 pin on CN8 can wp */
107 /* if solder-bridge closed: arduino A0 pin on CN8 can wp */
122 /* if solder-bridge closed: arduino A0 pin on CN8 can wp */
|
| /Zephyr-latest/doc/develop/west/ |
| D | sign.rst | 6 The ``west sign`` :ref:`extension <west-extensions>` command can be used to
24 all these layers can causes issues typical when the layers don't abstract
26 whitespace or other special characters through all the wrappers can be
28 can be very time-consuming: it requires at least enabling and searching verbose
30 build logs can be unreliable: it may produce different results because of subtle
34 To avoid these issues, ``rimage`` parameters can bet set in ``west config``.
45 # Not needed when rimage can be found in the default PATH
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_handlers.rst | 15 protocol and header. There can only be one registered group per unique ID.
20 MCUmgr handlers can be added externally by application code or by module code, they do not have
42 The purpose of the header file is to provide defines which can be used by the MCUmgr handler
57 header file (as upstream Zephyr has) can be used to distribute group IDs more easily.
62 The purpose of the header file is to provide defines which can be used by the MCUmgr handler
70 This sets up a single event which application (or module) code can register for to receive a
75 central index header file (as upstream Zephyr has) can be used to distribute event IDs more
94 functionality can be found on :ref:`mcumgr_callbacks`.
103 The purpose of the Kconfig file is to provide options which users can enable or change relating
113 directories to add and specify options that can be changed. A basic file only need to include the
[all …]
|
| /Zephyr-latest/boards/renode/riscv32_virtual/doc/ |
| D | index.rst | 7 Contrary to QEMU, the peripherals of this platform can be easily configured by editing the
17 Applications for the ``riscv32_virtual`` board configuration can be built as usual
27 While this board is emulated and you can't "flash" it, you can use this
|
| /Zephyr-latest/doc/develop/optimizations/ |
| D | footprint.rst | 33 Some peripherals are enabled by default. You can disable unused
47 This option can be disabled to save a few bytes.
50 This option can be enabled for debug builds.
58 Depending on your application and platform needs, you can disable MPU/MMU
|
| /Zephyr-latest/boards/native/nrf_bsim/ |
| D | Kconfig | 12 Will produce a console Linux process which can be executed natively.
23 Will produce a console Linux process which can be executed natively.
34 Will produce a console Linux process which can be executed natively.
45 Will produce a console Linux process which can be executed natively.
63 # which use BabbleSim. When that happens, we can move this to a common
99 # Let's reuse the RTC sync options so applications which use it can be reused as is
|
| /Zephyr-latest/samples/subsys/edac/ |
| D | README.rst | 15 This sample can be found under :zephyr_file:`samples/subsys/edac` in the
17 The sample can be built as follows for the :ref:`intel_ehl_crb` board:
26 The Zephyr image that's created can be run on the :ref:`intel_ehl_crb` board
36 After the application has started help can be read with the following
49 Help for subcommand info can be read with:
60 Injection help can be received with:
|
12345678910>>...100
