Home
last modified time | relevance | path

Searched full:shown (Results 1 – 25 of 171) sorted by relevance

1234567

/Zephyr-Core-3.7.0/doc/hardware/peripherals/can/
Dshell.rst62 The properties of a given CAN controller can be inspected using the ``can show`` subcommand as shown
111 subcommand as shown below. The bitrate is specified in bits per second.
119 the ``can dbitrate`` subcommand as shown below. The bitrate is specified in bits per second.
138 subcommand. An example for enabling loopback mode is shown below.
153 ``can start`` subcommand as shown below. This will enable reception and transmission of CAN frames.
161 stop`` subcommand as shown below:
172 added using the ``can filter add`` subcommand as shown below. The subcommand accepts a CAN ID in
185 Received CAN frames matching the added filter(s) are printed to the shell. A few examples are shown
233 Configured CAN RX filters can be removed again using the ``can filter remove`` subcommand as shown
245 CAN frames can be queued for transmission using the ``can send`` subcommand as shown below. The
[all …]
/Zephyr-Core-3.7.0/samples/boards/reel_board/mesh_badge/
DREADME.rst31 characteristic. The passkey for the pairing will be shown on the board's
50 #. Wait until "Resetting Device" is shown
/Zephyr-Core-3.7.0/dts/bindings/pinctrl/
Drenesas,rzt2m-pinctrl.yaml17 'pinctrl' node, as shown in this example:
42 As shown, pin configurations are organized in groups within each child node.
Dambiq,apollo4-pinctrl.yaml17 'pinctrl' node, as shown in this example:
42 As shown, pin configurations are organized in groups within each child node.
Dsilabs,gecko-pinctrl.yaml18 'pinctrl' node, as shown in this example:
44 As shown, pin configurations are organized in groups within each child node.
Drenesas,ra8-pinctrl.yaml17 'pinctrl' node, as shown in this example:
45 As shown, pin configurations are organized in groups within each child node.
Drenesas,smartbond-pinctrl.yaml17 'pinctrl' node, as shown in this example:
47 As shown, pin configurations are organized in groups within each child node.
Datmel,sam-pinctrl.yaml21 node, as shown in this example:
52 As shown, pin configurations are organized in groups within each child node.
Dti,cc32xx-pinctrl.yaml18 'pinctrl' node, as shown in this example:
48 As shown, pin configurations are organized in groups within each child node.
Datmel,sam0-pinctrl.yaml21 node, as shown in this example:
52 As shown, pin configurations are organized in groups within each child node.
Draspberrypi,pico-pinctrl.yaml18 'pinctrl' node, as shown in this example:
49 As shown, pin configurations are organized in groups within each child node.
Dgd,gd32-pinctrl-af.yaml18 'pinctrl' node, as shown in this example:
59 As shown, pin configurations are organized in groups within each child node.
Dambiq,apollo3-pinctrl.yaml17 'pinctrl' node, as shown in this example:
42 As shown, pin configurations are organized in groups within each child node.
Dnordic,nrf-pinctrl.yaml18 'pinctrl' node, as shown in this example:
46 As shown, pin configurations are organized in groups within each child node.
/Zephyr-Core-3.7.0/doc/build/kconfig/
Dmenuconfig.rst73 The two interfaces are shown below:
103 Boolean configuration options are shown with :guilabel:`[ ]` brackets,
104 while numeric and string-valued configuration symbols are shown with
105 :guilabel:`( )` brackets. Symbol values that can't be changed are shown as
/Zephyr-Core-3.7.0/drivers/display/
DKconfig.microbit15 int "Maximum length of strings that can be shown on the display"
/Zephyr-Core-3.7.0/samples/boards/mec15xxevb_assy6853/power_management/
DREADME.rst32 note:: The values shown above might differ.
/Zephyr-Core-3.7.0/dts/bindings/pwm/
Dst,stm32-pwm.yaml30 the following complementary PWMs(CH2&CH2N) are shown below.
/Zephyr-Core-3.7.0/subsys/testsuite/ztest/
DKconfig179 This option controls whether test output is shown verbosely or
186 This option controls whether suite summary is shown verbosely or
195 result will be shown as a failure in order to increase visibility. This precludes tests
/Zephyr-Core-3.7.0/samples/sensor/apds9960/
DREADME.rst17 (for example as shown in this
/Zephyr-Core-3.7.0/scripts/dts/python-devicetree/src/devicetree/
D_private.py19 # 'size_hint' is a string shown on errors that gives a hint on how
/Zephyr-Core-3.7.0/samples/boards/stm32/backup_sram/
DREADME.rst14 VBAT is preserved, the incremented value will be shown on the next power-cycle.
/Zephyr-Core-3.7.0/doc/hardware/peripherals/sensor/
Ddevice_tree.rst15 /* SPI bus options here, not shown */
/Zephyr-Core-3.7.0/samples/bluetooth/st_ble_sensor/
DREADME.rst27 To connect click on the device shown in the Device List.
/Zephyr-Core-3.7.0/samples/net/dhcpv4_client/
DREADME.rst82 are shown like this:
174 are shown like this:
215 are shown like this:

1234567