设备通过USB插入Host环境,通常可枚举出tty设备,如果没有出现,需要对模块进行驱动的安装。可通过Host代码直接访问这些设备
当我们想调试一些SPI、I2C接口的传感器或者模块,可通过CH341 A/B模块作中转,它可通过USB接口将SPI/IIC数据在设备与Host之间进行传输,通过其驱动可在Host环境下注册SPI/IIC字符设备
CH341转SPI
模块上有跳帽可以切换3.3V/5V,切换SPI+I2C/UART
USB转SPI驱动
驱动参考 https://github.com/gschorcht/spi-ch341-usb
git clone https://github.com/gschorcht/spi-ch341-usb.git
cd spi-ch341-usb
make
sudo make install
不将驱动安装到内核的话,可以在需要时手动加载驱动。
加载前先将CH341转串口和转I2C的驱动卸载,CH341转串口、转I2C、转SPI的驱动相互冲突
sudo rmmod ch341 #需要先卸载ch341,才能卸载usbserial
sudo rmmod usbserial
sudo rmmod i2c_ch341_usb
将仓库目录下的spi-ch341-usb.ko加载:
sudo insmod spi-ch341-usb.ko
设备1模块切换到SPI+I2C模式,插到主机USB上,此时通过 lsmod 可以看到spidev0.0/1/2,其中spidev0.x表示是SPI0总线上的设备,x用于区分各个从机(即通信时使能设备1上的CS0/1/2脚)。
电脑重启后需要重新加载spi-ch341-usb.ko
驱动参考 https://github.com/gschorcht/i2c-ch341-usb
git clone https://github.com/gschorcht/i2c-ch341-usb.git
cd i2c-ch341-usb
make
sudo make install
不将驱动安装到内核的话,可以在需要时手动加载驱动。
加载前先将CH341转串口和转SPI的驱动卸载,CH341转串口、转I2C、转SPI的驱动相互冲突:
sudo rmmod ch341 #需要先卸载ch341,才能卸载usbserial
sudo rmmod usbserial
sudo rmmod spidev
sudo rmmod spi_ch341_usb
将仓库目录下的i2c-ch341-usb.ko加载:
sudo insmod i2c-ch341-usb.ko
设备1模块切换到SPI+I2C模式,插到主机USB上,此时通过 lsmod 可以看到i2c_ch341_usb,通过 ls /dev 可以看到i2c-x,其中x根据原有的i2c设备编号而有所变化。
电脑重启后需要重新加载i2c-ch341-usb.ko。
如果insmod提示.ko文件invalid format,可能是linux内核版本更新了,需要重新编译。
当插入的设备可接收AT命令时,可通过如下程序向tty设备发送AT\r,读取到OK。
#include
#include
#include
#include
#include
#include
#include int main(int argc, char *argv[])
{struct termios opt;char cmd[] = "AT\r";int fd;int ret;/* Switch TTY to raw mode */memset(&opt, 0, sizeof(opt));cfmakeraw(&opt);errno = 0;fd = open("/dev/ttyUSB0", O_RDWR | O_NOCTTY);if (fd < 0)return -1;tcflush(fd, TCIOFLUSH);tcsetattr(fd, TCSANOW, &opt);write(fd, cmd, strlen(cmd));read(fd, buf, sizeof(buf));close(fd);
}
在Linux中编写应用程序测试SPI的可用性,可以使用类似如下代码,读取一个某个开发板/器件/模块的ID等寄存器验证:
#include
#include
#include
#include
#include
#include
#include
....../* path of spi dev,note the x of spidev0.x, must correspond to the CSx */
#define SPI_DEV "/dev/spidev0.1"
......int main( int argc, char *argv[] )
{....../* open the spi device */int handle_spi = 0;handle_spi = open(SPI_DEV, O_RDWR);/* since tx and rx will complete at the same time,one may use 1 message (the struct below) with rxbuf and txbuf,or may use 2 messages with txbuf and rxbuf respectively -- message 1 for tx first and message 2 for rx later, with a interval between 2 messages */struct spi_ioc_transfer spi_trans = {.tx_buf = (unsigned long)txbuf,.rx_buf = (unsigned long)rxbuf,.len = len, /* length of transmitted data */.delay_usecs = 0, /* interval between SPI_IOC_MESSAGEs */ */ .speed_hz = 1400000, /* unavailable for CH341 */.bits_per_word = 8, /* unavailabel for CH341 */};/* set SPI mode, unavailable for CH341*/ unsigned char mode = SPI_MODE_0;ret = ioctl(handle_spi, SPI_IOC_WR_MODE, &mode);/* transmit data through SPI device. The desired data is ready to read in rxbuf when transmitting completed*/ret = ioctl(handle_spi, SPI_IOC_MESSAGE(1), &spi_trans);/* close the spi device*/close(handle_spi);......
}
在Linux中编写应用程序测试I2C的可用性,可以使用类似如下代码,读取一个某个开发板/器件/模块的ID等寄存器验证
#include
#include
#include
#include
#include
#include
#include
#include
....../* path of i2c device */
#define I2C_DEV "/dev/i2c-7"/* address of the slave to communicate, in 7bit format, not left-shifted*/
#define SLAVE_ADDR 0x6C
......int main( int argc, char *argv[] )
{....../* open i2c device */int handle_i2c = 0;handle_i2c = open(I2C_DEV, O_RDWR);/* config the slave address */ret = ioctl(handle_i2c, I2C_SLAVE, SLAVE_ADDR);/* transmit data through i2c,slave addr and nW bit will be send first automatically */ret = write(i2c_fd, txbuf, tx_count);/* read data from i2c,slave addr and R bit will be send first automatically */ ret = read(i2c_fd, rxbuf, rx_count);/* close i2c device */close(handle_i2c);......
}