<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[USB driver for Raspberry Pi]]></title><description><![CDATA[<p dir="auto">Hi there,<br />
I'm trying to have the M5Stack products communicating by USB with my Raspberry PI.<br />
I've tried using the source package from <a href="https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/drivers/CP210x_VCP_Linux.zip" target="_blank" rel="noopener noreferrer nofollow ugc">https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/drivers/CP210x_VCP_Linux.zip</a>.<br />
I unzip the file, I have a .tar.gz file, I gaip -d it, got a tar. When doing a tar xvf on it, I have some error messages (tar: Ignoring unknown extended header keyword 'SCHILY.dev' for instance).<br />
I have only few files, including a Makefile, but when I run the make command, I have :<br />
make -C /lib/modules/<code>uname -r</code>/build M=/home/pi/Downloads/toto modules<br />
make[1]: *** /lib/modules/4.19.66-v7+/build: No such file or directory.  Stop.<br />
Makefile:7: recipe for target 'all' failed<br />
make: *** [all] Error 2</p>
<p dir="auto">I've also tried directly connected my M5Stack device, but I have the following lines in my /var/log/messages, and there's not serial port available:<br />
Jul 28 08:47:56 raspberrypi kernel: [61085.228222] usb 1-1.2: new full-speed USB device number 11 using dwc_otg<br />
Jul 28 08:47:57 raspberrypi kernel: [61086.098232] usb 1-1.2: new full-speed USB device number 12 using dwc_otg<br />
Jul 28 08:47:57 raspberrypi kernel: [61086.232479] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 5.00<br />
Jul 28 08:47:57 raspberrypi kernel: [61086.232503] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br />
Jul 28 08:47:57 raspberrypi kernel: [61086.232516] usb 1-1.2: Product: M5stack<br />
Jul 28 08:47:57 raspberrypi kernel: [61086.232528] usb 1-1.2: Manufacturer: Hades2001<br />
Jul 28 08:47:57 raspberrypi kernel: [61086.232539] usb 1-1.2: SerialNumber: 7152FA2E93<br />
Jul 28 08:47:57 raspberrypi kernel: [61086.234008] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected<br />
Jul 28 08:47:57 raspberrypi kernel: [61086.234353] usb 1-1.2: Detected FT232BM<br />
Jul 28 08:47:57 raspberrypi kernel: [61086.235408] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0<br />
Jul 28 08:47:57 raspberrypi mtp-probe: checking bus 1, device 12: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2"<br />
Jul 28 08:47:57 raspberrypi mtp-probe: bus: 1, device: 12 was not an MTP device<br />
Jul 28 08:47:58 raspberrypi kernel: [61086.473162] usb 1-1.2: USB disconnect, device number 12<br />
Jul 28 08:47:58 raspberrypi kernel: [61086.474080] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0<br />
Jul 28 08:47:58 raspberrypi kernel: [61086.474251] ftdi_sio 1-1.2:1.0: device disconnected<br />
How can we have the USB communication working with the Raspberry Pi ?</p>
]]></description><link>https://community.m5stack.com/topic/2164/usb-driver-for-raspberry-pi</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 04:00:21 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/2164.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 28 Jul 2020 08:23:37 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to USB driver for Raspberry Pi on Thu, 30 Jul 2020 04:53:41 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/funkyfab" aria-label="Profile: funkyfab">@<bdi>funkyfab</bdi></a> said in <a href="/post/9487">USB driver for Raspberry Pi</a>:</p>
<blockquote>
<p dir="auto">I'll answer myself ;-)<br />
I copied the /lib/udev/rules.d/69-libmtp.rules to /etc/udev/rules.d,  added the line<br />
ATTR{idVendor}=="0403", ATTR{idProduct}=="6001", GOTO="libmtp_rules_end"<br />
That prevents the M5 devices to be recognized as MTP devices.<br />
Then they're recognized as Serial ports, and Arduino IDE can access them.</p>
<p dir="auto">So we don't need the driver, just a change in udev configuration.</p>
</blockquote>
<p dir="auto">Oh cool, thats for working out how to do this. I can continue my plans of adding an RPI to my project bench to programme the M5Stacks and Sticks.<br />
Thanks you.</p>
]]></description><link>https://community.m5stack.com/post/9500</link><guid isPermaLink="true">https://community.m5stack.com/post/9500</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Thu, 30 Jul 2020 04:53:41 GMT</pubDate></item><item><title><![CDATA[Reply to USB driver for Raspberry Pi on Wed, 29 Jul 2020 09:04:32 GMT]]></title><description><![CDATA[<p dir="auto">I'll answer myself ;-)<br />
I copied the /lib/udev/rules.d/69-libmtp.rules to /etc/udev/rules.d,  added the line<br />
ATTR{idVendor}=="0403", ATTR{idProduct}=="6001", GOTO="libmtp_rules_end"<br />
That prevents the M5 devices to be recognized as MTP devices.<br />
Then they're recognized as Serial ports, and Arduino IDE can access them.</p>
<p dir="auto">So we don't need the driver, just a change in udev configuration.</p>
]]></description><link>https://community.m5stack.com/post/9487</link><guid isPermaLink="true">https://community.m5stack.com/post/9487</guid><dc:creator><![CDATA[FunkyFab]]></dc:creator><pubDate>Wed, 29 Jul 2020 09:04:32 GMT</pubDate></item></channel></rss>