Searched full:shown (Results 1 – 25 of 171) sorted by relevance
1234567
/Zephyr-Core-3.7.0/doc/hardware/peripherals/can/ |
D | shell.rst | 62 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/ |
D | README.rst | 31 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/ |
D | renesas,rzt2m-pinctrl.yaml | 17 'pinctrl' node, as shown in this example: 42 As shown, pin configurations are organized in groups within each child node.
|
D | ambiq,apollo4-pinctrl.yaml | 17 'pinctrl' node, as shown in this example: 42 As shown, pin configurations are organized in groups within each child node.
|
D | silabs,gecko-pinctrl.yaml | 18 'pinctrl' node, as shown in this example: 44 As shown, pin configurations are organized in groups within each child node.
|
D | renesas,ra8-pinctrl.yaml | 17 'pinctrl' node, as shown in this example: 45 As shown, pin configurations are organized in groups within each child node.
|
D | renesas,smartbond-pinctrl.yaml | 17 'pinctrl' node, as shown in this example: 47 As shown, pin configurations are organized in groups within each child node.
|
D | atmel,sam-pinctrl.yaml | 21 node, as shown in this example: 52 As shown, pin configurations are organized in groups within each child node.
|
D | ti,cc32xx-pinctrl.yaml | 18 'pinctrl' node, as shown in this example: 48 As shown, pin configurations are organized in groups within each child node.
|
D | atmel,sam0-pinctrl.yaml | 21 node, as shown in this example: 52 As shown, pin configurations are organized in groups within each child node.
|
D | raspberrypi,pico-pinctrl.yaml | 18 'pinctrl' node, as shown in this example: 49 As shown, pin configurations are organized in groups within each child node.
|
D | gd,gd32-pinctrl-af.yaml | 18 'pinctrl' node, as shown in this example: 59 As shown, pin configurations are organized in groups within each child node.
|
D | ambiq,apollo3-pinctrl.yaml | 17 'pinctrl' node, as shown in this example: 42 As shown, pin configurations are organized in groups within each child node.
|
D | nordic,nrf-pinctrl.yaml | 18 '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/ |
D | menuconfig.rst | 73 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/ |
D | Kconfig.microbit | 15 int "Maximum length of strings that can be shown on the display"
|
/Zephyr-Core-3.7.0/samples/boards/mec15xxevb_assy6853/power_management/ |
D | README.rst | 32 note:: The values shown above might differ.
|
/Zephyr-Core-3.7.0/dts/bindings/pwm/ |
D | st,stm32-pwm.yaml | 30 the following complementary PWMs(CH2&CH2N) are shown below.
|
/Zephyr-Core-3.7.0/subsys/testsuite/ztest/ |
D | Kconfig | 179 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/ |
D | README.rst | 17 (for example as shown in this
|
/Zephyr-Core-3.7.0/scripts/dts/python-devicetree/src/devicetree/ |
D | _private.py | 19 # 'size_hint' is a string shown on errors that gives a hint on how
|
/Zephyr-Core-3.7.0/samples/boards/stm32/backup_sram/ |
D | README.rst | 14 VBAT is preserved, the incremented value will be shown on the next power-cycle.
|
/Zephyr-Core-3.7.0/doc/hardware/peripherals/sensor/ |
D | device_tree.rst | 15 /* SPI bus options here, not shown */
|
/Zephyr-Core-3.7.0/samples/bluetooth/st_ble_sensor/ |
D | README.rst | 27 To connect click on the device shown in the Device List.
|
/Zephyr-Core-3.7.0/samples/net/dhcpv4_client/ |
D | README.rst | 82 are shown like this: 174 are shown like this: 215 are shown like this:
|
1234567