From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "GARNERO, PIERRE (P.)" <pgarnero@visteon.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Olivier Sobrie <olivier@sobrie.be>,
Daniel Berglund <db@kvaser.com>
Subject: Re: Kvazer USB CAN driver
Date: Wed, 08 Jan 2014 22:28:39 +0100 [thread overview]
Message-ID: <52CDC307.1020102@hartkopp.net> (raw)
In-Reply-To: <85d7d20e09a64996a182e491c6d250e0@AMSPR06MB053.eurprd06.prod.outlook.com>
Hello Pierre,
what exact kernel version are you using there?
Do you use the Mainline driver that comes with Linux or did you use the Kvaser
driver from http://www.kvaser.com/en/downloads.html ??
Can you provide a crash dump?
I also added the Kvaser authors in CC
Regards,
Oliver
On 07.01.2014 17:46, GARNERO, PIERRE (P.) wrote:
> Hello,
>
> Thanks for all this information. And, basically the issue is the fact that no can network interface shows up.
>
> If I boot with the Kvaser device plugged, I could well see it using:
> Lsusb
>
> ...but
> sudo ip link list
> ...does not reveal any can interface while I have loaded these modules: can, can-raw, can-dev, kvaser-usb.
> ...while dmesg displays "usbcore: registered new interface driver kvaser_usb"...
>
> In addition, if I hotplug Kvaser device, I get a kernel panic.
>
> So, I have probably made a mistake when I have built the kernel.
>
> Cheers,
>
> Pierre
>
>
> -----Message d'origine-----
> De : socketcan-users-bounces@lists.berlios.de [mailto:socketcan-users-bounces@lists.berlios.de] De la part de Max S.
> Envoyé : mardi 7 janvier 2014 16:17
> À : socketcan-users@lists.berlios.de
> Objet : Re: [Socketcan-users] Beginner question - Kvazer USB CAN driver
>
> Hello,
>
> I'm not sure about the kvaser in particular, but the driver should create the network interfaces when the USB device is attached.
>
> so no need to add a new socketcan device.
>
> Check to make sure you have kvaser connected:
> lsusb
>
> Check to make sure kvaser driver has made network interfaces:
> sudo ip link list
>
> Then bring the interface up:
> sudo ip link set can0 up type can bitrate 250000
>
> Listen to some frames:
> candump can0
>
> Depending on how you have permissions set up you will require sudo to use most of the ip commands.
>
> Regards,
> Max Schneider
>
> On Tue, 2014-01-07 at 14:17 +0000, GARNERO, PIERRE (P.) wrote:
>> Hello.
>>
>>
>>
>> I would like to use a KVAZER USBcan Rugged device with the socketcan
>> library.
>>
>> I use Raspbian OS and I have built a kernel with anything enabled
>> regarding CAN.
>>
>>
>>
>> I have loaded the following modules:
>>
>> # modprobe can
>>
>> # modprobe vcan
>>
>> # modprobe can-raw
>>
>> # modprobe can-dev
>>
>> # modprobe kvazer-usb
>>
>>
>>
>> But any ip link command (ex: ip link add dev can0 type can) failed
>> with “RTNETLINK answer : operation not permitted” (excepted for vcan
>> which works well).
>>
>>
>>
>> Could someone provide me some hints regarding the steps to have a
>> Kvaser USBcan device up and running using the net driver ?
>>
>>
>>
>> Many thanks in advance,
>>
>>
>>
>> Pierre
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Socketcan-users mailing list
>> Socketcan-users@lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/socketcan-users
>
>
> _______________________________________________
> Socketcan-users mailing list
> Socketcan-users@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/socketcan-users
> _______________________________________________
> Socketcan-users mailing list
> Socketcan-users@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/socketcan-users
>
next prev parent reply other threads:[~2014-01-08 21:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a8d74bed340445f081325afedf044bb5@AMSPR06MB053.eurprd06.prod.outlook.com>
2014-01-07 14:45 ` Kvazer USB CAN driver Oliver Hartkopp
2014-01-07 15:15 ` GARNERO, PIERRE (P.)
[not found] ` <1389107792.5708.9.camel@blackbox>
[not found] ` <85d7d20e09a64996a182e491c6d250e0@AMSPR06MB053.eurprd06.prod.outlook.com>
2014-01-08 21:28 ` Oliver Hartkopp [this message]
2014-01-09 7:12 ` GARNERO, PIERRE (P.)
2014-01-09 13:14 ` GARNERO, PIERRE (P.)
2014-01-13 9:31 ` GARNERO, PIERRE (P.)
2014-01-16 11:02 ` Olivier Sobrie
2014-01-16 12:55 ` GARNERO, PIERRE (P.)
2014-01-17 9:36 ` GARNERO, PIERRE (P.)
2014-01-17 9:50 ` Marc Kleine-Budde
2014-01-17 13:50 ` GARNERO, PIERRE (P.)
2014-01-17 14:00 ` Marc Kleine-Budde
2014-01-18 14:26 ` GARNERO, PIERRE (P.)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CDC307.1020102@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=db@kvaser.com \
--cc=linux-can@vger.kernel.org \
--cc=olivier@sobrie.be \
--cc=pgarnero@visteon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.