Re: [gentoo-user] TUSB3410 on 3.0.6 kernel

[Érico Porto]

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@××××××××××.com>wrote:

> 2011/11/7 Érico Porto <ericoporto2008@×××××.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@×××××.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.
>
>