Jump to content

CH340 serial converter - missing /dev/ttyUSB0

N3u67wEeUt2

By N3u67wEeUt2
in Beginners

 Share
Go to solution Solved by N3u67wEeUt2,

Recommended Posts

N3u67wEeUt2

N3u67wEeUt2

Posted
Posted

Hi All,

 

I have a BPI-M2 ZERO, BANANA-PI-ZERO with SERIAL to USB plugged in.

 

It's being detected by 

lsusb
Bus 002 Device 005: ID 1a86:7523 QinHeng Electronics CH340 serial converter

but it doesn't appear under /dev/ttyUSB0

 

The problem is that I can't see it under /dev/ as /dev/ttyUSB0.

 

I haven't tried installing CH340 drivers yet. Should I use the ones for Ubuntu? Here is the tutorial I found but I'm not sure if those are the correct drivers: 

https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all

 

  

uname -a
Linux bananapim2zero 6.2.13-sunxi #1 SMP Wed Apr 26 12:30:09 UTC 2023 armv7l GNU/Linux

sudo lsusb
Bus 002 Device 006: ID 413c:2110 Dell Computer Corp. Dell Wired Multimedia Keyboard
Bus 002 Device 005: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Bus 002 Device 004: ID 413c:1010 Dell Computer Corp. USB 2.0 Hub [MTT]
Bus 002 Device 003: ID 05c6:f00e Qualcomm, Inc. Android
Bus 002 Device 002: ID 0a05:7211 Unknown Manufacturer hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

sudo lsusb -t -v
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    ID 1d6b:0001 Linux Foundation 1.1 root hub
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 12M
        ID 0a05:7211 Unknown Manufacturer hub
        |__ Port 2: Dev 3, If 0, Class=Wireless, Driver=rndis_host, 12M
            ID 05c6:f00e Qualcomm, Inc.
        |__ Port 2: Dev 3, If 1, Class=CDC Data, Driver=rndis_host, 12M
            ID 05c6:f00e Qualcomm, Inc.
        |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 12M
            ID 413c:1010 Dell Computer Corp.
            |__ Port 4: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
                ID 413c:2110 Dell Computer Corp.
            |__ Port 4: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
                ID 413c:2110 Dell Computer Corp.
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub

grep CH34 /boot/config-6.2.13-sunxi
CONFIG_USB_SERIAL_CH341=m

ls /dev/ | grep -i usb
usb

ls /dev/ | grep -i tty
tty
tty0
tty1
tty10
tty11
tty12
tty13
tty14
tty15
tty16
tty17
tty18
tty19
tty2
tty20
tty21
tty22
tty23
tty24
tty25
tty26
tty27
tty28
tty29
tty3
tty30
tty31
tty32
tty33
tty34
tty35
tty36
tty37
tty38
tty39
tty4
tty40
tty41
tty42
tty43
tty44
tty45
tty46
tty47
tty48
tty49
ttty5
tty50
tty51
tty52
tty53
tty54
tty55
tty56
tty57
tty58
tty59
tty6
tty60
tty61
tty62
tty63
tty7
tty8
tty9
ttyS0
ttyS2
ttyS3
ttyS4
ttyS5
ttyS6
ttyS7

 

0
Link to comment
Share on other sites
Igor

Igor

Posted
Posted

https://forum.armbian.com/topic/5699-how-to-provide-and-interpret-debug-output/ (more debug helps a lot more)

 

My case with similar 32b hardware but with supported kernel on unsupported board.
  

nanopim1:~:# uname -a
Linux nanopim1 5.15.93-sunxi #23.02.2 SMP

  

nanopim1:~:# ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 May 15 07:17 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 May 15 07:17 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 May 15 07:17 /dev/ttyUSB2
crw-rw---- 1 root dialout 188, 3 May 15 07:17 /dev/ttyUSB3
crw-rw---- 1 root dialout 188, 4 May 15 07:17 /dev/ttyUSB4
crw-rw---- 1 root dialout 188, 5 May 15 07:17 /dev/ttyUSB5
crw-rw---- 1 root dialout 188, 6 May 15 07:17 /dev/ttyUSB6
crw-rw---- 1 root dialout 188, 7 May 15 07:17 /dev/ttyUSB7
crw-rw---- 1 root dialout 188, 8 May 15 07:17 /dev/ttyUSB8

 

Spoiler 
nanopim1:~:# sudo lsusb -t -v
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    ID 1d6b:0001 Linux Foundation 1.1 root hub
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    ID 1d6b:0001 Linux Foundation 1.1 root hub
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    ID 1d6b:0001 Linux Foundation 1.1 root hub
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 2109:2813 VIA Labs, Inc. 
        |__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
            ID 2109:2813 VIA Labs, Inc. 
            |__ Port 1: Dev 4, If 0, Class=Vendor Specific Class, Driver=ch341, 12M
                ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
            |__ Port 3: Dev 5, If 0, Class=Vendor Specific Class, Driver=ch341, 12M
                ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
            |__ Port 4: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M
                ID 2109:2813 VIA Labs, Inc. 
                |__ Port 4: Dev 10, If 0, Class=Hub, Driver=hub/4p, 480M
                    ID 2109:2813 VIA Labs, Inc. 
                    |__ Port 2: Dev 12, If 0, Class=Vendor Specific Class, Driver=ch341, 12M
                        ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
                    |__ Port 3: Dev 13, If 0, Class=Vendor Specific Class, Driver=ch341, 12M
                        ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
                    |__ Port 1: Dev 11, If 0, Class=Vendor Specific Class, Driver=ch341, 12M
                        ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
                    |__ Port 4: Dev 14, If 0, Class=Vendor Specific Class, Driver=ch341, 12M
                        ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
                |__ Port 2: Dev 8, If 0, Class=Vendor Specific Class, Driver=ch341, 12M
                    ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
                |__ Port 3: Dev 9, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M
                    ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
                |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M
                    ID 10c4:ea60 Silicon Labs CP210x UART Bridge
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub

 

 

Perhaps this?
https://www.google.com/search?q=ch340+fake

0
Link to comment
Share on other sites
N3u67wEeUt2

N3u67wEeUt2

Posted
  • Author
Posted

Thank you for reply.

 

It's definitely not fake as I use the same on Raspberry Pi and it works fine.

 

Raspberry pi: 

sudo lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 275d:0ba6  USB OPTICAL MOUSE
Bus 001 Device 004: ID 27c0:0818 Cadwell Laboratories, Inc. Paperlike HD-FT
Bus 001 Device 003: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


sudo lsusb -t -v
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 2109:3431 VIA Labs, Inc. Hub
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=ch341, 12M
            ID 1a86:7523 QinHeng Electronics CH340 serial converter
        |__ Port 2: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            ID 27c0:0818 Cadwell Laboratories, Inc. Paperlike HD-FT
        |__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            ID 27c0:0818 Cadwell Laboratories, Inc. Paperlike HD-FT
        |__ Port 3: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
            ID 275d:0ba6

ls /dev/ | grep -i usb
ttyUSB0
usb

 

 

Banana Pie 

 sudo lsusb
Bus 002 Device 006: ID 413c:2110 Dell Computer Corp. Dell Wired Multimedia Keyboard
Bus 002 Device 005: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Bus 002 Device 004: ID 413c:1010 Dell Computer Corp. USB 2.0 Hub [MTT]
Bus 002 Device 003: ID 05c6:f00e Qualcomm, Inc. Android
Bus 002 Device 002: ID 0a05:7211 Unknown Manufacturer hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub



sudo lsusb -t -v
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    ID 1d6b:0001 Linux Foundation 1.1 root hub
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 12M
        ID 0a05:7211 Unknown Manufacturer hub
        |__ Port 2: Dev 3, If 0, Class=Wireless, Driver=rndis_host, 12M
            ID 05c6:f00e Qualcomm, Inc.
        |__ Port 2: Dev 3, If 1, Class=CDC Data, Driver=rndis_host, 12M
            ID 05c6:f00e Qualcomm, Inc.
        |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 12M
            ID 413c:1010 Dell Computer Corp.
            |__ Port 4: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
                ID 413c:2110 Dell Computer Corp.
            |__ Port 4: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
                ID 413c:2110 Dell Computer Corp.
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub

ls /dev/ | grep -i usb
usb

 

 

Looks like low power: armbian-hardware-monitor.log 

[    4.212594] hub 2-1.4:1.0: USB hub found
[    4.214421] hub 2-1.4:1.0: 4 ports detected
[    4.524151] usb 2-1.4.1: new full-speed USB device number 5 using ohci-platform
[    4.640474] usb 2-1.4.1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.33
[    4.640518] usb 2-1.4.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[    4.640533] usb 2-1.4.1: Product: USB Serial
[    4.641133] usb 2-1.4.1: rejected 1 configuration due to insufficient available bus power

 

0
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept