Home
last modified time | relevance | path

Searched refs:PC (Results 1 – 25 of 171) sorted by relevance

1234567

/Zephyr-latest/include/zephyr/dt-bindings/pinctrl/
Dch32v003-pinctrl.h42 #define TIM1_ETR_PC5_0 CH32V003_PINMUX_DEFINE(PC, 5, TIM1, 0)
43 #define TIM1_ETR_PC5_1 CH32V003_PINMUX_DEFINE(PC, 5, TIM1, 1)
45 #define TIM1_ETR_PC2_3 CH32V003_PINMUX_DEFINE(PC, 2, TIM1, 3)
47 #define TIM1_CH1_PC6_1 CH32V003_PINMUX_DEFINE(PC, 6, TIM1, 1)
49 #define TIM1_CH1_PC4_3 CH32V003_PINMUX_DEFINE(PC, 4, TIM1, 3)
51 #define TIM1_CH2_PC7_1 CH32V003_PINMUX_DEFINE(PC, 7, TIM1, 1)
53 #define TIM1_CH2_PC7_3 CH32V003_PINMUX_DEFINE(PC, 7, TIM1, 3)
54 #define TIM1_CH3_PC3_0 CH32V003_PINMUX_DEFINE(PC, 3, TIM1, 0)
55 #define TIM1_CH3_PC0_1 CH32V003_PINMUX_DEFINE(PC, 0, TIM1, 1)
56 #define TIM1_CH3_PC3_2 CH32V003_PINMUX_DEFINE(PC, 3, TIM1, 2)
[all …]
Dch32v20x_30x-pinctrl.h89 #define USART1_CTS_PC4_3 CH32V20X_V30X_PINMUX_DEFINE(PC, 4, USART1, 3)
93 #define USART1_RTS_PC5_3 CH32V20X_V30X_PINMUX_DEFINE(PC, 5, USART1, 3)
107 #define USART3_CK_PC12_1 CH32V20X_V30X_PINMUX_DEFINE(PC, 12, USART3, 1)
111 #define USART3_TX_PC10_1 CH32V20X_V30X_PINMUX_DEFINE(PC, 10, USART3, 1)
115 #define USART3_RX_PC11_1 CH32V20X_V30X_PINMUX_DEFINE(PC, 11, USART3, 1)
138 #define USART5_TX_PC12_0 CH32V20X_V30X_PINMUX_DEFINE(PC, 12, USART5, 0)
145 #define USART6_TX_PC0_0 CH32V20X_V30X_PINMUX_DEFINE(PC, 0, USART6, 0)
148 #define USART6_RX_PC1_0 CH32V20X_V30X_PINMUX_DEFINE(PC, 1, USART6, 0)
152 #define USART7_TX_PC2_0 CH32V20X_V30X_PINMUX_DEFINE(PC, 2, USART7, 0)
155 #define USART7_RX_PC3_0 CH32V20X_V30X_PINMUX_DEFINE(PC, 3, USART7, 0)
[all …]
/Zephyr-latest/samples/boards/st/bluetooth/interactive_gui/
DREADME.rst11 Expose the Bluetooth network coprocessor via UART to a PC to be used
13 and it passes the data between the host (PC) and controller.
19 * `BlueNRG GUI`_ application installed on your PC
/Zephyr-latest/scripts/coredump/gdbstubs/arch/
Dxtensa.py278 PC = 0 variable in GdbRegDef_Sample_Controller.RegNum
312 PC = 0 variable in GdbRegDef_ESP32.RegNum
345 PC = 0 variable in GdbRegDef_ESP32S2.RegNum
374 PC = 0 variable in GdbRegDef_ESP32S3.RegNum
415 PC = 0 variable in GdbRegDef_Intel_Adsp_CAVS_Zephyr.RegNum
455 PC = 32 variable in GdbRegDef_Intel_Adsp_CAVS_XCC.RegNum
490 PC = 0 variable in GdbRegDef_DC233C.RegNum
Darm_cortex_m.py34 PC = 15 variable in RegNum
70 self.registers[RegNum.PC] = tu[6]
152 thread_registers[RegNum.PC] = tu[6]
Darm64.py50 PC = 32 # Program Counter (PC) variable in RegNum
104 self.registers[RegNum.PC] = tu[21]
Drisc_v.py49 PC = 32 variable in RegNum
95 self.registers[RegNum.PC] = tu[17]
/Zephyr-latest/tests/bluetooth/classic/sdp_c/
DREADME.rst10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
17 * The ``bumble`` library installed on the host PC.
18 The Bluetooth Classic controller on PC side is required. Refer to getting started of `bumble`_
39 On the host PC, a HCI transport needs to be required. Refer to `bumble platforms`_ page of
55 Running the test suite on hardware requires a HCI transport connected to the host PC.
/Zephyr-latest/arch/arm/core/
Dgdbstub.c28 unsigned int instr = sys_read32(ctx.registers[PC]); in is_bkpt()
69 ctx.registers[PC] = esf->basic.pc; in z_gdb_entry()
86 esf->basic.pc = ctx.registers[PC]; in z_gdb_entry()
119 uint32_t reg_val = ctx.registers[PC]; in arch_gdb_step()
/Zephyr-latest/soc/intel/lakemont/
DKconfig.defconfig15 # Target platforms are usually not PC-compatible
/Zephyr-latest/include/zephyr/arch/arm/
Dgdbstub.h54 PC, enumerator
/Zephyr-latest/boards/firefly/roc_rk3568_pc/
Droc_rk3568_pc.dts13 model = "Firefly ROC-RK3568-PC";
/Zephyr-latest/doc/hardware/peripherals/
Dps2.rst10 IBM's desktop PC line of the same name before
/Zephyr-latest/samples/net/sockets/echo_client/
DREADME.rst189 - Build ``echo-server`` for HOST PC (x86_64)
234 - Install the OTBR (OpenThread Border Router) docker container on your HOST PC (x86_64)
240 Linux PC
262 …:/64`` are the IPv6 addresses - On-Mesh - which allow accessing the OT devices) on HOST PC (x86_64)
296 On the HOST PC's webbrowser: http://localhost:8080/
321 In the HOST PC www webpage interface please:
331 This one can be accessed from HOST's PC network (via e.g.
334 Start ``echo-server`` on HOST PC (x86-64)
/Zephyr-latest/boards/qemu/x86/
DKconfig.defconfig68 # QEMU presents a PC-compatible machine
90 # QEMU presents a PC-compatible machine
/Zephyr-latest/soc/intel/intel_ish/
DKconfig.defconfig21 # Target platforms are not PC-compatible
/Zephyr-latest/tests/drivers/can/host/
DREADME.rst10 host PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
17 * The python-can library installed on the host PC.
18 * A CAN fixture creating a CAN bus between the host PC and the DUT.
52 On the host PC, a virtual SocketCAN interface needs to be created and brought up before running the
86 Running the test suite on hardware requires a physical CAN adapter connected to the host PC. The CAN
/Zephyr-latest/boards/others/serpente/doc/
Dindex.rst42 with a host PC. See the :zephyr:code-sample-category:`usb` sample applications for
44 to the host PC.
/Zephyr-latest/samples/subsys/modbus/tcp_server/
DREADME.rst21 on a PC or laptop.
40 On the client side, PC or laptop, the following command connects PyModbus
/Zephyr-latest/boards/96boards/argonkey/doc/
Dindex.rst172 flashing on a Linux PC using UART as communication channel.
174 1. Connect ArgonKey UART to your Linux PC using, for example, a USB-TTL serial
183 When the USB cable is inserted to the Linux PC the following device will be
205 is connected to the PC through USB, it presents itself as a USB composite
/Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/
DREADME.rst34 This broker can exist locally (e.g. on a host PC) or a publicly available MQTT broker
41 If using Ethernet, connect the board to the MQTT broker. This may be your host PC
103 - A DHCP server can be installed on the host PC to handle assigning an IP to the board
133 broker (i.e. IP address of Ethernet port on host PC). These addresses should be in the
135 - On your host PC, install Mosquitto.
/Zephyr-latest/boards/seeed/wio_terminal/doc/
Dindex.rst59 make the console available on PC as USB CDC class.
65 host PC. See the :zephyr:code-sample-category:`usb` sample applications for more, such as the
67 characters back to the host PC.
/Zephyr-latest/boards/st/sensortile_box/doc/
Dindex.rst63 on a smartphone/PC to implement applications such as:
109 available on PC.
110 - using the USB connector, which may be used to make the console available on PC as
118 SensorTile.box can be connected as a USB device to a PC host through its micro-B connector.
/Zephyr-latest/samples/subsys/usb/console-next/
DREADME.rst30 Plug the board into a host device, for sample, a PC running Linux OS.
/Zephyr-latest/samples/subsys/modbus/tcp_gateway/
DREADME.rst21 :zephyr:code-sample:`modbus-rtu-server` sample. Client is running on a PC or laptop.
44 On the client side, PC or laptop, the following command connects PyModbus

1234567