USB to Serial device won't assign CP210x driver Announcing the arrival of Valued Associate...

calculator's angle answer for trig ratios that can work in more than 1 quadrant on the unit circle

How to make triangles with rounded sides and corners? (squircle with 3 sides)

Sally's older brother

Was the pager message from Nick Fury to Captain Marvel unnecessary?

Pointing to problems without suggesting solutions

Improvising over quartal voicings

Found this skink in my tomato plant bucket. Is he trapped? Or could he leave if he wanted?

How to name indistinguishable henchmen in a screenplay?

3D Masyu - A Die

How can I prevent/balance waiting and turtling as a response to cooldown mechanics

What is "Lambda" in Heston's original paper on stochastic volatility models?

Should man-made satellites feature an intelligent inverted "cow catcher"?

Keep at all times, the minus sign above aligned with minus sign below

Can two people see the same photon?

Why can't fire hurt Daenerys but it did to Jon Snow in season 1?

Does the main washing effect of soap come from foam?

"Destructive power" carried by a B-52?

malloc in main() or malloc in another function: allocating memory for a struct and its members

What did Turing mean when saying that "machines cannot give rise to surprises" is due to a fallacy?

Is there a verb for listening stealthily?

Why are two-digit numbers in Jonathan Swift's "Gulliver's Travels" (1726) written in "German style"?

Where did Ptolemy compare the Earth to the distance of fixed stars?

Do i imagine the linear (straight line) homotopy in a correct way?

Did John Wesley plagiarize Matthew Henry...?



USB to Serial device won't assign CP210x driver



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionFind out which modules are associated with a usb device?How to assign USB driver to deviceWD MyBook 3TB - Gparted failed & HDD partitions recovery?Linux cdc_acm device - unexpected characters sent to USB deviceWhat can cause a usb port speed change?USB WiFi on CentOS7Laggy, hanging, unstable bluetooth keyboard with Linux onlyOutput to Mini USB keypad/screenGadget serial driver, communicate with another device through USBUSB ports keep resetting on LinuxPL2303/PL2303X USB-Serial driver





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















I'm running Jessie Lite on a RPi2. When I connect my USB to Serial device it does show up, however the driver is not assigned.



lsusb -t

/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
|__ Port 3: Dev 13, If 0, Class=Vendor Specific Class, Driver=, 12M


The CP210x driver from Silicon Labs seems to be installed:



lsmod

Module Size Used by
cp210x 9419 0
usbserial 29964 1 cp210x


Now I did try manual binding without success:



echo -n "1-1.3:1.0" > /sys/bus/usb/drivers/cp210x/bind

write error: No such device


Since I'm fairly new to Linux and I need that thing running, I'd be grateful for suggestions. Side note: I have a little Python script running on a Windows machine that is able to talk to the very device just fine...



The device is there, I can't figure out why it's not been found:



tree /sys/bus/usb/devices/

├── 1-1.3 -> ../../../devices/platform/soc/20980000.usb/usb1/1-1/1-1.3
├── 1-1.3:1.0 -> ../../../devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3:1.0


Might the additional information from usb-devices help finding the problem?



T:  Bus=01 Lev=02 Prnt=02 Port=04 Cnt=02 Dev#=  6 Spd=12  MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=18ef ProdID=e030 Rev=01.00
S: Manufacturer=Silicon Labs
S: Product=ALC 8500 Expert
S: SerialNumber=3ENAEFJAVJCO9AQQ
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)









share|improve this question
















bumped to the homepage by Community 36 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • What is the directory listing under /sys/bus/usb/drivers/cp210x ? Is there a new_id file?

    – jc__
    Aug 1 '16 at 18:24











  • There's just bind, module, uevent and unbind. The same goes for usbserial.

    – Matthias Frei
    Aug 2 '16 at 19:48











  • Double check the id for your device and try to rebind. (1-1:1.3).

    – jc__
    Aug 2 '16 at 20:39











  • Just passing through today... Here is a help page in my notes: (lwn.net/Articles/143397)

    – jc__
    Aug 2 '16 at 20:44











  • Are you working from a root shell? Remember that sudo echo... will not work.

    – jc__
    Aug 3 '16 at 18:34


















1















I'm running Jessie Lite on a RPi2. When I connect my USB to Serial device it does show up, however the driver is not assigned.



lsusb -t

/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
|__ Port 3: Dev 13, If 0, Class=Vendor Specific Class, Driver=, 12M


The CP210x driver from Silicon Labs seems to be installed:



lsmod

Module Size Used by
cp210x 9419 0
usbserial 29964 1 cp210x


Now I did try manual binding without success:



echo -n "1-1.3:1.0" > /sys/bus/usb/drivers/cp210x/bind

write error: No such device


Since I'm fairly new to Linux and I need that thing running, I'd be grateful for suggestions. Side note: I have a little Python script running on a Windows machine that is able to talk to the very device just fine...



The device is there, I can't figure out why it's not been found:



tree /sys/bus/usb/devices/

├── 1-1.3 -> ../../../devices/platform/soc/20980000.usb/usb1/1-1/1-1.3
├── 1-1.3:1.0 -> ../../../devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3:1.0


Might the additional information from usb-devices help finding the problem?



T:  Bus=01 Lev=02 Prnt=02 Port=04 Cnt=02 Dev#=  6 Spd=12  MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=18ef ProdID=e030 Rev=01.00
S: Manufacturer=Silicon Labs
S: Product=ALC 8500 Expert
S: SerialNumber=3ENAEFJAVJCO9AQQ
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)









share|improve this question
















bumped to the homepage by Community 36 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • What is the directory listing under /sys/bus/usb/drivers/cp210x ? Is there a new_id file?

    – jc__
    Aug 1 '16 at 18:24











  • There's just bind, module, uevent and unbind. The same goes for usbserial.

    – Matthias Frei
    Aug 2 '16 at 19:48











  • Double check the id for your device and try to rebind. (1-1:1.3).

    – jc__
    Aug 2 '16 at 20:39











  • Just passing through today... Here is a help page in my notes: (lwn.net/Articles/143397)

    – jc__
    Aug 2 '16 at 20:44











  • Are you working from a root shell? Remember that sudo echo... will not work.

    – jc__
    Aug 3 '16 at 18:34














1












1








1








I'm running Jessie Lite on a RPi2. When I connect my USB to Serial device it does show up, however the driver is not assigned.



lsusb -t

/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
|__ Port 3: Dev 13, If 0, Class=Vendor Specific Class, Driver=, 12M


The CP210x driver from Silicon Labs seems to be installed:



lsmod

Module Size Used by
cp210x 9419 0
usbserial 29964 1 cp210x


Now I did try manual binding without success:



echo -n "1-1.3:1.0" > /sys/bus/usb/drivers/cp210x/bind

write error: No such device


Since I'm fairly new to Linux and I need that thing running, I'd be grateful for suggestions. Side note: I have a little Python script running on a Windows machine that is able to talk to the very device just fine...



The device is there, I can't figure out why it's not been found:



tree /sys/bus/usb/devices/

├── 1-1.3 -> ../../../devices/platform/soc/20980000.usb/usb1/1-1/1-1.3
├── 1-1.3:1.0 -> ../../../devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3:1.0


Might the additional information from usb-devices help finding the problem?



T:  Bus=01 Lev=02 Prnt=02 Port=04 Cnt=02 Dev#=  6 Spd=12  MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=18ef ProdID=e030 Rev=01.00
S: Manufacturer=Silicon Labs
S: Product=ALC 8500 Expert
S: SerialNumber=3ENAEFJAVJCO9AQQ
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)









share|improve this question
















I'm running Jessie Lite on a RPi2. When I connect my USB to Serial device it does show up, however the driver is not assigned.



lsusb -t

/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
|__ Port 3: Dev 13, If 0, Class=Vendor Specific Class, Driver=, 12M


The CP210x driver from Silicon Labs seems to be installed:



lsmod

Module Size Used by
cp210x 9419 0
usbserial 29964 1 cp210x


Now I did try manual binding without success:



echo -n "1-1.3:1.0" > /sys/bus/usb/drivers/cp210x/bind

write error: No such device


Since I'm fairly new to Linux and I need that thing running, I'd be grateful for suggestions. Side note: I have a little Python script running on a Windows machine that is able to talk to the very device just fine...



The device is there, I can't figure out why it's not been found:



tree /sys/bus/usb/devices/

├── 1-1.3 -> ../../../devices/platform/soc/20980000.usb/usb1/1-1/1-1.3
├── 1-1.3:1.0 -> ../../../devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3:1.0


Might the additional information from usb-devices help finding the problem?



T:  Bus=01 Lev=02 Prnt=02 Port=04 Cnt=02 Dev#=  6 Spd=12  MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=18ef ProdID=e030 Rev=01.00
S: Manufacturer=Silicon Labs
S: Product=ALC 8500 Expert
S: SerialNumber=3ENAEFJAVJCO9AQQ
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)






linux drivers usb






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 2 '16 at 21:54







Matthias Frei

















asked Aug 1 '16 at 11:58









Matthias FreiMatthias Frei

614




614





bumped to the homepage by Community 36 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 36 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • What is the directory listing under /sys/bus/usb/drivers/cp210x ? Is there a new_id file?

    – jc__
    Aug 1 '16 at 18:24











  • There's just bind, module, uevent and unbind. The same goes for usbserial.

    – Matthias Frei
    Aug 2 '16 at 19:48











  • Double check the id for your device and try to rebind. (1-1:1.3).

    – jc__
    Aug 2 '16 at 20:39











  • Just passing through today... Here is a help page in my notes: (lwn.net/Articles/143397)

    – jc__
    Aug 2 '16 at 20:44











  • Are you working from a root shell? Remember that sudo echo... will not work.

    – jc__
    Aug 3 '16 at 18:34



















  • What is the directory listing under /sys/bus/usb/drivers/cp210x ? Is there a new_id file?

    – jc__
    Aug 1 '16 at 18:24











  • There's just bind, module, uevent and unbind. The same goes for usbserial.

    – Matthias Frei
    Aug 2 '16 at 19:48











  • Double check the id for your device and try to rebind. (1-1:1.3).

    – jc__
    Aug 2 '16 at 20:39











  • Just passing through today... Here is a help page in my notes: (lwn.net/Articles/143397)

    – jc__
    Aug 2 '16 at 20:44











  • Are you working from a root shell? Remember that sudo echo... will not work.

    – jc__
    Aug 3 '16 at 18:34

















What is the directory listing under /sys/bus/usb/drivers/cp210x ? Is there a new_id file?

– jc__
Aug 1 '16 at 18:24





What is the directory listing under /sys/bus/usb/drivers/cp210x ? Is there a new_id file?

– jc__
Aug 1 '16 at 18:24













There's just bind, module, uevent and unbind. The same goes for usbserial.

– Matthias Frei
Aug 2 '16 at 19:48





There's just bind, module, uevent and unbind. The same goes for usbserial.

– Matthias Frei
Aug 2 '16 at 19:48













Double check the id for your device and try to rebind. (1-1:1.3).

– jc__
Aug 2 '16 at 20:39





Double check the id for your device and try to rebind. (1-1:1.3).

– jc__
Aug 2 '16 at 20:39













Just passing through today... Here is a help page in my notes: (lwn.net/Articles/143397)

– jc__
Aug 2 '16 at 20:44





Just passing through today... Here is a help page in my notes: (lwn.net/Articles/143397)

– jc__
Aug 2 '16 at 20:44













Are you working from a root shell? Remember that sudo echo... will not work.

– jc__
Aug 3 '16 at 18:34





Are you working from a root shell? Remember that sudo echo... will not work.

– jc__
Aug 3 '16 at 18:34










1 Answer
1






active

oldest

votes


















0














Add a rule to udev that will automatically load a driver for an USB device.



Information needed:




  • USB device PID / VID numbers. lsusb output. Does not show in tree mode. lsusb -t

  • Device driver modprobe command. /sbin/modprobe usb-storage


Create a udev rule.



Add your own rule file under /etc/udev/rules.d



sudo vi /etc/udev/rules.d/80-serialToUsb_PID-VID.rules


When you add the rule for udev. This will allow udev to automatically load the driver, upon USB insertion, for any device with the pid/vid listed.




  • Replace #PID# with the PID of your device.

  • Replace #VID# with the VID of your device.

  • Replace #DRIVER# with the command to load the module.

  • Replace #SYS# with the location of the driver under the /sys
    directory.


ACTION=="add", ATTRS{idVendor}=="#VID#", ATTRS{idProduct}=="#PID#", RUN+="#DRIVER#" RUN+="/bin/sh -c 'echo #PID# #VID# > #SYS#'"



Restart udev



sudo /etc/init.d/udev restart


Attach the device and use dmesg to verify





Here is an example I used for a custom mp3 player.



ACTION=="add", ATTRS{idVendor}=="a000", ATTRS{idProduct}=="a000", RUN+="/sbin/modprobe usb-storage" RUN+="/bin/sh -c 'echo a000 a000 > /sys/bus/usb/drivers/usb-storage/new_id'"




This works on Debian 8, and Ubuntu 14.



You are using Debian lite. So, I'm am not 100% sure this will work for you.



I have a Freescale embedded device, mx23, that uses mdev instead of udev and the procedure is a bit different.






share|improve this answer


























  • For most drivers I have the subdir new_id (like for usb-storage or smc95xx). Also I'm not permitted to make it, nor will it be created automatically when I write the rule like you described?! The PI uses udev though.

    – Matthias Frei
    Aug 2 '16 at 20:25











  • new_id is supplied by the driver, not you. Also you may need to sudo su to have permission to echo to bind or new_id.

    – jc__
    Aug 2 '16 at 20:41











  • Replace the ...new_id line with the ...bind command you use.

    – jc__
    Aug 2 '16 at 20:45











  • I tried all of the above - still nothing. Does the added output from the edited question help verify the problem?

    – Matthias Frei
    Aug 2 '16 at 21:55











  • Is this supposed to show up as a ttyUSB or other tty?

    – jc__
    Aug 3 '16 at 18:18












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f299599%2fusb-to-serial-device-wont-assign-cp210x-driver%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Add a rule to udev that will automatically load a driver for an USB device.



Information needed:




  • USB device PID / VID numbers. lsusb output. Does not show in tree mode. lsusb -t

  • Device driver modprobe command. /sbin/modprobe usb-storage


Create a udev rule.



Add your own rule file under /etc/udev/rules.d



sudo vi /etc/udev/rules.d/80-serialToUsb_PID-VID.rules


When you add the rule for udev. This will allow udev to automatically load the driver, upon USB insertion, for any device with the pid/vid listed.




  • Replace #PID# with the PID of your device.

  • Replace #VID# with the VID of your device.

  • Replace #DRIVER# with the command to load the module.

  • Replace #SYS# with the location of the driver under the /sys
    directory.


ACTION=="add", ATTRS{idVendor}=="#VID#", ATTRS{idProduct}=="#PID#", RUN+="#DRIVER#" RUN+="/bin/sh -c 'echo #PID# #VID# > #SYS#'"



Restart udev



sudo /etc/init.d/udev restart


Attach the device and use dmesg to verify





Here is an example I used for a custom mp3 player.



ACTION=="add", ATTRS{idVendor}=="a000", ATTRS{idProduct}=="a000", RUN+="/sbin/modprobe usb-storage" RUN+="/bin/sh -c 'echo a000 a000 > /sys/bus/usb/drivers/usb-storage/new_id'"




This works on Debian 8, and Ubuntu 14.



You are using Debian lite. So, I'm am not 100% sure this will work for you.



I have a Freescale embedded device, mx23, that uses mdev instead of udev and the procedure is a bit different.






share|improve this answer


























  • For most drivers I have the subdir new_id (like for usb-storage or smc95xx). Also I'm not permitted to make it, nor will it be created automatically when I write the rule like you described?! The PI uses udev though.

    – Matthias Frei
    Aug 2 '16 at 20:25











  • new_id is supplied by the driver, not you. Also you may need to sudo su to have permission to echo to bind or new_id.

    – jc__
    Aug 2 '16 at 20:41











  • Replace the ...new_id line with the ...bind command you use.

    – jc__
    Aug 2 '16 at 20:45











  • I tried all of the above - still nothing. Does the added output from the edited question help verify the problem?

    – Matthias Frei
    Aug 2 '16 at 21:55











  • Is this supposed to show up as a ttyUSB or other tty?

    – jc__
    Aug 3 '16 at 18:18
















0














Add a rule to udev that will automatically load a driver for an USB device.



Information needed:




  • USB device PID / VID numbers. lsusb output. Does not show in tree mode. lsusb -t

  • Device driver modprobe command. /sbin/modprobe usb-storage


Create a udev rule.



Add your own rule file under /etc/udev/rules.d



sudo vi /etc/udev/rules.d/80-serialToUsb_PID-VID.rules


When you add the rule for udev. This will allow udev to automatically load the driver, upon USB insertion, for any device with the pid/vid listed.




  • Replace #PID# with the PID of your device.

  • Replace #VID# with the VID of your device.

  • Replace #DRIVER# with the command to load the module.

  • Replace #SYS# with the location of the driver under the /sys
    directory.


ACTION=="add", ATTRS{idVendor}=="#VID#", ATTRS{idProduct}=="#PID#", RUN+="#DRIVER#" RUN+="/bin/sh -c 'echo #PID# #VID# > #SYS#'"



Restart udev



sudo /etc/init.d/udev restart


Attach the device and use dmesg to verify





Here is an example I used for a custom mp3 player.



ACTION=="add", ATTRS{idVendor}=="a000", ATTRS{idProduct}=="a000", RUN+="/sbin/modprobe usb-storage" RUN+="/bin/sh -c 'echo a000 a000 > /sys/bus/usb/drivers/usb-storage/new_id'"




This works on Debian 8, and Ubuntu 14.



You are using Debian lite. So, I'm am not 100% sure this will work for you.



I have a Freescale embedded device, mx23, that uses mdev instead of udev and the procedure is a bit different.






share|improve this answer


























  • For most drivers I have the subdir new_id (like for usb-storage or smc95xx). Also I'm not permitted to make it, nor will it be created automatically when I write the rule like you described?! The PI uses udev though.

    – Matthias Frei
    Aug 2 '16 at 20:25











  • new_id is supplied by the driver, not you. Also you may need to sudo su to have permission to echo to bind or new_id.

    – jc__
    Aug 2 '16 at 20:41











  • Replace the ...new_id line with the ...bind command you use.

    – jc__
    Aug 2 '16 at 20:45











  • I tried all of the above - still nothing. Does the added output from the edited question help verify the problem?

    – Matthias Frei
    Aug 2 '16 at 21:55











  • Is this supposed to show up as a ttyUSB or other tty?

    – jc__
    Aug 3 '16 at 18:18














0












0








0







Add a rule to udev that will automatically load a driver for an USB device.



Information needed:




  • USB device PID / VID numbers. lsusb output. Does not show in tree mode. lsusb -t

  • Device driver modprobe command. /sbin/modprobe usb-storage


Create a udev rule.



Add your own rule file under /etc/udev/rules.d



sudo vi /etc/udev/rules.d/80-serialToUsb_PID-VID.rules


When you add the rule for udev. This will allow udev to automatically load the driver, upon USB insertion, for any device with the pid/vid listed.




  • Replace #PID# with the PID of your device.

  • Replace #VID# with the VID of your device.

  • Replace #DRIVER# with the command to load the module.

  • Replace #SYS# with the location of the driver under the /sys
    directory.


ACTION=="add", ATTRS{idVendor}=="#VID#", ATTRS{idProduct}=="#PID#", RUN+="#DRIVER#" RUN+="/bin/sh -c 'echo #PID# #VID# > #SYS#'"



Restart udev



sudo /etc/init.d/udev restart


Attach the device and use dmesg to verify





Here is an example I used for a custom mp3 player.



ACTION=="add", ATTRS{idVendor}=="a000", ATTRS{idProduct}=="a000", RUN+="/sbin/modprobe usb-storage" RUN+="/bin/sh -c 'echo a000 a000 > /sys/bus/usb/drivers/usb-storage/new_id'"




This works on Debian 8, and Ubuntu 14.



You are using Debian lite. So, I'm am not 100% sure this will work for you.



I have a Freescale embedded device, mx23, that uses mdev instead of udev and the procedure is a bit different.






share|improve this answer















Add a rule to udev that will automatically load a driver for an USB device.



Information needed:




  • USB device PID / VID numbers. lsusb output. Does not show in tree mode. lsusb -t

  • Device driver modprobe command. /sbin/modprobe usb-storage


Create a udev rule.



Add your own rule file under /etc/udev/rules.d



sudo vi /etc/udev/rules.d/80-serialToUsb_PID-VID.rules


When you add the rule for udev. This will allow udev to automatically load the driver, upon USB insertion, for any device with the pid/vid listed.




  • Replace #PID# with the PID of your device.

  • Replace #VID# with the VID of your device.

  • Replace #DRIVER# with the command to load the module.

  • Replace #SYS# with the location of the driver under the /sys
    directory.


ACTION=="add", ATTRS{idVendor}=="#VID#", ATTRS{idProduct}=="#PID#", RUN+="#DRIVER#" RUN+="/bin/sh -c 'echo #PID# #VID# > #SYS#'"



Restart udev



sudo /etc/init.d/udev restart


Attach the device and use dmesg to verify





Here is an example I used for a custom mp3 player.



ACTION=="add", ATTRS{idVendor}=="a000", ATTRS{idProduct}=="a000", RUN+="/sbin/modprobe usb-storage" RUN+="/bin/sh -c 'echo a000 a000 > /sys/bus/usb/drivers/usb-storage/new_id'"




This works on Debian 8, and Ubuntu 14.



You are using Debian lite. So, I'm am not 100% sure this will work for you.



I have a Freescale embedded device, mx23, that uses mdev instead of udev and the procedure is a bit different.







share|improve this answer














share|improve this answer



share|improve this answer








edited Aug 2 '16 at 20:57

























answered Aug 1 '16 at 18:21









jc__jc__

1,462719




1,462719













  • For most drivers I have the subdir new_id (like for usb-storage or smc95xx). Also I'm not permitted to make it, nor will it be created automatically when I write the rule like you described?! The PI uses udev though.

    – Matthias Frei
    Aug 2 '16 at 20:25











  • new_id is supplied by the driver, not you. Also you may need to sudo su to have permission to echo to bind or new_id.

    – jc__
    Aug 2 '16 at 20:41











  • Replace the ...new_id line with the ...bind command you use.

    – jc__
    Aug 2 '16 at 20:45











  • I tried all of the above - still nothing. Does the added output from the edited question help verify the problem?

    – Matthias Frei
    Aug 2 '16 at 21:55











  • Is this supposed to show up as a ttyUSB or other tty?

    – jc__
    Aug 3 '16 at 18:18



















  • For most drivers I have the subdir new_id (like for usb-storage or smc95xx). Also I'm not permitted to make it, nor will it be created automatically when I write the rule like you described?! The PI uses udev though.

    – Matthias Frei
    Aug 2 '16 at 20:25











  • new_id is supplied by the driver, not you. Also you may need to sudo su to have permission to echo to bind or new_id.

    – jc__
    Aug 2 '16 at 20:41











  • Replace the ...new_id line with the ...bind command you use.

    – jc__
    Aug 2 '16 at 20:45











  • I tried all of the above - still nothing. Does the added output from the edited question help verify the problem?

    – Matthias Frei
    Aug 2 '16 at 21:55











  • Is this supposed to show up as a ttyUSB or other tty?

    – jc__
    Aug 3 '16 at 18:18

















For most drivers I have the subdir new_id (like for usb-storage or smc95xx). Also I'm not permitted to make it, nor will it be created automatically when I write the rule like you described?! The PI uses udev though.

– Matthias Frei
Aug 2 '16 at 20:25





For most drivers I have the subdir new_id (like for usb-storage or smc95xx). Also I'm not permitted to make it, nor will it be created automatically when I write the rule like you described?! The PI uses udev though.

– Matthias Frei
Aug 2 '16 at 20:25













new_id is supplied by the driver, not you. Also you may need to sudo su to have permission to echo to bind or new_id.

– jc__
Aug 2 '16 at 20:41





new_id is supplied by the driver, not you. Also you may need to sudo su to have permission to echo to bind or new_id.

– jc__
Aug 2 '16 at 20:41













Replace the ...new_id line with the ...bind command you use.

– jc__
Aug 2 '16 at 20:45





Replace the ...new_id line with the ...bind command you use.

– jc__
Aug 2 '16 at 20:45













I tried all of the above - still nothing. Does the added output from the edited question help verify the problem?

– Matthias Frei
Aug 2 '16 at 21:55





I tried all of the above - still nothing. Does the added output from the edited question help verify the problem?

– Matthias Frei
Aug 2 '16 at 21:55













Is this supposed to show up as a ttyUSB or other tty?

– jc__
Aug 3 '16 at 18:18





Is this supposed to show up as a ttyUSB or other tty?

– jc__
Aug 3 '16 at 18:18


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f299599%2fusb-to-serial-device-wont-assign-cp210x-driver%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...