Re: Kvaser socketCAN support

[Oliver Hartkopp <socketcan@hartkopp.net>]

On 01.05.2014 16:31, Adams, Shawn - 0999 - MITLL wrote:
> On boot, with the kvaser device attached we see a vcan0
> Please find the output of lsusb and dmesg as well as the contents of /proc/net/dev
> 
> root@localhost:~# cat /proc/net/dev
> Inter-|   Receive                                                |  Transmit
>  face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
>  vcan0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
>     lo:    3432      40    0    0    0     0          0         0     3432      40    0    0    0     0       0          0
>   eth0:       0       0    0    0    0     0          0         0     1646      11    0    0    0     0       0          0

Ok - you have a vcan0 (which is implemented by the virtual CAN 'vcan' driver).
Nothing like "can0" we would expect from a *real* CAN interface :-(

> 
> root@localhost:~# lsusb
> Bus 001 Device 002: ID 0bfd:0017 Kvaser AB

Looks like a
#define USB_LEAF_PRO_LIN_PRODUCT_ID	17

> root@localhost:~# dmesg |grep -i can
> [    4.231784] CAN device driver interface
> [    5.233369] kvaser_usb 1-1:1.0: Cannot get software infos, error -110

Ugh!
The driver fails to retrieve the firmware information. Therefore no 'can0' is
created by the driver.

The return code '-110' is a timeout, see
linux/include/uapi/asm-generic/errno.h:

#define ETIMEDOUT       110     /* Connection timed out */

So it looks like an USB communication problem - or the hardware does not know
about the firmware information command.

Besides trying another PC with a different USB host adapter the only guys that
might help in this situation are Olivier or Troy - I put them in CC.

Regards,
Oliver