[gentoo-user] TUSB3410 on 3.0.6 kernel

[gentoo-user] TUSB3410 on 3.0.6 kernel

[Érico Porto]

[-- Attachment #1: Type: text/plain, Size: 620 bytes --]

Hello,

I would like to ask about the kernel 3.0.6. I can't load
the ti_usb_3410_5052.ko. I mean, when I select it in the kernel menu, it
makes fine, but when I type make modules_install, I get an error:

make[1]: *** No rule to make target `/lib/firmware/./', needed by
`/lib/firmware/ti_3410.fw'.  Stop.
make: *** [_modinst_post] Error 2

Has anyone tried it in the 3.0.6 kernel? My uname -a output is:

Linux localhost 3.0.6-gentoo #13 SMP Wed Nov 2 21:05:47 BRST 2011 i686
Intel(R) Celeron(R) M processor 900MHz GenuineIntel GNU/Linux

My kernel was loaded using emerge.

Regards

Érico V. Porto

[-- Attachment #2: Type: text/html, Size: 1225 bytes --]

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Adam Carter]

> I would like to ask about the kernel 3.0.6. I can't load
> the ti_usb_3410_5052.ko. I mean, when I select it in the kernel menu, it
> makes fine, but when I type make modules_install, I get an error:
> make[1]: *** No rule to make target `/lib/firmware/./', needed by
> `/lib/firmware/ti_3410.fw'.  Stop.

Did you remember to 'make modules' first?

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Aljosha Papsch]

2011/11/6 Érico Porto <ericoporto2008@gmail.com>:
> Hello,
> I would like to ask about the kernel 3.0.6. I can't load
> the ti_usb_3410_5052.ko. I mean, when I select it in the kernel menu, it
> makes fine, but when I type make modules_install, I get an error:
> make[1]: *** No rule to make target `/lib/firmware/./', needed by
> `/lib/firmware/ti_3410.fw'.  Stop.
> make: *** [_modinst_post] Error 2
> Has anyone tried it in the 3.0.6 kernel? My uname -a output is:
> Linux localhost 3.0.6-gentoo #13 SMP Wed Nov 2 21:05:47 BRST 2011 i686
> Intel(R) Celeron(R) M processor 900MHz GenuineIntel GNU/Linux
> My kernel was loaded using emerge.
> Regards
> Érico V. Porto
>

I solved this by not building firmware into kernel. It's somewhere in
Linux config "General Options".

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Érico Porto]

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

Ok I will try it.

I used:

make && make modules_install && make install

Doesn't the modules get made in the make part?

Érico V. Porto


On Sun, Nov 6, 2011 at 8:16 PM, Aljosha Papsch <papsch.al@googlemail.com>wrote:

> 2011/11/6 Érico Porto <ericoporto2008@gmail.com>:
> > Hello,
> > I would like to ask about the kernel 3.0.6. I can't load
> > the ti_usb_3410_5052.ko. I mean, when I select it in the kernel menu, it
> > makes fine, but when I type make modules_install, I get an error:
> > make[1]: *** No rule to make target `/lib/firmware/./', needed by
> > `/lib/firmware/ti_3410.fw'.  Stop.
> > make: *** [_modinst_post] Error 2
> > Has anyone tried it in the 3.0.6 kernel? My uname -a output is:
> > Linux localhost 3.0.6-gentoo #13 SMP Wed Nov 2 21:05:47 BRST 2011 i686
> > Intel(R) Celeron(R) M processor 900MHz GenuineIntel GNU/Linux
> > My kernel was loaded using emerge.
> > Regards
> > Érico V. Porto
> >
>
> I solved this by not building firmware into kernel. It's somewhere in
> Linux config "General Options".
>
>

[-- Attachment #2: Type: text/html, Size: 1688 bytes --]

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Adam Carter]

On Mon, Nov 7, 2011 at 9:28 AM, Érico Porto <ericoporto2008@gmail.com> wrote:
> Ok I will try it.
> I used:
> make && make modules_install && make install
> Doesn't the modules get made in the make part?

Yes, you're right. I only use make modules if I'm adding a module to
an existing setup.

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Aljosha Papsch]

2011/11/6 Érico Porto <ericoporto2008@gmail.com>:
> Ok I will try it.
> I used:
> make && make modules_install && make install
> Doesn't the modules get made in the make part?
> Érico V. Porto
>
>
> On Sun, Nov 6, 2011 at 8:16 PM, Aljosha Papsch <papsch.al@googlemail.com>
> wrote:
>>
>> 2011/11/6 Érico Porto <ericoporto2008@gmail.com>:
>> > Hello,
>> > I would like to ask about the kernel 3.0.6. I can't load
>> > the ti_usb_3410_5052.ko. I mean, when I select it in the kernel menu, it
>> > makes fine, but when I type make modules_install, I get an error:
>> > make[1]: *** No rule to make target `/lib/firmware/./', needed by
>> > `/lib/firmware/ti_3410.fw'.  Stop.
>> > make: *** [_modinst_post] Error 2
>> > Has anyone tried it in the 3.0.6 kernel? My uname -a output is:
>> > Linux localhost 3.0.6-gentoo #13 SMP Wed Nov 2 21:05:47 BRST 2011 i686
>> > Intel(R) Celeron(R) M processor 900MHz GenuineIntel GNU/Linux
>> > My kernel was loaded using emerge.
>> > Regards
>> > Érico V. Porto
>> >
>>
>> I solved this by not building firmware into kernel. It's somewhere in
>> Linux config "General Options".
>>
>
>

Yes it's just make. Then I tried compiling the kernel, I got the same
error with installing firmware. But I lied in the other message ;) The
location of the option is:
Symbol: FIRMWARE_IN_KERNEL [=n]
  |  Type  : boolean
  │ Prompt: Include in-kernel firmware blobs in kernel binary
  │   Defined at drivers/base/Kconfig:80
  │   Depends on: FW_LOADER [=y]
  │   Location:
  │     -> Device Drivers
  │       -> Generic Driver Options
  │         -> Userspace firmware loading support (FW_LOADER [=y])

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Érico Porto]

[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]

solved,

unmark:

[ ] Include in-kernel firmware blobs in kernel binary

then, type:


make && make firmware_install && make modules_install && make install

Érico V. Porto


On Sun, Nov 6, 2011 at 8:28 PM, Érico Porto <ericoporto2008@gmail.com>wrote:

> Ok I will try it.
>
> I used:
>
> make && make modules_install && make install
>
> Doesn't the modules get made in the make part?
>
> Érico V. Porto
>
>
>
> On Sun, Nov 6, 2011 at 8:16 PM, Aljosha Papsch <papsch.al@googlemail.com>wrote:
>
>> 2011/11/6 Érico Porto <ericoporto2008@gmail.com>:
>> > Hello,
>> > I would like to ask about the kernel 3.0.6. I can't load
>> > the ti_usb_3410_5052.ko. I mean, when I select it in the kernel menu, it
>> > makes fine, but when I type make modules_install, I get an error:
>> > make[1]: *** No rule to make target `/lib/firmware/./', needed by
>> > `/lib/firmware/ti_3410.fw'.  Stop.
>> > make: *** [_modinst_post] Error 2
>> > Has anyone tried it in the 3.0.6 kernel? My uname -a output is:
>> > Linux localhost 3.0.6-gentoo #13 SMP Wed Nov 2 21:05:47 BRST 2011 i686
>> > Intel(R) Celeron(R) M processor 900MHz GenuineIntel GNU/Linux
>> > My kernel was loaded using emerge.
>> > Regards
>> > Érico V. Porto
>> >
>>
>> I solved this by not building firmware into kernel. It's somewhere in
>> Linux config "General Options".
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 2416 bytes --]

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Dale]

[-- Attachment #1: Type: text/plain, Size: 319 bytes --]

Érico Porto wrote:
> Ok I will try it.
>
> I used:
>
> make && make modules_install && make install
>
> Doesn't the modules get made in the make part?
>
> Érico V. Porto


Yep and make install installs them.  I use make all for the first one 
but I don't think it is required anymore.

Dale

:-)  :-)

[-- Attachment #2: Type: text/html, Size: 978 bytes --]

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Dale]

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

Dale wrote:
> Érico Porto wrote:
>> Ok I will try it.
>>
>> I used:
>>
>> make && make modules_install && make install
>>
>> Doesn't the modules get made in the make part?
>>
>> Érico V. Porto
>
>
> Yep and make install installs them.  I use make all for the first one 
> but I don't think it is required anymore.
>
> Dale
>
> :-)  :-)

Sorry, make modules_install installs them.  To many words starting with 
M there.  lol

Dale

:-)  :-)

P. S.  To highlight a point someone else made, you can use make modules 
&& make modules_install if the modules is all you need.  In other words, 
the kernel is already built.

[-- Attachment #2: Type: text/html, Size: 1618 bytes --]

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Érico Porto]

[-- Attachment #1: Type: text/plain, Size: 833 bytes --]

type there :  modprobe ti_usb_3410_5052 product=f432 vendor=0451


Érico V. Porto


On Sun, Nov 6, 2011 at 8:50 PM, Dale <rdalek1967@gmail.com> wrote:

>  Dale wrote:
>
> Érico Porto wrote:
>
> Ok I will try it.
>
>  I used:
>
>  make && make modules_install && make install
>
>  Doesn't the modules get made in the make part?
>
> Érico V. Porto
>
>
>
> Yep and make install installs them.  I use make all for the first one but
> I don't think it is required anymore.
>
> Dale
>
> :-)  :-)
>
>
> Sorry, make modules_install installs them.  To many words starting with M
> there.  lol
>
> Dale
>
> :-)  :-)
>
> P. S.  To highlight a point someone else made, you can use make modules &&
> make modules_install if the modules is all you need.  In other words, the
> kernel is already built.
>

[-- Attachment #2: Type: text/html, Size: 1744 bytes --]

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Érico Porto]

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

so now the module is loadable through modprobe, it all makes with no errors.

It's probably out of this topic, but shouldn't I see a ttyUSB or something
like that in my /dev/ ?

I tried using

modprobe ti_usb_3410_5052 product=0451 vendor f432

I just wanted to read the virtual usb serial out of a Texas launchpad
board. This board uses the TUSB3410 chip. I'm asking about this in the
texas forums too, just was surprised to see so many fast answers.

Érico V. Porto


On Sun, Nov 6, 2011 at 8:40 PM, Dale <rdalek1967@gmail.com> wrote:

>  Érico Porto wrote:
>
> Ok I will try it.
>
>  I used:
>
>  make && make modules_install && make install
>
>  Doesn't the modules get made in the make part?
>
> Érico V. Porto
>
>
>
> Yep and make install installs them.  I use make all for the first one but
> I don't think it is required anymore.
>
> Dale
>
> :-)  :-)
>

[-- Attachment #2: Type: text/html, Size: 1784 bytes --]

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Dale]

Érico Porto wrote:
> so now the module is loadable through modprobe, it all makes with no 
> errors.
>
> It's probably out of this topic, but shouldn't I see a ttyUSB or 
> something like that in my /dev/ ?
>
> I tried using
>
> modprobe ti_usb_3410_5052 product=0451 vendor f432
>
> I just wanted to read the virtual usb serial out of a Texas launchpad 
> board. This board uses the TUSB3410 chip. I'm asking about this in the 
> texas forums too, just was surprised to see so many fast answers.
>
> Érico V. Porto
>

I would think udev would create the device when it is connected or you 
boot up, whichever comes first.  I have no knowledge on the device you 
are using but do on the kernel part.  If you load the module, udev 
should then see the device and create the file in /dev.  That's the 
theory anyway.  You can use udevadm monitor to see if udev sees it as it 
should.  You can also tail -f /var/log/messages to see what happens when 
you connect it or look in dmesg.  One or more of those should tell you 
what is not working.

Dale

:-)  :-)

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Érico Porto]

[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]

Yeah, seem udev is the problem.

I'm reading http://hackaday.com/2009/09/18/how-to-write-udev-rules/

It seems once this is done right, thing will work

Thanks!

(right now, it sees it as generic usb something...)

Érico V. Porto


On Sun, Nov 6, 2011 at 9:20 PM, Dale <rdalek1967@gmail.com> wrote:

> Érico Porto wrote:
>
>> so now the module is loadable through modprobe, it all makes with no
>> errors.
>>
>> It's probably out of this topic, but shouldn't I see a ttyUSB or
>> something like that in my /dev/ ?
>>
>> I tried using
>>
>> modprobe ti_usb_3410_5052 product=0451 vendor f432
>>
>> I just wanted to read the virtual usb serial out of a Texas launchpad
>> board. This board uses the TUSB3410 chip. I'm asking about this in the
>> texas forums too, just was surprised to see so many fast answers.
>>
>> Érico V. Porto
>>
>>
> I would think udev would create the device when it is connected or you
> boot up, whichever comes first.  I have no knowledge on the device you are
> using but do on the kernel part.  If you load the module, udev should then
> see the device and create the file in /dev.  That's the theory anyway.  You
> can use udevadm monitor to see if udev sees it as it should.  You can also
> tail -f /var/log/messages to see what happens when you connect it or look
> in dmesg.  One or more of those should tell you what is not working.
>
> Dale
>
> :-)  :-)
>
>

[-- Attachment #2: Type: text/html, Size: 2079 bytes --]

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Dale]

Érico Porto wrote:
> Yeah, seem udev is the problem.
>
> I'm reading http://hackaday.com/2009/09/18/how-to-write-udev-rules/
>
> It seems once this is done right, thing will work
>
> Thanks!
>
> (right now, it sees it as generic usb something...)
>
> Érico V. Porto
>

You may be able to google around and find one someone else posted.  It 
may be a long shot but writing a udev rule that works could be a long 
shot too.  For me, it would be like hitting the moon with a sling shot.  
lol

If you do write one and it works well, send it to the udev folks and let 
them add it to their list.

Dale

:-)  :-)

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Aljosha Papsch]

2011/11/7 Érico Porto <ericoporto2008@gmail.com>:
> Yeah, seem udev is the problem.
> I'm reading http://hackaday.com/2009/09/18/how-to-write-udev-rules/
> It seems once this is done right, thing will work
> Thanks!
> (right now, it sees it as generic usb something...)
> Érico V. Porto
>
>
> On Sun, Nov 6, 2011 at 9:20 PM, Dale <rdalek1967@gmail.com> wrote:
>>
>> Érico Porto wrote:
>>>
>>> so now the module is loadable through modprobe, it all makes with no
>>> errors.
>>>
>>> It's probably out of this topic, but shouldn't I see a ttyUSB or
>>> something like that in my /dev/ ?
>>>
>>> I tried using
>>>
>>> modprobe ti_usb_3410_5052 product=0451 vendor f432
>>>
>>> I just wanted to read the virtual usb serial out of a Texas launchpad
>>> board. This board uses the TUSB3410 chip. I'm asking about this in the texas
>>> forums too, just was surprised to see so many fast answers.
>>>
>>> Érico V. Porto
>>>
>>
>> I would think udev would create the device when it is connected or you
>> boot up, whichever comes first.  I have no knowledge on the device you are
>> using but do on the kernel part.  If you load the module, udev should then
>> see the device and create the file in /dev.  That's the theory anyway.  You
>> can use udevadm monitor to see if udev sees it as it should.  You can also
>> tail -f /var/log/messages to see what happens when you connect it or look in
>> dmesg.  One or more of those should tell you what is not working.
>>
>> Dale
>>
>> :-)  :-)
>>
>
>

I'm also not familiar with your device, but some devices need to be
mode switched manually if they show up as something different. You can
use usb-modeswitch for that or some more convenient tool like sakis3g:
http://www.sakis3g.org/

Btw: I'll report a bug in Gentoo's Bugzilla regarding your (and mine)
problem. Maybe others are affected too and this option can be switched
off at least for genkernel users.

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Érico Porto]

[-- Attachment #1: Type: text/plain, Size: 2955 bytes --]

oh no, I don't think it is a bug.

I mean, this is suposed to be open using some tool named mspdebug of some
sorta:
http://hackaday.com/2010/08/11/how-to-launchpad-programming-with-linux/

But I know this chip is a usb to serial adapter, only the product Id is
exchanged to be a Development Tool. To change the vendor and product id, I
found a how-to here :
http://www.brimson.com/downloads/ti_usb_multitech_release_notes-1.1.txt

It doesn't seem to do nothing, but maybe I have to write some code on the
msp before. I haven't used this board much, but it is the only thing I have
to test now - I need to interface with   a gps chip, but I have no serials
available, so later I plan to use this chip. I know I have loaded this as a
serial long before...

Érico V. Porto


On Sun, Nov 6, 2011 at 9:58 PM, Aljosha Papsch <papsch.al@googlemail.com>wrote:

> 2011/11/7 Érico Porto <ericoporto2008@gmail.com>:
> > Yeah, seem udev is the problem.
> > I'm reading http://hackaday.com/2009/09/18/how-to-write-udev-rules/
> > It seems once this is done right, thing will work
> > Thanks!
> > (right now, it sees it as generic usb something...)
> > Érico V. Porto
> >
> >
> > On Sun, Nov 6, 2011 at 9:20 PM, Dale <rdalek1967@gmail.com> wrote:
> >>
> >> Érico Porto wrote:
> >>>
> >>> so now the module is loadable through modprobe, it all makes with no
> >>> errors.
> >>>
> >>> It's probably out of this topic, but shouldn't I see a ttyUSB or
> >>> something like that in my /dev/ ?
> >>>
> >>> I tried using
> >>>
> >>> modprobe ti_usb_3410_5052 product=0451 vendor f432
> >>>
> >>> I just wanted to read the virtual usb serial out of a Texas launchpad
> >>> board. This board uses the TUSB3410 chip. I'm asking about this in the
> texas
> >>> forums too, just was surprised to see so many fast answers.
> >>>
> >>> Érico V. Porto
> >>>
> >>
> >> I would think udev would create the device when it is connected or you
> >> boot up, whichever comes first.  I have no knowledge on the device you
> are
> >> using but do on the kernel part.  If you load the module, udev should
> then
> >> see the device and create the file in /dev.  That's the theory anyway.
>  You
> >> can use udevadm monitor to see if udev sees it as it should.  You can
> also
> >> tail -f /var/log/messages to see what happens when you connect it or
> look in
> >> dmesg.  One or more of those should tell you what is not working.
> >>
> >> Dale
> >>
> >> :-)  :-)
> >>
> >
> >
>
> I'm also not familiar with your device, but some devices need to be
> mode switched manually if they show up as something different. You can
> use usb-modeswitch for that or some more convenient tool like sakis3g:
> http://www.sakis3g.org/
>
> Btw: I'll report a bug in Gentoo's Bugzilla regarding your (and mine)
> problem. Maybe others are affected too and this option can be switched
> off at least for genkernel users.
>
>

[-- Attachment #2: Type: text/html, Size: 4143 bytes --]

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Aljosha Papsch]

2011/11/7 Érico Porto <ericoporto2008@gmail.com>:
> oh no, I don't think it is a bug.
> I mean, this is suposed to be open using some tool named mspdebug of some
> sorta: http://hackaday.com/2010/08/11/how-to-launchpad-programming-with-linux/
> But I know this chip is a usb to serial adapter, only the product Id is
> exchanged to be a Development Tool. To change the vendor and product id, I
> found a how-to here
> : http://www.brimson.com/downloads/ti_usb_multitech_release_notes-1.1.txt
> It doesn't seem to do nothing, but maybe I have to write some code on the
> msp before. I haven't used this board much, but it is the only thing I have
> to test now - I need to interface with   a gps chip, but I have no serials
> available, so later I plan to use this chip. I know I have loaded this as a
> serial long before...
> Érico V. Porto
>
>
> On Sun, Nov 6, 2011 at 9:58 PM, Aljosha Papsch <papsch.al@googlemail.com>
> wrote:
>>
>> 2011/11/7 Érico Porto <ericoporto2008@gmail.com>:
>> > Yeah, seem udev is the problem.
>> > I'm reading http://hackaday.com/2009/09/18/how-to-write-udev-rules/
>> > It seems once this is done right, thing will work
>> > Thanks!
>> > (right now, it sees it as generic usb something...)
>> > Érico V. Porto
>> >
>> >
>> > On Sun, Nov 6, 2011 at 9:20 PM, Dale <rdalek1967@gmail.com> wrote:
>> >>
>> >> Érico Porto wrote:
>> >>>
>> >>> so now the module is loadable through modprobe, it all makes with no
>> >>> errors.
>> >>>
>> >>> It's probably out of this topic, but shouldn't I see a ttyUSB or
>> >>> something like that in my /dev/ ?
>> >>>
>> >>> I tried using
>> >>>
>> >>> modprobe ti_usb_3410_5052 product=0451 vendor f432
>> >>>
>> >>> I just wanted to read the virtual usb serial out of a Texas launchpad
>> >>> board. This board uses the TUSB3410 chip. I'm asking about this in the
>> >>> texas
>> >>> forums too, just was surprised to see so many fast answers.
>> >>>
>> >>> Érico V. Porto
>> >>>
>> >>
>> >> I would think udev would create the device when it is connected or you
>> >> boot up, whichever comes first.  I have no knowledge on the device you
>> >> are
>> >> using but do on the kernel part.  If you load the module, udev should
>> >> then
>> >> see the device and create the file in /dev.  That's the theory anyway.
>> >>  You
>> >> can use udevadm monitor to see if udev sees it as it should.  You can
>> >> also
>> >> tail -f /var/log/messages to see what happens when you connect it or
>> >> look in
>> >> dmesg.  One or more of those should tell you what is not working.
>> >>
>> >> Dale
>> >>
>> >> :-)  :-)
>> >>
>> >
>> >
>>
>> I'm also not familiar with your device, but some devices need to be
>> mode switched manually if they show up as something different. You can
>> use usb-modeswitch for that or some more convenient tool like sakis3g:
>> http://www.sakis3g.org/
>>
>> Btw: I'll report a bug in Gentoo's Bugzilla regarding your (and mine)
>> problem. Maybe others are affected too and this option can be switched
>> off at least for genkernel users.
>>
>
>

Sorry, I wasn't clear enough: I reported the bug, that installation of
the kernel will fail if FIRMWARE_IN_KERNEL is enabled. You can add you
to the list, if you want:
https://bugs.gentoo.org/show_bug.cgi?id=389775

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Érico Porto]

[-- Attachment #1: Type: text/plain, Size: 4437 bytes --]

A guy replied this in the e2e ti`s community :
*
n the directory /etc/udev/rules.d/ create a file with the name
026_ti_usb_3410.rules *

*Copy to into this file the following lines*
* *

*#TI USB 3410*
* *

*SUBSYSTEM=="usb_device" ACTION=="add"
SYSFS{idVendor}=="0451",SYSFS{idProduct}=="3410" \*
* *

*SYSFS{bNumConfigurations}=="2" \*
* *

*SYSFS{bConfigurationValue}=="1" \*
* *

*RUN+="/bin/sh -c 'echo 2 > /sys%p/device/bConfigurationValue'"*
* *

* *
* *

*NOTE: Please replace the VID/PID with your device’s VID/PID.*
* *

* *
* *

* *
* *

*At the time you finish this process reboot your system and connect your
device and you must be able to see the node in /dev/ttyUSB0 as your serial
port.*


I will try this when I get home.

Érico V. Porto


On Sun, Nov 6, 2011 at 10:27 PM, Aljosha Papsch <papsch.al@googlemail.com>wrote:

> 2011/11/7 Érico Porto <ericoporto2008@gmail.com>:
> > oh no, I don't think it is a bug.
> > I mean, this is suposed to be open using some tool named mspdebug of some
> > sorta:
> http://hackaday.com/2010/08/11/how-to-launchpad-programming-with-linux/
> > But I know this chip is a usb to serial adapter, only the product Id is
> > exchanged to be a Development Tool. To change the vendor and product id,
> I
> > found a how-to here
> > :
> http://www.brimson.com/downloads/ti_usb_multitech_release_notes-1.1.txt
> > It doesn't seem to do nothing, but maybe I have to write some code on the
> > msp before. I haven't used this board much, but it is the only thing I
> have
> > to test now - I need to interface with   a gps chip, but I have no
> serials
> > available, so later I plan to use this chip. I know I have loaded this
> as a
> > serial long before...
> > Érico V. Porto
> >
> >
> > On Sun, Nov 6, 2011 at 9:58 PM, Aljosha Papsch <papsch.al@googlemail.com
> >
> > wrote:
> >>
> >> 2011/11/7 Érico Porto <ericoporto2008@gmail.com>:
> >> > Yeah, seem udev is the problem.
> >> > I'm reading http://hackaday.com/2009/09/18/how-to-write-udev-rules/
> >> > It seems once this is done right, thing will work
> >> > Thanks!
> >> > (right now, it sees it as generic usb something...)
> >> > Érico V. Porto
> >> >
> >> >
> >> > On Sun, Nov 6, 2011 at 9:20 PM, Dale <rdalek1967@gmail.com> wrote:
> >> >>
> >> >> Érico Porto wrote:
> >> >>>
> >> >>> so now the module is loadable through modprobe, it all makes with no
> >> >>> errors.
> >> >>>
> >> >>> It's probably out of this topic, but shouldn't I see a ttyUSB or
> >> >>> something like that in my /dev/ ?
> >> >>>
> >> >>> I tried using
> >> >>>
> >> >>> modprobe ti_usb_3410_5052 product=0451 vendor f432
> >> >>>
> >> >>> I just wanted to read the virtual usb serial out of a Texas
> launchpad
> >> >>> board. This board uses the TUSB3410 chip. I'm asking about this in
> the
> >> >>> texas
> >> >>> forums too, just was surprised to see so many fast answers.
> >> >>>
> >> >>> Érico V. Porto
> >> >>>
> >> >>
> >> >> I would think udev would create the device when it is connected or
> you
> >> >> boot up, whichever comes first.  I have no knowledge on the device
> you
> >> >> are
> >> >> using but do on the kernel part.  If you load the module, udev should
> >> >> then
> >> >> see the device and create the file in /dev.  That's the theory
> anyway.
> >> >>  You
> >> >> can use udevadm monitor to see if udev sees it as it should.  You can
> >> >> also
> >> >> tail -f /var/log/messages to see what happens when you connect it or
> >> >> look in
> >> >> dmesg.  One or more of those should tell you what is not working.
> >> >>
> >> >> Dale
> >> >>
> >> >> :-)  :-)
> >> >>
> >> >
> >> >
> >>
> >> I'm also not familiar with your device, but some devices need to be
> >> mode switched manually if they show up as something different. You can
> >> use usb-modeswitch for that or some more convenient tool like sakis3g:
> >> http://www.sakis3g.org/
> >>
> >> Btw: I'll report a bug in Gentoo's Bugzilla regarding your (and mine)
> >> problem. Maybe others are affected too and this option can be switched
> >> off at least for genkernel users.
> >>
> >
> >
>
> Sorry, I wasn't clear enough: I reported the bug, that installation of
> the kernel will fail if FIRMWARE_IN_KERNEL is enabled. You can add you
> to the list, if you want:
> https://bugs.gentoo.org/show_bug.cgi?id=389775
>
>

[-- Attachment #2: Type: text/html, Size: 7196 bytes --]

Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Érico Porto]

[-- Attachment #1: Type: text/plain, Size: 5079 bytes --]

(small parenthesis, has anyone tried one of those KKL Vag-Com USB/OBDII
cables on linux? I'm trying it using pyobd, but it doesn't seem to work
very well.. I could find fiat stuff in here
http://www.nailed-barnacle.co.uk/coupe/startrek/startrek.html, but no
Volkswagen stuff, timing, device initialization, does anyone knows it?)

Érico V. Porto


On Mon, Nov 7, 2011 at 3:58 PM, Érico Porto <ericoporto2008@gmail.com>wrote:

> A guy replied this in the e2e ti`s community :
> *
> n the directory /etc/udev/rules.d/ create a file with the name
> 026_ti_usb_3410.rules *
>
> *Copy to into this file the following lines*
> * *
>
> *#TI USB 3410*
> * *
>
> *SUBSYSTEM=="usb_device" ACTION=="add"
> SYSFS{idVendor}=="0451",SYSFS{idProduct}=="3410" \*
> * *
>
> *SYSFS{bNumConfigurations}=="2" \*
> * *
>
> *SYSFS{bConfigurationValue}=="1" \*
> * *
>
> *RUN+="/bin/sh -c 'echo 2 > /sys%p/device/bConfigurationValue'"*
> * *
>
> * *
> * *
>
> *NOTE: Please replace the VID/PID with your device’s VID/PID.*
> * *
>
> * *
> * *
>
> * *
> * *
>
> *At the time you finish this process reboot your system and connect your
> device and you must be able to see the node in /dev/ttyUSB0 as your serial
> port.*
>
>
> I will try this when I get home.
>
> Érico V. Porto
>
>
>
> On Sun, Nov 6, 2011 at 10:27 PM, Aljosha Papsch <papsch.al@googlemail.com>wrote:
>
>> 2011/11/7 Érico Porto <ericoporto2008@gmail.com>:
>> > oh no, I don't think it is a bug.
>> > I mean, this is suposed to be open using some tool named mspdebug of
>> some
>> > sorta:
>> http://hackaday.com/2010/08/11/how-to-launchpad-programming-with-linux/
>> > But I know this chip is a usb to serial adapter, only the product Id is
>> > exchanged to be a Development Tool. To change the vendor and product
>> id, I
>> > found a how-to here
>> > :
>> http://www.brimson.com/downloads/ti_usb_multitech_release_notes-1.1.txt
>> > It doesn't seem to do nothing, but maybe I have to write some code on
>> the
>> > msp before. I haven't used this board much, but it is the only thing I
>> have
>> > to test now - I need to interface with   a gps chip, but I have no
>> serials
>> > available, so later I plan to use this chip. I know I have loaded this
>> as a
>> > serial long before...
>> > Érico V. Porto
>> >
>> >
>> > On Sun, Nov 6, 2011 at 9:58 PM, Aljosha Papsch <
>> papsch.al@googlemail.com>
>> > wrote:
>> >>
>> >> 2011/11/7 Érico Porto <ericoporto2008@gmail.com>:
>> >> > Yeah, seem udev is the problem.
>> >> > I'm reading http://hackaday.com/2009/09/18/how-to-write-udev-rules/
>> >> > It seems once this is done right, thing will work
>> >> > Thanks!
>> >> > (right now, it sees it as generic usb something...)
>> >> > Érico V. Porto
>> >> >
>> >> >
>> >> > On Sun, Nov 6, 2011 at 9:20 PM, Dale <rdalek1967@gmail.com> wrote:
>> >> >>
>> >> >> Érico Porto wrote:
>> >> >>>
>> >> >>> so now the module is loadable through modprobe, it all makes with
>> no
>> >> >>> errors.
>> >> >>>
>> >> >>> It's probably out of this topic, but shouldn't I see a ttyUSB or
>> >> >>> something like that in my /dev/ ?
>> >> >>>
>> >> >>> I tried using
>> >> >>>
>> >> >>> modprobe ti_usb_3410_5052 product=0451 vendor f432
>> >> >>>
>> >> >>> I just wanted to read the virtual usb serial out of a Texas
>> launchpad
>> >> >>> board. This board uses the TUSB3410 chip. I'm asking about this in
>> the
>> >> >>> texas
>> >> >>> forums too, just was surprised to see so many fast answers.
>> >> >>>
>> >> >>> Érico V. Porto
>> >> >>>
>> >> >>
>> >> >> I would think udev would create the device when it is connected or
>> you
>> >> >> boot up, whichever comes first.  I have no knowledge on the device
>> you
>> >> >> are
>> >> >> using but do on the kernel part.  If you load the module, udev
>> should
>> >> >> then
>> >> >> see the device and create the file in /dev.  That's the theory
>> anyway.
>> >> >>  You
>> >> >> can use udevadm monitor to see if udev sees it as it should.  You
>> can
>> >> >> also
>> >> >> tail -f /var/log/messages to see what happens when you connect it or
>> >> >> look in
>> >> >> dmesg.  One or more of those should tell you what is not working.
>> >> >>
>> >> >> Dale
>> >> >>
>> >> >> :-)  :-)
>> >> >>
>> >> >
>> >> >
>> >>
>> >> I'm also not familiar with your device, but some devices need to be
>> >> mode switched manually if they show up as something different. You can
>> >> use usb-modeswitch for that or some more convenient tool like sakis3g:
>> >> http://www.sakis3g.org/
>> >>
>> >> Btw: I'll report a bug in Gentoo's Bugzilla regarding your (and mine)
>> >> problem. Maybe others are affected too and this option can be switched
>> >> off at least for genkernel users.
>> >>
>> >
>> >
>>
>> Sorry, I wasn't clear enough: I reported the bug, that installation of
>> the kernel will fail if FIRMWARE_IN_KERNEL is enabled. You can add you
>> to the list, if you want:
>> https://bugs.gentoo.org/show_bug.cgi?id=389775
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 8099 bytes --]