1 |
A guy replied this in the e2e ti`s community : |
2 |
* |
3 |
n the directory /etc/udev/rules.d/ create a file with the name |
4 |
026_ti_usb_3410.rules * |
5 |
|
6 |
*Copy to into this file the following lines* |
7 |
* * |
8 |
|
9 |
*#TI USB 3410* |
10 |
* * |
11 |
|
12 |
*SUBSYSTEM=="usb_device" ACTION=="add" |
13 |
SYSFS{idVendor}=="0451",SYSFS{idProduct}=="3410" \* |
14 |
* * |
15 |
|
16 |
*SYSFS{bNumConfigurations}=="2" \* |
17 |
* * |
18 |
|
19 |
*SYSFS{bConfigurationValue}=="1" \* |
20 |
* * |
21 |
|
22 |
*RUN+="/bin/sh -c 'echo 2 > /sys%p/device/bConfigurationValue'"* |
23 |
* * |
24 |
|
25 |
* * |
26 |
* * |
27 |
|
28 |
*NOTE: Please replace the VID/PID with your device’s VID/PID.* |
29 |
* * |
30 |
|
31 |
* * |
32 |
* * |
33 |
|
34 |
* * |
35 |
* * |
36 |
|
37 |
*At the time you finish this process reboot your system and connect your |
38 |
device and you must be able to see the node in /dev/ttyUSB0 as your serial |
39 |
port.* |
40 |
|
41 |
|
42 |
I will try this when I get home. |
43 |
|
44 |
Érico V. Porto |
45 |
|
46 |
|
47 |
On Sun, Nov 6, 2011 at 10:27 PM, Aljosha Papsch <papsch.al@××××××××××.com>wrote: |
48 |
|
49 |
> 2011/11/7 Érico Porto <ericoporto2008@×××××.com>: |
50 |
> > oh no, I don't think it is a bug. |
51 |
> > I mean, this is suposed to be open using some tool named mspdebug of some |
52 |
> > sorta: |
53 |
> http://hackaday.com/2010/08/11/how-to-launchpad-programming-with-linux/ |
54 |
> > But I know this chip is a usb to serial adapter, only the product Id is |
55 |
> > exchanged to be a Development Tool. To change the vendor and product id, |
56 |
> I |
57 |
> > found a how-to here |
58 |
> > : |
59 |
> http://www.brimson.com/downloads/ti_usb_multitech_release_notes-1.1.txt |
60 |
> > It doesn't seem to do nothing, but maybe I have to write some code on the |
61 |
> > msp before. I haven't used this board much, but it is the only thing I |
62 |
> have |
63 |
> > to test now - I need to interface with a gps chip, but I have no |
64 |
> serials |
65 |
> > available, so later I plan to use this chip. I know I have loaded this |
66 |
> as a |
67 |
> > serial long before... |
68 |
> > Érico V. Porto |
69 |
> > |
70 |
> > |
71 |
> > On Sun, Nov 6, 2011 at 9:58 PM, Aljosha Papsch <papsch.al@××××××××××.com |
72 |
> > |
73 |
> > wrote: |
74 |
> >> |
75 |
> >> 2011/11/7 Érico Porto <ericoporto2008@×××××.com>: |
76 |
> >> > Yeah, seem udev is the problem. |
77 |
> >> > I'm reading http://hackaday.com/2009/09/18/how-to-write-udev-rules/ |
78 |
> >> > It seems once this is done right, thing will work |
79 |
> >> > Thanks! |
80 |
> >> > (right now, it sees it as generic usb something...) |
81 |
> >> > Érico V. Porto |
82 |
> >> > |
83 |
> >> > |
84 |
> >> > On Sun, Nov 6, 2011 at 9:20 PM, Dale <rdalek1967@×××××.com> wrote: |
85 |
> >> >> |
86 |
> >> >> Érico Porto wrote: |
87 |
> >> >>> |
88 |
> >> >>> so now the module is loadable through modprobe, it all makes with no |
89 |
> >> >>> errors. |
90 |
> >> >>> |
91 |
> >> >>> It's probably out of this topic, but shouldn't I see a ttyUSB or |
92 |
> >> >>> something like that in my /dev/ ? |
93 |
> >> >>> |
94 |
> >> >>> I tried using |
95 |
> >> >>> |
96 |
> >> >>> modprobe ti_usb_3410_5052 product=0451 vendor f432 |
97 |
> >> >>> |
98 |
> >> >>> I just wanted to read the virtual usb serial out of a Texas |
99 |
> launchpad |
100 |
> >> >>> board. This board uses the TUSB3410 chip. I'm asking about this in |
101 |
> the |
102 |
> >> >>> texas |
103 |
> >> >>> forums too, just was surprised to see so many fast answers. |
104 |
> >> >>> |
105 |
> >> >>> Érico V. Porto |
106 |
> >> >>> |
107 |
> >> >> |
108 |
> >> >> I would think udev would create the device when it is connected or |
109 |
> you |
110 |
> >> >> boot up, whichever comes first. I have no knowledge on the device |
111 |
> you |
112 |
> >> >> are |
113 |
> >> >> using but do on the kernel part. If you load the module, udev should |
114 |
> >> >> then |
115 |
> >> >> see the device and create the file in /dev. That's the theory |
116 |
> anyway. |
117 |
> >> >> You |
118 |
> >> >> can use udevadm monitor to see if udev sees it as it should. You can |
119 |
> >> >> also |
120 |
> >> >> tail -f /var/log/messages to see what happens when you connect it or |
121 |
> >> >> look in |
122 |
> >> >> dmesg. One or more of those should tell you what is not working. |
123 |
> >> >> |
124 |
> >> >> Dale |
125 |
> >> >> |
126 |
> >> >> :-) :-) |
127 |
> >> >> |
128 |
> >> > |
129 |
> >> > |
130 |
> >> |
131 |
> >> I'm also not familiar with your device, but some devices need to be |
132 |
> >> mode switched manually if they show up as something different. You can |
133 |
> >> use usb-modeswitch for that or some more convenient tool like sakis3g: |
134 |
> >> http://www.sakis3g.org/ |
135 |
> >> |
136 |
> >> Btw: I'll report a bug in Gentoo's Bugzilla regarding your (and mine) |
137 |
> >> problem. Maybe others are affected too and this option can be switched |
138 |
> >> off at least for genkernel users. |
139 |
> >> |
140 |
> > |
141 |
> > |
142 |
> |
143 |
> Sorry, I wasn't clear enough: I reported the bug, that installation of |
144 |
> the kernel will fail if FIRMWARE_IN_KERNEL is enabled. You can add you |
145 |
> to the list, if you want: |
146 |
> https://bugs.gentoo.org/show_bug.cgi?id=389775 |
147 |
> |
148 |
> |