(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 initiali
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" \*
*
2011/11/7 É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
> exchan
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
2011/11/7 Érico Porto :
> 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,
É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
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 wrote:
> Érico Porto 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 virt
type there : modprobe ti_usb_3410_5052 product=f432 vendor=0451
Érico V. Porto
On Sun, Nov 6, 2011 at 8:50 PM, Dale 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
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
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
:-)
É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
:-) :-)
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 wrote:
> Ok I will try it.
>
> I used:
>
> make && make modules_install && make
2011/11/6 Érico Porto :
> 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
> wrote:
>>
>> 2011/11/6 Érico Porto :
>> > Hello,
>> > I would like to ask ab
On Mon, Nov 7, 2011 at 9:28 AM, É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?
Yes, you're right. I only use make modules if I'm adding a module to
an existing setup.
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 wrote:
> 2011/11/6 Érico Porto :
> > Hello,
> > I would like to ask about the kernel 3.0.6. I can't load
> > the
2011/11/6 Érico Porto :
> 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
> 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'.
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'.
19 matches
Mail list logo
