# ch341par_linux

**Repository Path**: YK_Chen/ch341par_linux

## Basic Information

- **Project Name**: ch341par_linux
- **Description**: ch347/ch341 linux SDK

This directory contains 3 parts, usb device driver, application library and examples. This driver and applications support usb bus interface chip ch347 and ch341
- **Primary Language**: C
- **License**: Not specified
- **Default Branch**: main
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 1
- **Created**: 2025-06-16
- **Last Updated**: 2025-06-16

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# ch347/ch341 linux SDK

## Description

This directory contains 3 parts, usb device driver, application library and examples. This driver and applications support usb bus interface chip ch347 and ch341, ch347 implements high-speed usb to uart/jtag/swd/spi/i2c/gpio/etc., ch341 implements full-speed usb to uart/spi/i2c/gpio/parport/etc. This driver is not applicable to uart.

## Driver Operating Overview

1. Open "Terminal"
2. Switch to "driver" directory
3. Compile the driver using "make", you will see the module "ch34x_pis.ko" if successful
4. Type "sudo make load" or "sudo insmod ch34x_pis.ko" to load the driver dynamically
5. Type "sudo make unload" or "sudo rmmod ch34x_pis.ko" to unload the driver
6. Type "sudo make install" to make the driver work permanently
7. Type "sudo make uninstall" to remove the driver

Before the driver works, you should make sure that the ch347/ch341 device has been plugged in and is working properly, you can use shell command "lsusb" or "dmesg" to confirm that, VID of ch347/ch341 is [0x1A86].

If ch347/ch341 device works well, the driver will created devices named "ch34x_pis*" in /dev directory.

## Application Operating Overview

1. Copy the dynamic library in "lib" directory to system default library path: "sudo cp libch347.so /usr/lib"
2. Switch to "demo" directory
3. Type "gcc ch347_demo.c -o app -lch347" to compile the demo

## Note

**ch347f supports 2 modes:**

​	mode0: [uart * 2 + spi + i2c + jtag] in vcp driver mode, the devices are named /dev/ch34x_pis* and /dev/tty*

​	mode1: [uart * 2 + spi + i2c] in hid driver mode, the devices are named /dev/hidraw* 

**ch347t supports 4 modes:**

​	mode0: [uart * 2] in vcp/cdc driver mode, the devices are named /dev/tty*

​	mode1: [spi + i2c + uart * 1] in vcp driver mode, the devices are named /dev/ch34x_pis* and /dev/tty*

​	mode2: [spi + i2c + uart * 1] in hid driver mode, the devices are named /dev/hidraw*

​	mode3: [jtag + uart * 1] in vcp driver mode, the devices are named /dev/ch34x_pis* and /dev/tty*

**ch341 supports 3 modes:**

​	mode0: [uart]

​	mode1: [spi + i2c + parallel + gpio]

​	mode2: [printer]

This driver can be used with **ch347f**, **ch347t mode1/mode3** or **ch341 mode1**.

This application library and examples can be used with all modes.

Any question, you can send feedback to mail: tech@wch.cn